Editing a codebase with Vesper Code

This is the core loop: describe a change in natural language, let Vesper Code find the right files, make the edits, and review them before they land.

cd /path/to/your-repo
vesper

Vesper Code reads your project on demand. You do not need to paste files or explain the layout. The File Picker agent finds what is relevant.

For a one-line fix, just describe it. For anything that spans files, plan first:

/plan

In plan mode Vesper Code proposes the approach and the files it intends to touch before changing anything. You approve or redirect. This is the cheapest place to catch a wrong assumption — before any code is written, not after.

Describe the outcome you want, not the implementation:

"Add rate limiting to the public API routes and return 429 with a Retry-After header."

The Planner sequences the work, the Editor makes precise, context-aware edits across the files, and the Reviewer checks the result for correctness and regressions with fresh context. You see a diff, not a black box.

Read the diff like you would a teammate's pull request. The Reviewer agent has already done an adversarial pass, but you have context it does not — business rules, timing, taste. Accept, refine, or ask for a different approach.

• One task at a time. A focused request produces a focused, reviewable diff. Bundle five unrelated changes and review gets harder.
• Use /init once per project. It creates a knowledge.md where you can record setup commands and conventions Vesper Code should respect. See Knowledge files.
• Large repos: see Working with large projects.

• Quick Start
• How it works
• Modes

Need help? Join the Discord or email support@vespercode.com.