What Veyyon gives you
Veyyon runs in your terminal and edits real code on your keys. The harness is built so capable models waste fewer turns on bad edits and opaque scaffolding.
The problem Veyyon solves
Most coding agents wrap every model in the same generic scaffolding. A model trained for one edit shape is forced into another. The result is wasted turns, malformed tool calls, diffs that fail to apply, and token bills that climb with every retry. The weights are often capable; the scaffolding holds them back.
Veyyon (oh-my-pi lineage) cuts that waste: hashline edits tuned per model, native search and read paths, provider-agnostic configuration, and a TUI that keeps sandboxing and approvals visible.
What you get today
- Edits that land. Hashline and related edit tools with model-specific prompts; fewer retry loops on bad diffs.
- Bring your own key. Dozens of providers via the bundled catalog; no vendor lock-in.
- Per-role models. Assign fast, thinking, vision, task, and other roles without reconfiguring every session.
- A real agent loop. Read, search, edit, bash, LSP, browser, MCP, compaction, and subagents, all inside approval and sandbox policy you control.
- Session trees. Branch, fork, and navigate conversation history without losing abandoned paths.
- Memory. mnemopi-backed recall across sessions (see Memory).
- Lower cost. Fewer format retries and leaner reads mean fewer tokens for the same outcome.
Who Veyyon is for
- Developers who want a capable terminal agent on their own keys.
- Teams running open or gateway models with a harness tuned for coding, not chat-only UIs.
- Anyone who wants visible sandbox boundaries and honest tool failures.