Moe's Tavern

An AI agent task board for Claude Code, Codex, Gemini CLI and Grok Build

New Run agents across several Claude accounts →

View on GitHub Get Started

Features

Kanban Board

Visual task management directly in your IDE. See what AI agents are working on at a glance.

Plan Approval

Review and approve AI implementation plans before any code gets written.

Multi-Agent

Run architect, worker, QA, and governor agents with distinct roles and tools.

MCP Protocol

Agents connect through the bundled MCP proxy. Claude Code, Codex, Gemini CLI, and Grok Build are supported out of the box.

Real-time Sync

Live updates via WebSocket keep all clients synchronized instantly.

Rails System

Define constraints that AI must follow at project, epic, or task level.

New Claude Account Rotation

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.

No Step 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.

Limits Handled

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.

Credentials Stay with Claude

Each account is its own Claude config folder, signed in through Claude's own login. Moe never reads, copies, or stores a credential.

Set it up

In JetBrains, open the Moe tool window's Accounts tab and click Add.... A terminal tab opens with Claude's own sign-in; finish it in your browser. The tab then shows each account's 5-hour and weekly usage. From a terminal:

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

New on the main branch: build from source to use it before the next release. Read the full guide.

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.

Architecture

    +------------------+     +------------------+     +------------------+
    |  JetBrains IDE   |     |    AI Agents     |     |   Other CLIs     |
    |    (Plugin)      |     | (Claude Code...) |     |                  |
    +--------+---------+     +--------+---------+     +--------+---------+
             |                        |                        |
             | WebSocket              | MCP (stdio)            |
             |                        |                        |
             v                        v                        v
    +--------+------------------------+------------------------+---------+
    |                         Moe Daemon                                 |
    |                    (WebSocket + MCP Server)                        |
    +-----------------------------------+--------------------------------+
                                        |
                                        | Read/Write
                                        v
                              +---------+---------+
                              |    .moe/ folder   |
                              |  (source of truth)|
                              +-------------------+

Key Principle: The daemon is the sole writer of .moe/ files. All clients communicate through the daemon.

Getting Started

Install a release: download the plugin from the latest GitHub Release: moe-jetbrains-<version>.zip for JetBrains IDEs, or moe-vscode-<version>.vsix for VS Code and Antigravity. The IDE plugins bundle the daemon and proxy; you still need Node.js and a coding CLI (Claude Code, Codex, Gemini CLI, or Grok Build). JetBrains Marketplace, VS Code Marketplace, Open VSX, and npm listings are not published yet.

Build from source: download the source ZIP, extract it, and open a terminal in the extracted Moe folder. The installer handles missing dependencies, installs your coding CLI, and builds Moe and the board plugin. Build from source to use Claude account rotation before the next release.

Use a JetBrains IDE for the board. Automatic dependency installation supports Windows with WinGet, macOS with Homebrew and Command Line Tools, and Linux with apt-get or dnf. It may request operating system permission to install system packages.

Windows

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

Mac / Linux

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

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.

Open the board and complete a task

  1. Install the release ZIP, or the ZIP you built in moe-jetbrains/build/distributions/, through your IDE's Plugins → Install Plugin from Disk menu, and restart. Run your CLI once to sign in. Open your target project and its Moe tool window; wait for Connected.
  2. Keep Approval Mode: CONTROL in Project Settings. Click + Epic, then use the + in its Backlog column to create one small task with a description and Definition of Done.
  3. Drag the task to Planning. Choose Agents → Architect → your CLI.
  4. When the task shows Awaiting Approval, open it, read the plan, and click Approve.
  5. Launch Worker and QA from the Agents menu. Keep their terminals open.
  6. Follow Working → Review → Done, then inspect the verification result, QA summary, changed files, and recorded Git commit.

Moe's launchers commit task changes and attempt to push them by default. Review any reported Git or verification failure before treating a task as delivered.

Follow the full first-task guide for exact commands, CLI selection, PATH fixes, and troubleshooting. GitHub Release assets are built from the release tag; if you build from source, install the plugin you built.