Start with the issue context
Assign or mention Claude on tracked work so the task, comments and relevant workspace context stay connected to the run.
Claude + Velocity
Agents
Bring Claude into the work your team already tracks.
Use Claude with Velocity to triage issues, work selected tasks and review linked pull requests with the context of your workspace.
Illustrative workflow
- 1
Choose the task
Assign an issue, mention Claude, or enable a scoped automatic workflow.
- 2
Run the configured agent
A worker or cloud agent processes the task using its configured capabilities and scope.
- 3
Inspect the result
Review its issue comments, linked commits and supported PR output before completing the work.
What your team gets
Choose the execution method
Use a Claude Code worker for repository edits, tests and commits, or local API and cloud agents for supported workspace and GitHub actions.
Control automatic work
Configure optional triage, scoped backlog work and linked PR reviews with team, project and concurrency controls.
Make it work for your workspace
Enable Claude in the workspace and configure the execution method. Claude Code needs a signed-in local runtime and selected repository. API executors have different capabilities and need their own configured credentials. Automatic workflows are off by default.
Choose the workspace and follow its integration setup. Your existing issue ownership, priorities and workspace permissions stay part of the workflow.
Questions, answered
Can Claude Code edit code for a Velocity issue?
Yes. A configured Claude Code worker uses its selected writable repository to edit, test and commit issue work. Pushing and opening a PR require delivery to be enabled and repository access.
Does connecting Claude to MCP start an agent worker?
No. MCP gives a client access to Velocity tools. A worker or cloud executor must be configured and running to process queued agent tasks.
Bring Claude into your Velocity workflow.
Connect the tools your team uses to the work your team tracks.