Skip to main content
Voss is a local control plane for coding agents: scoped tools, permission modes, reusable project memory, independent review, and a replayable trail of every action. The harness is the bounded agent loop for a single repo task: plan, execute, inspect, resume. You drive it from the Go terminal client (bare voss), the plain voss chat REPL, or one-shot voss do. The orchestration layer adds teams, a board, a session tree, swarms, and reviewers on top of that loop. voss serve exposes the same engine over a local REST + SSE protocol for SDKs and the separate Voss ADE desktop app. The .voss language declares and controls all of it.

Orchestrate a team

Declare roles and gates, then inspect runs on the board and in the audit.

Run your first task

Use voss do for a bounded one-shot repo task.

Make a scoped edit

Use voss edit to constrain writes to a target and related tests.

Learn .voss

See how the language expresses control — for one agent or a team.

Run a team

A team is declared once in .voss, then a single goal runs as scoped, budgeted, independently reviewed work:
voss team run runs an LLM EM, role workers, and Reviewer A and B. Cards run one at a time in the project directory, and workers can write only inside the team scope. Swarms through voss serve are the other multi-agent path. See the orchestration overview.

What Voss is for

Voss is for developers who already use AI coding tools and want stronger boundaries:
  • Clear separation between planning and mutation
  • Permission prompts for risky operations
  • Scoped file writes for edit sessions
  • Resumable project context
  • Code-aware recall across rebuildable code cache and curated project memory
  • Conservative context packing with an explicit --no-pack escape hatch
  • Workflow rules that can move from prompts into .voss code
  • Multi-agent runs that stay scoped, budgeted, and independently reviewed
  • Your existing Claude and Codex logins, MCP servers, and skills, reused instead of reconfigured
  • Opt-in, advisory Jev judgments that record real probabilities instead of made-up confidence
Voss v0.1 is harness-led and ships through npm as @vosslang/cli, which bundles the Go terminal client. Voss ADE is a separate desktop product that talks to Voss only through the voss serve protocol. Homebrew, editor marketplace work, hosted teams, and broad launch polish remain deferred.

What to read first

  1. Install Voss: Install Voss
  2. Run a read-only one-shot task: First task
  3. Try a scoped edit session: First edit
  4. Learn the safety model: Modes and Security
  5. Run a whole team: Orchestration overview