Skip to content
Docs
Arcus
Popular questions
↑↓ to navigate↵ to selectesc to close
Book a demo

Claude Code

The Arcus plugin for Claude Code sends your coding sessions to Context Management in QI Home, where Arcus generates test cases from them.

Prerequisites

  • Claude Code.
  • Python 3.9 or later. The plugin finds python3, python, or the Windows py launcher on its own.
  • Git.
  • An Arcus account and project.
  1. In your terminal, add the Arcus marketplace and install the plugin.

    Terminal window
    claude plugin marketplace add testsigmahq/arcus-claude-plugin
    claude plugin install arcus@testsigma

    The terminal after the install, with the marketplace and plugin success lines outlined

  2. Run claude plugin list and confirm that arcus@testsigma shows as enabled.

  3. If Claude Code was already open, run /reload-plugins in it. If /arcus:login still isn’t found, start a new Claude Code session.

Claude Code loads plugins when a session starts. A session that was open during the install doesn’t know the /arcus: commands until you reload or start a new one.

To update the plugin later, run claude plugin marketplace update testsigma, then claude plugin update arcus@testsigma, then /reload-plugins.

  1. In Claude Code, run /arcus:login.

  2. Pick the region your Arcus account is in: United States (the default), India, or Europe. Signing in to the wrong region sends your sessions to the wrong place.

  3. Complete the sign-in in the browser tab that opens. If no tab opens, copy the URL that Claude Code prints into your browser. The sign-in times out after 5 minutes.

  4. Run /arcus:project list to see your projects, then /arcus:project use <project_id> to pin the one your sessions go to. /arcus:project current shows the pinned project.

Capture starts after you sign in. Until then, the plugin sends nothing. You sign in once per machine, and the plugin keeps your sign-in in the OS keychain.

To switch regions, run /arcus:logout, then /arcus:login again. Sessions already sent stay in the old region. /arcus:logout clears your sign-in on this machine only.

Run /arcus:map ticket <KEY> with the ticket for the work you’re doing:

Terminal window
/arcus:map ticket PROJ-123

Claude shows the pinned project and the ticket, and asks you to confirm. The ticket can come from Jira, Azure DevOps, Linear, ClickUp, or GitHub. Your session then arrives in QI Home already mapped to the sprint holding that ticket, so nobody maps it manually.

  • Sessions arrive on the Unlinked Contexts tab of Context Management, under the Claude filter, unless you linked a ticket. Mapping a session to a sprint or an Adhoc session triggers test generation from it.

On QI Home, Dev Tools and AI shows Claude Code as Active once you sign in with /arcus:login.

QI Home Dev Tools and AI, with Claude Code shown as Active and the Context Management button outlined

With the Arcus GitHub App installed, a pull request for work you captured here joins your session:

  • Session not mapped yet: the session and the pull request become a single entry in Unlinked Contexts.
  • Session already mapped: the pull request is mapped to the same sprint or Adhoc session.

After you sign in, the plugin sends your prompts, the tools Claude runs with their inputs and outputs, the files Claude reads and writes, subagent starts and stops, and Claude’s last reply.

  • Sensitive files are never sent: .env files, private keys, credentials* files, .netrc, and anything under ~/.ssh. Add your own patterns, comma-separated, in TESTSIGMA_SENSITIVE_PATTERNS.
  • Dependency and build folders are skipped, such as node_modules, dist, build, and .git. Add your own in TESTSIGMA_EXCLUDE_PATTERNS.
  • To send events without file contents, set TESTSIGMA_CONTEXT_INCLUDE_FILES=false.
Message or symptomFix
Unknown command: /arcus:loginThe session started before the install. Run /reload-plugins, or start a new Claude Code session.
The browser didn’t open on sign-inCopy the URL that Claude Code prints into your browser. Run /arcus:login again if 5 minutes have passed.
Sessions don’t reach ArcusRun /arcus:project current to check that a project is pinned, then run /arcus:login again.
Signed in to the wrong regionRun /arcus:logout, then /arcus:login, and pick the right region.
/arcus:map says no project is pinnedRun /arcus:project use <project_id>, then map the ticket again.
A session is mapped to the wrong ticketRun /arcus:map ticket <KEY> again with the right ticket.

Run /arcus:help to see the commands and the usual flow.

Was this page helpful?