Turn intent into durable work
Jobs remain visible through restarts, dependencies, and handoffs. They are not buried inside one transcript.
CCC Captain · powered by WatchTower
Give one agent a goal. WatchTower gives it a crew.
Stay in Claude or Codex. Captain turns your request into durable jobs, sends each one to the right coding-agent context, waits for verification, and returns the proof.
No new chat surface. No model picker. Start where you already work.
One goal in. A verified result out.
The work becomes visible only after you delegate it.
The terminal remains the control surface. Captain reveals the jobs, contexts, dependencies, and evidence behind the request.
CCC Captain · demo repository
Loading walkthrough
C
F
Q
T
I
·
Claude Code · existing session
Ship the mobile navigation fix. Reuse context, verify it visually, and bring me proof.
shaping the goal into bounded jobs
filing durable WatchTower work
reusing the session that knows the navigation
starting an independent verification lane
returning proof to this session
Captain · live operation
Mobile navigation
- Goal receivedOne bounded outcome entered in the existing session.
- Plan shapedThree jobs and one dependency identified.
- Implementation filedThe responsive navigation fix becomes durable work.
- Verification filedDesktop and mobile behavior get a separate owner.
- Warm context reusedThe navigation session already knows the affected files.
- Verification lane startedA separate worker owns browser evidence.
- Review waitsThe dependent job does not race implementation.
- Verification runningTests and responsive browser checks are in progress.
- Jobs resolvedImplementation, verification, and review completed.
- Receipt returnedThe initiating session receives the evidence.
✓ Receipt returned
Resolution summary · commit proof · tests · responsive screenshots
0s / 45s
Recorded walkthrough. Demo repository data. No models run in your browser.
The completion loop
Activity is not the outcome.
Captain is built around the work returning to the initiating agent with enough evidence to trust it.
Use context before creating more
Reuse the session that already understands the code when it is the right home. Spawn a worker when independence matters.
Return evidence, not confidence
Resolve with a summary plus commit or no-code proof, and the tests or screenshots the job requires.
Not another place to chat
The agent is still the interface.
Your Claude or Codex session operates WatchTower through skills and the wt CLI. CCC is where invisible execution becomes inspectable. Open it to intervene, not to copy and paste the conversation.
WatchTower is the durable runtime
Queues, workers, dependencies, messages, waits, learnings, and resolutions.
CCC Captain is the control plane
Shape the request, see the crew, inspect evidence, and intervene when judgment is needed.
Start with one real job
Give your current agent a durable crew.
Install CCC for the visual control plane, or use WatchTower directly from the terminal.