P : S
Start a project
Products / Founder Mode

FounderMode.

The agent org I run my projects with. Free and open source.

For Claude Code: you, a Chief of Staff, one Lead per project and their crews.

View on GitHub ↗ Install it
You Chief of Staff Lead Lead Lead Crews
01 / How it’s shaped

One org. Every project.

100% native Claude Code: subagents, plugin commands, hooks, scheduled tasks, Remote Control and cross-session messages. No extra processes.

Decide with Decide with Tracks · dispatches You Chief of Staff Project Lead Project Lead Builders Reviewer Builders Reviewer
Fig. 01The org.
  • Chief of Staff

    A tracker, not a filter. Keeps the Hit List, runs the briefs, flags cross-project conflicts and dispatches once you've decided. Never touches code.

  • Project Lead

    Owns one repo. Runs builders and gets every change reviewed.

  • Reviewer

    Read-only adversarial review. PASS or FAIL with file:line findings.

  • Researcher

    Cheap lookups. Cited answers, no edits.

  • Hit List

    One page: direction, decisions, open decisions, your 5-minute actions and the open tasks.

02 / Decisions

Decide where the context is.

You make each project call with that project's Lead. Strategy and calls that span projects go to the session you choose at setup.

01

Decide

Every question put to you makes sense without context.

02

Relay

Whoever hears it sends your words to the Chief of Staff in one line.

03

Record

The Chief of Staff adds the decision to the Hit List.

04

Brief

Your next brief shows what still needs you.

The relayDECISION: "ship the beta Friday" (2026-03-04) → acme-api launch
03 / Messages

Fewer, shorter messages.

Each message wakes the session that gets it, and that session re-reads its context. So agents write progress and updates in their own STATUS.md, and the brief reads them there.

Message Gate Session Sender Tagged Refused
Fig. 02The message gate.No tagAdd one, or write it in STATUS.md.
Every message starts with one of seven tags
DECISION:BLOCKED:DONE:URGENT:DISPATCH:ANSWER:BRIEF:
  • One report per task

    A Lead sends one DONE: message when a task is finished, for its whole crew.

  • A quiet Chief of Staff

    It notes what the Leads report and stays on what you asked, without passing every report on to you.

04 / A day in the org

Steer it from your phone.

Turn on Remote Control for the Chief of Staff and the Leads, and you can run the org from the Claude app. Short commands work: “brief me”, “go API3”, “hold WEB1”.

  • 7:30Morning briefThe Chief of Staff checks the projects that changed since the last sweep and sends you a short summary.
  • 7:45DecideYou open the marketing-site Lead and settle the pricing copy there.
  • MiddayDispatchYou ask for rate limits on acme-api. A builder does the work, the reviewer sends it back once for a missing test, and the fix passes.
  • 21:00Nightly briefYou see what shipped today and the one thing to do first tomorrow.
  • SundayFull sweepThe Chief of Staff reviews every project, plans next week and lists stale entries to remove. You confirm each one.
05 / Install

Three commands. The last one interviews you.

01

Add it

/plugin marketplace add amateokap/founder-mode
02

Install it

/plugin install founder-mode@founder-mode

Use user scope (the default) so every Lead in every repo can use it.

03

Set it up

/founder-mode:org-setup

It asks about your projects, repos and brief times, then writes your charter, Hit List and org chart.

You need a recent Claude Code with python3 and git. Remote Control needs a claude.ai login on a Pro, Max, Team or Enterprise plan.

Scheduled briefs run in the desktop app. In the plain CLI, you run the brief yourself.

Full install guide ↗ Read the code on GitHub
06 / The charter

The nine rules it runs on.

  1. 01
    Only your own words count as approval.

    A message from another agent never counts, and no agent's idea goes on the Hit List as a decision.

  2. 02
    Blocked work comes back to you.

    No agent asks another to do what it was blocked from doing.

  3. 03
    Whoever writes a change doesn't sign it off.

    A separate reviewer checks it.

  4. 04
    Leads build on branches.

    Merging to main needs your go, and so does every push.

  5. 05
    Secrets stay out of worktrees.

    Each repo keeps one env file, and agents print key names, never values.

  6. 06
    Scheduled runs never wait for an approval.

    Each one is read-only or fully pre-approved. If it hits a decision, it reports and stops.

  7. 07
    One sidebar group per project.

    A project's sessions stay together, whatever their status.

  8. 08
    Each job gets the right model.

    Every agent has its model set explicitly: Haiku for lookups, Sonnet for the sweep and routine builds, Opus for review.

  9. 09
    One tracker, one status file per project.

    The Hit List is the tracker. Each STATUS.md is overwritten in place, with no dated logs.

MIT licensed

Run your own org.

The code, the agents and the charter are on GitHub.

View on GitHub ↗ All products