Moe's Tavern

An AI agent task board. Turn your coding agents into a team you can steer.

Run Claude Code, Codex, Gemini CLI, and Grok Build through a shared task board in your IDE. Give agents clear roles, review their plans, and follow the work through implementation and QA.

Get started · See the workflow · Features · Claude accounts · Documentation

New on main: Claude account rotation. Sign in each of your Claude subscription accounts once, and Moe moves Claude Code agents to the next account when the active one reaches 90% of a usage window. Workers switch between steps, never mid-step, and the Accounts tab shows every account's 5-hour and weekly usage. See how it works.

One place to see what is planned, what is being built, and what needs review.

Why Moe?

Working with several coding agents means keeping track of their tasks, context, plans, and results. Moe gives that work a shared workflow: you define the outcome, an architect proposes the approach, a worker implements it, and QA checks it against your Definition of Done.

Start with one small task. As you add agents, the same board keeps their plans, progress, conversations, and review feedback together. Choose the coding CLI for each role and decide how much approval you want to retain.

What you get

Moe's daemon and project state run locally, with workflow data stored in .moe/. Your coding agents use their own providers and sign-ins, and Moe never handles their credentials; with account rotation, it only chooses which of your signed-in Claude accounts a new session starts on. Moe is MIT licensed; provider access and usage are separate.

How it works

In the default CONTROL mode:

flowchart LR
    Task[You define a task] --> Plan[Architect proposes a plan]
    Plan --> Approve[You review and approve]
    Approve --> Build[Worker implements]
    Build --> Review[QA checks the result]
    Review --> Done[Done]
    Review -->|Changes requested| Build

For a first task, ask Moe to document your project's setup and test commands. Review the architect's proposed scope, let the worker write the guide, then inspect QA's findings and the Git diff. Use the same workflow for features, bug fixes, and refactors.

Get started

The first-run path below uses JetBrains and one small task. The full walkthrough includes platform details and troubleshooting.

Install a release

Download the plugin from the latest GitHub Release:

• JetBrains — moe-jetbrains-<version>.zip. Open Settings / Preferences → Plugins → gear icon → Install Plugin from Disk, select the ZIP, and restart the IDE.
• VS Code / Antigravity — moe-vscode-<version>.vsix. Install it with Extensions: Install from VSIX, open your target project, then run Moe: Connect to Daemon.

The plugins bundle their own daemon and proxy. You still need Node.js on PATH and one coding CLI (Claude Code, Codex, Gemini CLI, or Grok Build) installed and signed in. After installing, continue at step 2.

JetBrains Marketplace, VS Code Marketplace, Open VSX, and npm listings are not published yet. Claude account rotation arrived after v0.8.0; build from source to use it before the next release.

1. Build from source

Download the source ZIP, extract it, and open a terminal in the extracted Moe folder. You can also clone this repository.

Windows — PowerShell:

powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\install-all.ps1 -BuildPlugin

macOS / Linux:

bash scripts/install-mac.sh --global --skip-mcp --with-plugin

The installer sets up Git, Node.js/npm, package dependencies, the daemon and proxy, the selected agent CLI, and JDK 17 for the plugin build. It also builds the JetBrains plugin ZIP. On Linux, it installs tmux for agent terminals. Existing compatible dependencies are reused.

You need a JetBrains IDE and your platform's package manager: WinGet on Windows, Homebrew and Xcode Command Line Tools on macOS, or apt/dnf on Linux. The script may request administrator access when installing system packages. If a prerequisite cannot be installed, it stops with instructions.

Claude Code is the default. To choose another bootstrap option, append the corresponding flag:

Grok Build is supported by the agent launchers. The Windows installer also accepts -AgentCommand grok; on macOS/Linux, install Grok Build separately.

Keep the Moe folder after installation. Open a new terminal, go to your target project, and run your selected coding CLI once to sign in to your provider account.

Terminal only? Leave off -BuildPlugin or --with-plugin. The installer still puts moe-daemon and moe-proxy on your PATH; run moe-daemon init --project . inside your project to create .moe/ and keep the daemon running in that terminal.

2. Open the board

1. If you built from source: in JetBrains, open Settings / Preferences → Plugins → gear icon → Install Plugin from Disk.
2. Select the ZIP in moe-jetbrains/build/distributions/ and restart the IDE. (If you installed a release ZIP, skip 1–2.)
3. Open your target Git project, then open the Moe tool window. The plugin initializes .moe/ and starts the daemon. Wait for Connected.

