01terse
Spends fewer tokens.
Short output, budgeted context, visible usage. Code, paths, errors, and safety text stay exact.
/terse ultraNewCLI-first coding crew→
Spends less. Writes less. Proves its work.
A coding crew in your terminal: fewer tokens, leaner diffs, review that runs the checks. Bring your own provider key.
Read01
Read the repo before touching it.
Plan02
Pick the smallest checkable path.
Patch03
Patch in the project’s style.
Verify04
Run the gate, then trust it.
Explain05
Report outcome without filler.
›Agent spine[1/5]
01 / runtime
The spine is the product.
Every agent carries the same spine: terse output, budgeted context, lean code, and verification by running.
02budget
Keeps context under control.
Tool output caps and compaction receipts keep long sessions useful without flooding the model.
/status03lean
Writes less, better code.
YAGNI, stdlib, native, existing dependency, one line, then custom code. In that order.
/review04plan
Plans before files move.
Best route, named alternatives, scaffold, and checks before implementation starts.
/plan <need>05build
Builds in vertical slices.
Small repo-aware diffs, project conventions, checks after each slice.
/build <need>06review
Proves its review.
Findings are proposals. Tests, typechecks, builds, and repros decide what is real.
/review02 / flow
Plan. Build. Review. Run.
Every useful step saves tokens, reduces code, or makes a review verifiable. If checks disagree with prose, checks win.
01
Read
Map the repository before acting, including scripts, frameworks, dirty files, and local conventions.
→02
Plan
Name the path, tradeoffs, and checks so implementation has a finish line.
→03
Patch
Make focused edits in the right files and keep unrelated churn out of the diff.
→04
Verify
Run the closest meaningful gate and separate confirmed failures from speculation.
→05
Explain
Close with changed files, commands, outcomes, and any remaining risk.
→03 / commands
Commands are the interface.
A small command surface for the whole crew: plan, build, review, scan, remember, resume.
04 / pricing
Start local. Scale when needed.
BYOK by default. Hosted credit resale stays outside the CLI core.
Install
BYOK · your keys
Put the crew in your terminal.
Open GitHub→
Includes:
- orchentra and otr binaries
- Bring your own provider keys
- Repo-local skills and hooks
- JSONL sessions
Operate
Local-first · zero DB
Keep work in git and sessions on disk.
Read the README→
Includes:
- No database in the CLI
- No hosted code workspace required
- Visible token and cost receipts
- Verification gates in the terminal
Scale
Deferred · later
Hosted credit resale stays outside the CLI core.
Track releases→
Includes:
- BYOK remains the default
- Provider routing can stay private
- Policy travels with repos
- No telemetry by default
05 / FAQ
The practical questions.
Short answers for putting a crew near a real repo.
Is Orchentra a model provider?+
No. Orchentra is the crew and spine around your model route: plan, build, review, budget, verify.
[01]
Is Orchentra hosted?+
No. The product runs from your terminal, works against your checkout, stores sessions locally, and ships through CLI plus git.
[02]
How is it different from a normal coding chat?+
It works from the repo outward: read, plan, patch, run, report. The check output beats the prose.
[03]
What happens when a check fails?+
The failure is the source of truth. Orchentra separates proposed findings from evidence produced by real gates.
[04]
Does it store private code?+
The CLI is local-first. Provider traffic depends on your model route; Orchentra does not require a hosted workspace or app database.
[05]