- Projects
- Test Cases
- Data Sets
- Imports and Exports
- Step Groups
- Test Runs
- Test Plans
- Integrations
- Testsigma Two-way Integration
- Settings
- Manage Users
- Reports & Analytics
- CI/CD Integrations
Connect Codex
Install the Arcus plugin for Codex so that your coding context is captured and sent to QI Home for test generation.
When the plugin is installed and connected to a project, Atto captures your prompts, tool calls, and file changes as you work. When you are done, you push the context to QI Home with a single command. QA maps the context to the right sprint, and Atto generates test cases based on your development activity.
Prerequisites
Before you begin, ensure that:
- Codex is installed.
- You have an active project in Arcus by Testsigma.
Install the Plugin
The install command for the Codex Arcus plugin is pending confirmation from the dev team. This step will be updated before publication.
Log In and Connect Your Project
- In Codex, run /arcus:login.
- Complete the login flow in the browser. Return to Codex when prompted.
- Run /arcus:project <project-id> to connect the plugin to your Arcus project. Replace <project-id> with your project ID from Arcus > Settings > Project.
- Start coding. The plugin begins capturing your context in the background.
No data is sent to Arcus until you run /arcus:push. Logging in and setting your project does not start any upload.
Map Your Context to a Sprint
Run /arcus:map <ticket-key> at any point before pushing to link your context to a sprint story.
/arcus:map PROJ-123Running /arcus:map before pushing means your context arrives in QI Home already mapped to the correct sprint. QA does not need to route it manually from Unmapped Context.
You can push without mapping. The context lands in Unmapped Context and QA maps it from there. See Map Developer Context.
Push Your Context
- When you are done, run /arcus:push to upload the captured context to QI Home.
The context appears in QI Home under Unmapped Context (if you did not run /arcus:map) or under the mapped sprint (if you did).
Commands Reference
| Command | What it does |
|---|---|
| /arcus:help | Lists all available Arcus commands |
| /arcus:login | Authenticates your Arcus account |
| /arcus:logout | Logs out of your Arcus account |
| /arcus:project |
Connects the plugin to an Arcus project |
| /arcus:map |
Links the current context to a sprint story |
| /arcus:test | Runs tests from QI Home in the current context |
| /arcus:testsigma-tests | Lists existing Testsigma tests for the current project |
| /arcus:push | Uploads the current context to QI Home |
If You Also Use GitHub
If your team has the Arcus GitHub App installed and you raise a pull request for the same work you captured in this context, Atto connects the two automatically:
- Context still unmapped: Atto converts it into a GitHub context. The Codex context and the pull request are unified as a single entry in Unmapped Context.
- Context already mapped: The pull request is auto-mapped to the same sprint or Ad-Hoc session. No further action is needed.
Want to contribute or report missing content?