Codee3 is a desktop IDE each developer installs and runs on their own AI accounts; there’s no team plan today. What the team shares is the project brain: plain Markdown committed in the repository, so every developer’s agents read the same decisions, and changes to them go through your normal review.
What Codee3 is for a team
Codee3 is a desktop IDE that each developer installs on their own Windows computer and runs with their own AI accounts. There’s no team plan, shared seat or admin console today, and each Founder licence key works on up to three computers.
What a team shares is the repository. The project brain is plain Markdown in the repository’s .ai/ folder, so it travels with the code: commit it once and every clone has it, along with every branch and every review.
Why teams want one record of decisions
Put five developers on a project, each with their own agent, and you get five versions of the rules. One person’s CLAUDE.md says one thing, another’s chat said something else last week, and the agents follow whichever they saw last. A decision record in the repository gives every agent on the team the same starting point, and a change to it is reviewed like any other change. That’s how you stop agents drifting across a team; the decision log guide has the format.
How does a team set up Codee3?
- Each developer installs Codee3 and signs in to their own Claude Code, Codex or Gemini CLI. Nobody shares an account.
- One person opens the project, chooses Adopt the Codee3 kit from the command palette, checks what it would add, and starts it. Make sure the
.ai/folder it writes is committed and pushed. - Everyone else pulls. Their agents are told to read the decisions in force before they start.
- When the team settles something, whoever settled it chooses Keep a decision. It’s committed as
Record D-…, so it arrives through your normal review. - Agree as a team who may change or replace a decision, the same way you agree who approves a pull request.
Teammates who don’t use Codee3
Not everyone has to switch. When the brain is set up, Connect your agents adds a marked block to the project’s agent instructions files, such as AGENTS.md and CLAUDE.md, and keeps the rest of each file as it was. An agent that reads those files in another editor or a plain terminal reads where the decisions are too. The Claude Code and Codex guide covers keeping those files in step.
What Founder adds for each developer
- Founder: helpers working at once, each in its own git worktree on its own branch (how that works: run agents in parallel).
- Founder: the brain’s checks, run before a helper’s work lands.
Several helpers at once means several agent sessions on that developer’s plan, which uses its limits faster; heavy use on a consumer plan can be slowed or paused by the provider (see the terms). Work arrives as ordinary branches and commits, with nothing in a format only Codee3 can read. See pricing for what each plan includes.