Overview
Why Multiple Agents?
Vesper Code agents spawn other agents, share tools, and pass context between tasks:
- Code Generation - writes code
- Review - catches bugs and style issues
- Research - finds docs and examples
- Planning - breaks down requirements
- File Discovery - navigates codebases
Programmatic Control
Control agents with TypeScript generator functions. Orchestrate workflows, branch on file contents, and make steps deterministic instead of hoping a prompt lands the right way.
Built-in Agents
vesper/base- Main coding assistant (orchestrates other agents)vesper/editor- Code editing and file modificationsvesper/reviewer- Code review and feedbackvesper/thinker- Deep thinking and problem analysisvesper/researcher- Web search and documentation lookupvesper/file-picker- File discovery in your codebasevesper/commander- Terminal command executionvesper/code-searcher- Search patterns in code files
Browse all available agents at the Agent Store.
Agent Workflow
A typical call to Vesper Code may result in the following flow:
mermaid diagram
Rendering diagram...
Example: Authentication System Refactoring
If you ask "refactor this authentication system", Vesper Code might:
- File Picker finds auth-related files
- Research looks up best practices
- Planning creates step-by-step plan
- Base implements changes informed by the previous agents
- Reviewer checks for security issues
Agent Coordination
Agents coordinate through the spawnerPrompt field, which tells others when to spawn them. Agents can spawn others listed in spawnableAgents.
Quick Start
Start Vesper Code and run the /init command to set up your project:
vesper
Then inside the CLI:
/init
- Customize existing agents - Modify prompts and tools
- Create new agents - Build specialized functionality
- Reference guide - Complete field documentation