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 Windowspylauncher on its own. - Git.
- An Arcus account and project.
Install the plugin
Section titled “Install the plugin”-
In your terminal, add the Arcus marketplace and install the plugin.
Terminal window claude plugin marketplace add testsigmahq/arcus-claude-pluginclaude plugin install arcus@testsigma
-
Run
claude plugin listand confirm thatarcus@testsigmashows as enabled. -
If Claude Code was already open, run
/reload-pluginsin it. If/arcus:loginstill 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.
Sign in and pick a project
Section titled “Sign in and pick a project”-
In Claude Code, run
/arcus:login. -
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.
-
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.
-
Run
/arcus:project listto see your projects, then/arcus:project use <project_id>to pin the one your sessions go to./arcus:project currentshows 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.
Link your work to a ticket
Section titled “Link your work to a ticket”Run /arcus:map ticket <KEY> with the ticket for the work you’re doing:
/arcus:map ticket PROJ-123Claude 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.
Where your work lands
Section titled “Where your work lands”- 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.

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.
What the plugin sends
Section titled “What the plugin sends”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:
.envfiles, private keys,credentials*files,.netrc, and anything under~/.ssh. Add your own patterns, comma-separated, inTESTSIGMA_SENSITIVE_PATTERNS. - Dependency and build folders are skipped, such as
node_modules,dist,build, and.git. Add your own inTESTSIGMA_EXCLUDE_PATTERNS. - To send events without file contents, set
TESTSIGMA_CONTEXT_INCLUDE_FILES=false.
Troubleshooting
Section titled “Troubleshooting”| Message or symptom | Fix |
|---|---|
Unknown command: /arcus:login | The session started before the install. Run /reload-plugins, or start a new Claude Code session. |
| The browser didn’t open on sign-in | Copy the URL that Claude Code prints into your browser. Run /arcus:login again if 5 minutes have passed. |
| Sessions don’t reach Arcus | Run /arcus:project current to check that a project is pinned, then run /arcus:login again. |
| Signed in to the wrong region | Run /arcus:logout, then /arcus:login, and pick the right region. |
/arcus:map says no project is pinned | Run /arcus:project use <project_id>, then map the ticket again. |
| A session is mapped to the wrong ticket | Run /arcus:map ticket <KEY> again with the right ticket. |
Run /arcus:help to see the commands and the usual flow.
Was this page helpful?
Thanks for the feedback.