Captain Code runs Claude Code, Codex CLI, Cursor and the API models you connect. Gouvernail is the desk where you see those captains and answer the decisions they cannot make alone.
Lantern, a sample notes app. Scripted walkthrough · example agent picks · nothing here runs
Notes · this sessionApplication · waiting on the export
captain · ~/lanternbrain · local
Lantern · CSV exportscripted demo
LanternSample notes app. Export the notes. Keep the date format the tests already expect.
›
Chapter 1 of 6 · Ask
Ask in plain words.
No command to learn. Captain Code chooses who works.
1 / 13
Space play · ← → step · j k · choose a chapter · illustrative picks, not a live brain
Scripted walkthrough. The fleet is in development. Nothing on this page runs your agents.
01 / A captain for each project
Close a terminal. Keep the thread.
Your project is more than the window it runs in.
Captain Code keeps the agents, the tests and the task. Gouvernail keeps the project’s purpose and backlog, and shows which captain needs you. A captain can run on your computer, on a private server or in the cloud.
AI agentsCaptain CodeBacklog cursorNeeds you
Northstar workspaceInteractive concept · sample data
Captains
Notes · Private server
Choose a data source for the export
Source B covers 14 more markets than source A. It also costs more per month.
✓Collect sources
✓Compare coverage
→Choose a source
·Write the note
Use source B? Recommended: yesWaits for a person
Application → NotesWhich data source covers the export?
Notes → youDecision: use source B?
Application → DocumentationQueued until the tests pass
A product preview. These controls change this example only; they do not run or approve work.
02 / Decisions with their reasons
Less watching. Better steering.
Every update says what was done, what was learned, what is left and what is still uncertain. When a step needs you, your captain brings a recommendation and the reason for it. Usually you can decide without asking a follow-up question.
Compared both sources on the markets the export needs.
Learned
Source B covers 14 more markets. Source A costs less.
Left
Update the export, then its documentation.
Uncertain
The price of source B after the trial is not confirmed.
Why this recommendation?
The application cannot ship without those markets. The switch is one setting, so you can reverse it next month. The captains cannot settle this alone, because it changes what you pay.
Next: Application updates the export ↗
03 / Captains work together
They coordinate. You break ties.
Related projects depend on each other. Your captains can ask each other for help, so you no longer carry every message between them.
01
A captain asks another captain
Application asks Notes which data source to use. The request goes through Gouvernail with its sender, a hop limit and a budget.
02
Questions get answers
Read-only questions, and test runs inside the agreed scope, go ahead without you.
03
Changes wait for a person
A push, a release, a deletion or spending above the limit comes to you as a decision.
04
You break the tie
When captains disagree, or the next step is unclear, you get one question with a recommendation and its reason.
Planned. A captain’s workers cannot forward messages themselves. The captain routes a request, and only to projects you linked.
04 / Clear responsibilities
Connected work. Distinct authority.
The target architecture separates the conversation, the execution, and the permission to reuse work.
01
Gouvernail
People & decisions
Your institution’s workspace. Reach your captains on the web and WhatsApp, start captains in the cloud, and answer the questions that need you. Gouvernail does not run the agents.
02
Captain Code
Work & evidence
Models, workers, tests and task budgets. Open source, and it works on its own, with or without Gouvernail. captaincode.ai ↗
03
Collaboration
Contributions & repair
Track the inputs that work relies on. When an input changes, find the affected results and the repair they need.
A delivered message is not permission. A passing test is not approval.
05 / When shared work changes
Pause what depends. Nothing else.
Work shared between institutions stays connected to its inputs. When a partner withdraws an input, the work that builds on it pauses. Work that only cites it gets a notice. Unrelated work continues.
A captain prepares a repair in a sandbox. A person approves the exact repaired result before it is released.
Northstar workspaceInteractive concept · sample data
P
PARTNER INSTITUTIONComponent captainReleased · v2
Cloud
↓ builds on↓ cites
AYOUR INSTITUTIONApplicationBuilding on v2This computer
NYOUR INSTITUTIONNotesCites v2Private server
↗ Documentation captain Independent · continues
The next step
A shared result, with its inputs attached.
The application captain builds on a partner’s released component. A research note only cites it.
✓Record inputs
→Check impact
·Prepare repair
·Review and release
Run compatibility checksWithin the agreed project scope
A product preview. These controls change this example only; they do not run or approve work.
06 / Meet your work where it lives
At your desk. Away from it.
Focus in the terminal. See the whole fleet on the web. Answer short questions on WhatsApp.
Start a captain in the cloud from the web when a project needs one. Cloud captains use your organization’s API accounts. Personal subscription logins stay on your own computers.
Remote code and test runs are planned to use an OpenShell sandbox. If no sandbox is ready, the task waits or is refused. It never falls back to your computer.
WhatsApp is for low-risk answers. A push, a release, a deletion or spending above the limit needs a stronger approval.
Notes needs a decision (K7Q2): use source B for the export? Recommended: yes. Reply 1 = yes · 2 = no · why. Expires 18:00, then no.
why
The application cannot ship without the 14 extra markets. The switch is one setting to reverse.