- Per-action credits you watch drain
- Inference billed at a markup on top of the model
- Cost scales with anxiety, not just usage
- Cloud-locked: pay to keep access to your own work
The Chief of Staff you own
Decide. Delegate. Through the gate.
Cloud agents are horizontal, credit-metered builders you rent and watch. Chief of Staffs is different: a local-first, gate-governed Chief of Staff named Eden. It runs on your machine, asks before anything you cannot undo, and re-checks the result before you trust it.
- Sovereignty
- Local-first. Your code never leaves your machine.
- Governance
- A gate that blocks before anything irreversible.
- Predictable cost
- Bring your own model. No credit meter.
Work routes through the gate. Nothing irreversible slips past unseen.
How it works
One loop, end to end.
You set the outcome and it runs the loop: decide the goal, delegate to the right role, hold at the gate, then verify the result before you rely on it. Decide. Delegate. Through the gate.
- 01
Decide
You name the outcome and the success criteria. It does not start work until the goal is clear.
- 02
Delegate
It routes the work to the right role (recon, build, review) instead of grinding everything in one thread.
- 03
Gate
Anything irreversible halts first. It asks before it does what you cannot undo.
- 04
Verify
A finished result is a claim, not a fact. It re-checks the work against evidence before you rely on it.
01 / Sovereignty
Your code never leaves your machine.
Cloud agents lift your repository into someone else's runtime and meter you for the privilege. Chief of Staffs runs local-first. The work, the files, and the memory live where you do. You are not renting access to your own project.
Memory is file-native and git-diffable: every fact, decision, and handoff is a plain file you can read, review, and own. There is no opaque vector store you cannot inspect and no vendor lock on the thing that knows your work best.
- Local-first execution. No upload of your repository to run.
- File-native memory you can open, diff, and version in git.
- You own it. Portable, inspectable, yours to keep.
02 / Cost
Predictable cost. No inference markup.
Bring your own model and your own subscription. There is no credit meter ticking behind every action and no per-token surcharge stacked on top of what you already pay. The anxiety of watching a balance drain is not part of the deal.
- Bring your own model or subscription
- No credit meter, no credit-burn anxiety
- No inference markup layered on top
- Predictable: you already know what you pay
03 / Governance
Trust by gate, not by watching.
You should not have to babysit an agent to keep it safe. Chief of Staffs asks before it acts on anything you cannot undo, and re-checks the result before you trust it. Two gates do the governing, so you do not have to.
01 Blocks
The plan-gate
Before it acts
Anything irreversible halts first. The gate names the outcome, the success criteria, the blast radius, and the data-safety constraints before a single destructive step runs. It asks before it does what you cannot undo.
02 Re-verifies
The adversarial gate
After it acts
A finished result is a claim, not a fact. The gate re-verifies the work against the goal before you rely on it: evidence is demanded, the result is re-checked, and a shaky claim is rejected rather than handed to you as done.
A chief of staff, not a fleet to assemble. You do not build a team and hope. You have a chief of staff that decides, delegates to the right role, and stands accountable at both gates.
04 / Memory
A Chief of Staff that remembers. Correctly.
Most agents forget between sessions or quietly accumulate contradictions. Chief of Staffs is built on a memory engine modeled on the four kinds of human memory, kept in plain files you own.
Working memory
Continuity that survives a context reset. It picks up exactly where you left off, no re-briefing.
Semantic memory
Facts and decisions that supersede cleanly. It never holds two contradictory truths at once.
Procedural memory
How you like things done, learned once and reused.
Episodic memory
A dated trail of what happened. Auditable, in plain files, not an opaque store.
File-native and git-diffable. You can read it, diff it, and own it. No vector store you cannot inspect.
FAQ
Questions, answered straight.
Is my code uploaded to the cloud?
No. Chief of Staffs is local-first. The work, the files, and the memory stay on your machine.
Which model does it run on?
Bring your own. It uses the model you already pay for, with no markup layered on top.
What does it actually cost?
Predictable. You pay for your own model or subscription. There is no credit meter and no per-action surcharge.
Is it safe to let it act on its own?
Two gates govern it. The plan-gate blocks before anything irreversible. The adversarial gate re-verifies a finished result before you rely on it.
How is its memory different?
It is modeled on the four kinds of human memory and kept in plain, git-diffable files you own, so it remembers correctly instead of drifting.
What is a founding seat?
A limited early place. Founding members shape the roadmap, lock in founding terms, and get hands on the gates first.
Founding members
Take a founding seat.
A limited number of founding seats open first. Founding members shape Eden's roadmap, lock in founding terms, and get hands on the gates before anyone else. This is for operators who want a Chief of Staff they own, not an agent they rent.
- Direct line into the roadmap
- Founding terms, held
- Early access to the gates