The coordinationlayer for theagent era
- [ 01 ]Plan before code.
- [ 02 ]Concepts, not diffs.
- [ 03 ]Cross-machine by default.
The agents you already run.
Claude Code
Codex
Cursor
Gemini CLI
OpenCode
Aider- Claude Code
- Codex
- Cursor
- Gemini CLI
- OpenCode
- Aider
- Claude Code
- Codex
- Cursor
- Gemini CLI
- OpenCode
- Aider
Five primitives. One agent contract.
Wrap, plan, submit, verdict, replay. The shape is the same whether the master sits on your laptop or a hosted region.
$ tether wrap claude
→ master: tetherlab.ai (online)
→ session: 4b2e-…-91af
→ developer: alex@team
→ ready.::tether-plan-ready::
{
"summary": "Add /healthz to master HTTP API.",
"steps": [
"Add route in packages/master/src/routes/health.ts",
"Register under public routes",
"Document the endpoint"
]
}
::tether-plan-end::$ tether intent submit --plan plan.json
→ POST /intents (signed: ed25519)
← 202 accepted id=int_8h2k…7c
→ matched concepts: master.health, infra.routes
→ waiting for verdict…← verdict: continue
reason: "no concept conflicts; audit ok"
ttl: 120s
← verdict: revert
reason: "conflicts with auth.session.realized"
snapshot: snap_a3f1…$ tether replay int_8h2k…7c
10:42 plan submitted
10:42 verdict: continue
10:43 3 files edited
10:44 concept: master.health.realized
10:44 ✓ run completeUse Cases
Cross-machine coordination
- multi-laptop
- live intents
- single master
Agents on different developers' machines share one master. Coordination is live, not after-the-fact at PR review.
Read more
Intent-level conflict detection
- plan-stage
- concept match
- rescope
The master matches intents to concepts before any code is written. Conflicts surface as the plan lands, not after the diff.
Read more
Semantic concept catalogue
- domain tags
- global lookup
- self-evolving
Concepts replace files as the unit of meaning. Domains bias ranking. The catalogue updates with every accepted intent.
Read more
Plan-stage incident response
- pause master
- replay
- cross-machine revert
Freeze the swarm mid-flight. Replay any intent timeline post-mortem. Revert across machines, not just inside a repo.
Read more
Living shared world model
- onboarding
- catalogue read
- domain ranking
New agents read the catalogue, not the codebase. Tribal knowledge becomes structured. Ranking stays honest at scale.
Read more
Audit-grade by construction
- signed intents
- verdict trail
- export
Every line of agent code traces back to a signed intent. Verdicts and tool calls land on the timeline. Export on demand.
Read more
Simple per-seat pricing.
One predictable bill. No per-agent fees, no per-intent gotchas.
Solo
Local master, one developer, no card.
$0forever- Local master on your laptop
- 100 intents / month
- Wrap any agent CLI
- Replay last 7 days
- Community Discord
Team
Hosted master for small teams.
$20/moper seat / month- Hosted master (US/EU regions)
- 10,000 intents / month
- Audit log, 30-day retention
- Concept catalogue (250 concepts)
- Slack + email notifications
- Email support
- Most popular
Scale
For coordinated swarms in production.
$60/moper seat / month- Everything in Team
- Unlimited intents
- Audit log, 1-year retention
- SSO (Okta, Google, Azure)
- Role-based concept access
- Priority support, 4h SLA
Enterprise
VPC, on-prem, custom retention.
Customcustom- Self-hosted or VPC master
- Custom audit retention
- SAML SSO + SCIM
- Custom concept policies
- Dedicated Slack channel
- Onboarding engineer
Plug Tether into the agent of your choice.
Tether ships as a Model Context Protocol server. If your CLI speaks MCP, it speaks Tether.
Replaces the diff. Replaces the PR.
Other tools review code after it's written. Tether coordinates the plan before.
| Capability | Tether | Aider | Continue | CodeRabbit | Raw CLI |
|---|---|---|---|---|---|
| Wraps your agent CLI | |||||
| Plan-stage conflict detection | |||||
| Verdict before any edit | |||||
| Cross-machine coordination | |||||
| Semantic concept catalogue | |||||
| Signed audit trail per intent | |||||
| Rescope as a first-class primitive | ~ | ||||
| MCP-native | ~ | ||||
| Self-hostable master |
Teams running it in production.
What engineers say after their first month with the shim.
“Three agents now run the migration in parallel. The master holds the line. We caught a bad rename before it shipped.”
EMElena M.Staff engineer, fintech“The plan-before-write loop changed how we ship. Reviews happen on intent, not on diff.”
DKDevon K.Founding eng, marketplace“Audit log is the bit our security team cared about. Every line of agent code maps to a signed intent.”
RPRiya P.Platform lead“Replay saved us a week. We rewound a bad refactor across two services and re-ran with one tweak.”
MTMateo T.Tech lead, infra“We were already on Claude Code. Tether sat under it on day one. No new mental model.”
ASAnya S.CTO, dev tools startup“Self-hosted master inside the VPC. The compliance review took an afternoon, not a quarter.”
JNJames N.Engineer, gov sector“Three agents now run the migration in parallel. The master holds the line. We caught a bad rename before it shipped.”
EMElena M.Staff engineer, fintech“The plan-before-write loop changed how we ship. Reviews happen on intent, not on diff.”
DKDevon K.Founding eng, marketplace“Audit log is the bit our security team cared about. Every line of agent code maps to a signed intent.”
RPRiya P.Platform lead“Replay saved us a week. We rewound a bad refactor across two services and re-ran with one tweak.”
MTMateo T.Tech lead, infra“We were already on Claude Code. Tether sat under it on day one. No new mental model.”
ASAnya S.CTO, dev tools startup“Self-hosted master inside the VPC. The compliance review took an afternoon, not a quarter.”
JNJames N.Engineer, gov sector
From the engineering log.
Posts on the shim, the master, and the agents we're wrapping.
- Engineering
Why a coordination layer beats more guardrails
Agents already follow instructions. They just don't follow each other. A shim that intercepts the plan does what review rules cannot.
Read - Architecture
The sentinel pattern: extracting plans from any agent
We needed a structured plan from any CLI agent, with no SDK access. Two strings, one JSON blob, zero brittle parsers.
Read $ tether init $ tether wrap claude → master: localhost:8080 → wrap: claude/4b2e…91af → ready.Field notesWrapping Claude Code: a 10-minute tour
Spin up a local master, point it at a worktree, hand it a session id. The agent starts under coordination on the first keystroke.
Read
Frequently asked.
If you don't find your question, email founders@tetherlab.ai. Real humans, fast replies.
If the agent runs in a terminal, Tether can wrap it. We ship first-class support for Claude Code, OpenCode, Codex CLI, Cursor's CLI, Aider, and Continue. Anything else falls back to a passthrough wrap with manual plan injection.