THE ACCOUNTABLE CODING HARNESS
Ship code with
proof attached.
Orchentra coordinates the models, specialist agents, checks, and browser work behind one verifiable coding run.
THE MOTIVE
Models can write code. Orchentra makes the entire run accountable.
THE PROBLEM
A capable model is not
an accountable system.
Without a harness, execution, delegation, and proof drift apart.
- ×One general-purpose agent owns every decision
- ×Subtasks lose budget, lineage, and run context
- ×Exit codes are mistaken for product correctness
- ×Browser verification is optional or manual
- ×Long runs collapse into an uncheckable recap
- ×Parallel work can spread beyond its real limits
- ✓Specialist roles with explicit authority
- ✓Shared budgets and durable child transcripts
- ✓Tests, builds, and browser evidence gate completion
- ✓Real browser operation with deterministic waits
- ✓Linked traces preserve the complete evidence chain
- ✓Local-first, BYOK, zero database, no telemetry
THE SYSTEM
Everything required to turn
a request into verified work.
Unified Harness
Keep planning, edits, delegated work, checks, browser state, and the final completion decision in one accountable run.
Model Profiles
Adapt prompt structure, edit dialect, tool vocabulary, and continuation behavior to the model family doing the work.
Context Engine
Preserve trust-boundary messages and live evidence while compacting only the context that is safe to replace.
ONE ACCOUNTABLE RUN
Launch a coding crew in minutes.
Browser Verification
Start the application, operate the rendered product, and surface console or network failures from a real Chromium session.
Completion Gates
Keep verifiable work open until its declared checks run and the evidence supports the completion claim.
Sub-Agent Runtime
Fan out bounded, independent work while retaining shared budgets, role restrictions, durable state, and parent-child traces.
OUTCOME FIRST
Describe the finish line, not every keystroke.
Orchentra reads the repository, selects a bounded execution path, and keeps the completion contract attached to the work.
SEE THE WORKFLOW ↗MODEL AWARE
One standard of proof. Provider-specific execution.
Prompt structure, edit behavior, tools, and continuation adapt to the model family without changing what “complete” means.
YOUR PROVIDER KEYS.
QUICK START
From install to evidence
in three clear moves.
Install The Harness
Add Orchentra globally, open the repository you want to change, and bring the provider credentials you already control.
Describe The Outcome
State the result you need. Orchentra reads repository instructions, dirty state, scripts, and architecture before work begins.
Run Until Proven
The harness plans, delegates, edits, executes checks, operates the browser when relevant, and returns the evidence chain.
THE RUN LIFECYCLE
Every stage visible.
Every handoff explicit.
Start With The Repository
Load instructions, scripts, architecture, worktree state, and existing conventions before deciding what the task requires.
CLEAR FROM DAY ONE
Open source at the core.
No usage tax from us.
For developers and teams running locally
Open Source
The complete local coding harness. Bring your own provider keys and keep the control plane in your checkout.
- ✓Model-aware runtime
- ✓Browser verification
- ✓Evidence-gated completion
- ✓Specialist sub-agents
- ✓Local traces and sessions
- —Hosted workspace
- —Managed provider credits
For organizations standardizing trusted runs
Teams
A future collaboration layer for teams that need shared policy and review without weakening the local-first core.
- ✓Everything in open source
- ✓Shared completion policies
- ✓Team evidence review
- ✓Organization controls
- ✓Managed collaboration
- —Product telemetry
- —Closed provider lock-in
BUILT ON CONTRACTS
Trust comes from
how the system behaves.
A passing edit is not a finished product. The rendered behavior gets a vote.
Browser evidenceVerification contract
Every specialist receives only the tools and authority required by its role.
Constrained delegationSub-agent contract
The final answer points back to checks and artifacts instead of asking for trust.
Inspectable proofTrace contract
Children draw from the parent run. Parallel work never invents a hidden budget.
Shared ceilingsBudget contract
Provider choice changes execution strategy without changing the completion standard.
Model awarenessRuntime contract
Sessions, traces, credentials, and the working repository remain under local control.
Local ownershipProduct contract
COMMON QUESTIONS
Before your first run.
Orchentra is a model-aware coding harness that coordinates specialist agents, runs the real checks, operates the rendered product when relevant, and preserves the evidence behind completion.
READY WHEN YOUR REPOSITORY IS
Give the next coding run
a real finish line.
Install the open-source harness. Bring your provider keys. Keep the evidence local.