How does Vesper Code actually work?

Vesper Code runs multiple agents, each tuned for a specific task.

The main agent ("Vesper") runs on your selected provider. It reads your prompt, gathers context, and spawns subagents. The orchestrator is available in several variants:

• base2 — Default mode orchestrator
• base2-free — Free mode (faster, no credit cost)
• base2-max — Max mode (best-of-N selection)
• base2-plan — Plan mode (no file writes)

• File Picker — finds relevant files
• Code Searcher — grep-style pattern matching
• Researcher — web and docs lookup
• Thinker — works through hard problems
• Editor — writes and modifies code
• Reviewer — catches bugs and style issues
• Commander — runs terminal commands

In Max mode, Vesper Code spawns multiple editors with different strategies. A selector compares the outputs and picks the best one.

1. Tree-sitter scans your repo and builds a code map
2. File pickers and searchers find relevant code
3. Thinkers analyze the problem if needed
4. Editors generate changes
5. Reviewers check for issues; commanders run tests

The server is stateless. It streams requests to the active model provider over encrypted connections. Your code stays local; only relevant context is sent.