Vinci Code can spawn multiple agents (called a Crew) to work together on complex tasks. Each agent is isolated, independent, and can review and integrate the work of others.
Spawn a Crew
Use the /agents command (or /helpers as an alias) to tell Vinci to create and spawn child agents:
/agents "Create three agents: one to write the backend API, one to build the frontend, and one to write tests"
Each agent:
- Inherits the session's active Vinci class and works from an isolated snapshot of your project worktree
- Runs independently with its own reasoning and tool use
- Can navigate the codebase, run tests, and make changes to its own copy
How agents work together
- Independent work — each agent explores and implements without waiting for the others.
- Patch review — verified ordinary patches (changes that pass Vinci's review) auto-integrate into the main worktree.
- Status visibility — stale, risky, conflicting, or unverified patches show their status so you can see what's pending.
- No capacity limits — Crew capacity is operational and never plan-tier gated — spawn as many helpers as the task needs.
When to use Crew
Crew shines for:
- Parallel work streams — front-end, back-end, and testing all happening at once.
- Specialized agents — assigning each agent a focused role ("you write documentation", "you optimize performance").
- Large refactors — breaking a big change into independent slices.
Monitor and steer
Type /task-info to see the current task ID and status. Each agent's work is tracked; you can see progress, review patches, and undo or request changes.
For more depth, see the Vinci Code developer guide.