CapitanIA Join the private beta

My coding agents know about all my projects now.

A macOS app for developers with lots of projects. It gives Claude Code, Codex, Gemini CLI, opencode and Kilo Code one shared index of everything you've built, runs their sessions as tabs, and lets them ask each other for help.

Join the private beta

macOS · works with the agents you already use · everything stays on your machine

I have seventy-odd projects on the same handful of services. Every new agent session used to start blind: it saw one repo, rebuilt the auth I already had working next door, and forgot everything when it ended.

CapitanIA is the desktop app I built to fix that. It keeps one index of every project (stack, services, where it runs, how it deploys), hands it to every agent I use, and runs their sessions as tabs.

CapitanIA with three projects open as tabs. The trailhead project shows its builder, nemesis and deploy agents; the builder has just finished a trip planner and run the tests.
One project, three agents: the builder writes the trip planner, the nemesis tries to break it, the deploy agent ships it. Every other project is one click away in the sidebar.

Every session starts knowing what I've already built.

Each agent gets the index of all my projects: stack, services, where each one runs. So when Inkwell needs payments, the agent doesn't invent a new Stripe setup. It finds the one that already works in Trailhead and reuses it.

inkwell ❯ capitania find stripe trailhead ~/code/trailhead sveltekit, fastapi, postgres, stripe ⏺ Trailhead already takes payments with Stripe Checkout (src/lib/checkout.ts, webhook in api/stripe.py). I'll reuse that setup for Inkwell's paid plans instead of starting over.

Agents ask each other instead of asking me.

When the builder needs a dev server, it doesn't stop and wait for me. It asks the Infra assistant, which knows every server and domain I have. The message lands in that agent's terminal, or starts one, and the answer comes back the same way.

trailhead ❯ capitania ask infra "Add dev.trailhead.example.com on the Hetzner VPS, same Coolify app as prod" Sent to the Infra assistant (role "infra"). CapitanIA starts it if needed and types your message in. ⏺ Infra assistant: dev.trailhead.example.com points to the Hetzner VPS and Coolify deploys the dev branch. Recorded in the infrastructure registry.
The sessions graph: projects, the agents working in each, the servers they run on, and the messages between agents in the last day.
Who talked to whom today: a nemesis reporting a bug to its builder, one project depending on another's API, the Infra assistant answering a request.

Every project gets a builder, a nemesis and a deploy agent.

The builder plans and builds. The nemesis reads what the builder made and tries to break it, with tests as evidence; it never edits the product. The deploy agent runs every check and deploys the way the project's written recipe says (target, steps, checks, how to verify), then confirms it's live.

Above them sit agents that work across everything: the Infra assistant for servers, DNS, domains and accounts, and a Marketing assistant that plans launches and asks the builders for landing pages.

Nothing gets lost.

Close the tab, the terminal or the whole app: every session resumes where it left off. Per-project notes keep what the agents learned, so the next session doesn't rediscover it.

It stays on my machine, and nothing speaks for me without my OK.

The index, notes and settings are files on my computer. No telemetry; .env files are never opened, and tokens stay in the system keychain. Before an agent deploys to production, posts or sends anything, it asks me, and I answer with one tap in the app or on my phone.

And a secretary for the rest of my day.

SecretarIA keeps my agenda, briefs me every morning on it and on what the agents did, and answers me on Telegram when I'm away.

  • Anything urgent today?
  • SecretarIAGood morning, Captain. Two things: renew trailhead.example.com (21 days left), and reply to the guide in Moshi about October dates. Shall I draft that reply?
  • Yes. Tell him the 12th works for a group of four.
  • SecretarIADraft: “Hi Joseph, October 12 works for us, a group of four. Could you confirm the price per person?” Send it?

Join the private beta.

I'm letting developers in a few at a time while it settles, on macOS. It will most likely be open source later.

Which coding agents do you use? (optional)

I'll keep your email only to write to you about the beta. To be removed, write to hola@capitania.dev. Privacy

Join the private beta