Features
Everything you need to plan work worth shipping.
Corvi pairs codebase-aware retrieval with a multi-model review engine and an auditable trust boundary. Here's how each piece fits together.
Context
Plans that fit your codebase
Corvi reads your workspace through a security broker and pulls in the code that matters to the task. Each step points at exactly where the work goes — so a reader (or an agent) follows the plan straight into the codebase and starts.
- Workspace-scoped retrieval picks the relevant files automatically.
- Steps resolve to paths and symbols you can click into.
- Refresh the plan at any time as the code evolves.
The engine
A multi-model draft → review → synthesise pipeline
One model drafts the plan, a second independent model reviews it like a senior engineer, and a third synthesises the result into a single coherent plan. Disagreement between models is a feature: it surfaces wrong claims and gaps before you commit to an approach.
- Independent review catches confident-but-wrong reasoning.
- Synthesis de-conflicts findings into one plan.
- Swap models per pass to balance cost and rigor.
Trust & egress
Know exactly what left your machine
Every outbound tool call is opt-in per server, capped by a fetch budget, and logged with its arguments hashed. The egress audit answers a question most tools can't: what data actually left this machine, and why.
- Opt-in egress per integration — nothing leaks by default.
- Budgets stop runaway fetches; events are written to the run log.
- Untrusted content is wrapped before it reaches a model.
The editor
A native macOS editor that respects your work
Plans live in a rich Markdown editor with syntax-aware live preview. Streamed model output flows into a read-only buffer — never over the text you're editing — so iterating on a plan feels safe and fast.
- Live-preview Markdown with code, headings, and lists.
- Streaming never clobbers your edits.
- Keyboard-driven, fast, and local-first.
Workflow
Integrations that draft plans for you
Connect your issue tracker and chat. Assigning a ticket to Corvi auto-drafts a grounded plan attached to the issue, so planning happens where the work already lives — and the loop closes itself.
- Issue assignment triggers an auto-plan.
- Chat integration brings plans to the conversation.
- Extend with MCP servers behind the egress gate.