The ZIP and .vsix attached to each GitHub Release are built from that release's tag. If you built from source, install the plugin you built so it matches your checkout.

3. Run your first task

1. Open Project Settings and keep Approval Mode: CONTROL.
2. Click + Epic, create an epic such as First task, then use the + in its Backlog column to create a task. Give it a clear description and Definition of Done.
3. Drag the task to Planning. In Agents, choose Architect, then your installed CLI. Architects claim tasks in Planning, so a task left in Backlog will wait.
4. When the task shows Awaiting Approval, open it, read the plan, and click Approve.
5. Launch Worker and QA from the same menu. Keep their terminals open and follow the task through Working → Review → Done.

Open the completed task to inspect its steps, verification results, and QA summary, then review the changed files and recorded commit in Git. By default, the launchers commit task changes and attempt to push them; check any reported Git or verification failure before treating the task as delivered.

Once one task completes, use Agents → All Agents to start the team together. Have more than one Claude subscription account? Add them in the Accounts tab first, so the team can move between them. If a step stalls, use the first-task troubleshooting guide.

powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\moe-agent.ps1 -Role architect -Project "C:\your\project"

./scripts/moe-agent.sh --role architect --project "/your/project"

cd moe-vscode
npm.cmd install
npm.cmd run package

cd moe-vscode
npm install
npm run package

Choose your level of control

Set the approval mode in Project Settings:

Agent review and project rules support your workflow. Inspect the results and keep your normal repository checks and merge protections.

Run Claude agents across several accounts

New on main, not in v0.8.0. Build from source to use it before the next release.

Have more than one Claude subscription account? Sign each one in once, and Moe picks the account each Claude Code session starts on. It fills the accounts in your order and moves to the next one once any usage window of the active account (5-hour or weekly) reaches the switch point, 90% by default.

In JetBrains: in the Moe tool window, open Accounts and click Add.... Name the account, and a terminal tab opens with Claude's own sign-in (claude auth login --claudeai); finish it in your browser. Repeat for each account, put them in order with Move up and Move down, and change Switch to the next account at if 90% doesn't suit you. Then launch agents as usual.

From a terminal, after a source install:

moe-daemon accounts add --label "Personal"   # prints the new id, e.g. acct-1
moe-daemon accounts login acct-1             # Claude's own sign-in for that account
moe-daemon accounts check                    # exits 0 when every account is on a subscription

• No step is cut short. A worker whose account reaches the switch point finishes its current step and ends its session. The launcher restarts the same task on the next account, and the new session picks up at the next step. A QA seat moves at its next launch. An architect or governor terminal moves between tasks: after a plan is recorded, or while it waits on chat, its session ends by itself and the launcher restarts it on the next account.
• Limits are handled for you. If Claude refuses a launch at its limit, the launcher retries on the next account at once. When every account is spent, agents keep their tasks and resume at the earliest reset.
• You always know which account is in use. The Accounts tab shows each account's sign-in, 5-hour and weekly usage, and status. The tool-window header shows the active account, worker cards name theirs, and #governors gets a 🔁 post on every switch.
• Credentials stay with Claude. Each account is its own Claude config folder under ~/.moe/claude-accounts/. Moe creates the folder and hands its path to Claude; it never reads, copies, or stores a login.
• Off until you sign an account in. Until then, or whenever Bedrock, Vertex, or Foundry is configured, Claude launches exactly as before. MOE_ACCOUNT_ROTATION=off turns rotation off. Codex, Gemini CLI, and Grok Build seats are unaffected.

One account list serves every project on the machine. Each account folder takes the place of ~/.claude for its sessions, so add any user-level settings, CLAUDE.md, agents, skills, or plugins your agents rely on to each folder.

Use your own accounts, within Anthropic's terms. Rotation only chooses which of your accounts a new session starts on; it never raises a limit. Pro and Max limits assume ordinary, individual use, and logins may not be shared, so check that your setup fits before relying on it. If you run a large, always-on fleet, API keys or a Team or Enterprise plan are the better fit.

More: rotation rules · environment variables · troubleshooting.

Extend Moe

Moe connects its IDE interfaces and coding agents through a local TypeScript daemon and an MCP proxy. Use the MCP reference and architecture guide to build integrations or understand the runtime.

Customize role guidance and agent skills for your project. Optionally connect Serena for code navigation and shared memory.

Documentation

Role guides: Architect · Worker · QA · Governor.

Contribute

Try Moe on a small task and tell us what worked or got in your way. Report a bug or request a feature, or see the contribution guide to help build it.

License

MIT.