v1.1.6GitHub

Menu

InstallFeaturesHostsDocsFAQKeep up to date

Your agents' plan, in plain sight.

Give your agents real work: features, bugs, releases, research. Planban is the live board where they scope it, plan it, build it, and keep it current as they go, so you always see where every project is up to and what needs you.

Install with CodexInstall with ClaudeDesktop only. Works with Codex and Claude.

Every Item, tracked as it happens.

An Item is a feature, a bug, a release, a piece of research. Your agents scope it, plan it, build it, and keep its card current while they do. You see where it is and what needs you, the moment it changes.

Following one ItemImport Items from GitHub issuesP1
  1. AgentScoped
    Pending
    Spec written: purpose, scope, acceptance.

    From a note or an issue.

  2. AgentPlanned
    Up Next
    Plan: 3 phases, owner gate after phase 1.

    Only when the work needs one.

  3. AgentBuilding
    In Progress
    Phase 2 of 3. Runs behind a flag.

    The blue edge means an agent is on it now.

  4. YouNeeds you
    In Progress
    Owner: try it on a real repo, then ship or revise.

    One next action says what to decide.

  5. YouDone
    Complete
    Shipped in v1.2. Accepted by you.

    Only you mark it Complete.

Planban does not write the code or make the plan. Codex and Claude do. Planban is the always-accurate picture of that work, living beside you and your agents, kept true in real time.

Prompt to install,to open.

  1. 1Ask your agent to set it up

    One prompt installs Planban and opens the interactive tutorial, in Codex or Claude.

  2. 2Open the board from any thread

    Type /planban in Codex, or /planban:pb in Claude Code, to bring the board to any thread.

  3. 3Keep the work structured

    Use Items for independent outcomes. Use Groups when several Items contribute to one larger outcome.

Install with CodexInstall with ClaudeDesktop only. Works with Codex and Claude.
or
Paste this to Codex:
Install Planban from piercekearns/planban. Follow the Install With Codex details in the public GitHub README exactly, verify the plugin and MCP tools work, open the interactive tutorial in the Codex in-app browser, then ask whether I want to set up Planban for a local project.

One board for the whole project.

Every outcome is an Item with a Status, a summary, a next action, and its own Spec and Plan. Related Items become a Group whose progress you can read at a glance. Nothing lives only in a chat transcript.

Planban / Next release
In Progress 2
Import Items from GitHub issuesP1
Import runs behind a flag on the import branch. Owner: try it on a real repository, then decide whether to ship or revise.
Add keyboard shortcuts for moving ItemsP1
Shortcuts call the same move operation as drag. Verifying focus handling after a move.
Up Next 1
Board search and filtersP1
Search by title and idIn Progress
Filter by tag and StatusIn Progress
Keep filters in the URLComplete
Pending 4
Export a Board to MarkdownP1
Show Group progress on the Main BoardP2
Add a History tab to Item detailsP3
Archive and restore BoardsP2

Talk to your agents. The board stays true.

Your agents do the work. Planban keeps the picture true. Agents are trusted editors of the plan; you own intent, priority, and acceptance.

You say"Build the GitHub import, then hand it back for my review."In Codex, in Claude, or in any MCP host. One sentence, no ticket to fill in.
The agent doesScopes it, plans it, builds it, and keeps the card current as it goes.Spec, Plan, Status, summary, and next action, written by the agent, not by you.
You seeWhere it is, what is stuck, and what needs your decision, live on the board.You steer from the board or the conversation. Only you mark work Complete.

Bring your plans where you work.

Start from repo docs, issues, Notion pages, Linear tickets, Jira work, copied notes, or a plain-language update. Ask your agent to turn that context into draft Planban Items and Groups. Review them before they become your working plan. No native integration is required.

From context to ItemsTurn scattered planning inputs into independent outcomes with clear titles, summaries, priorities, Specs, and next actions.
Nothing lands until you approve itDrafts arrive as Pending Items with a summary and a proposed priority. Accept, edit, or discard them before they become the plan.

Local and agent-readable.

Structured commands, a local API, MCP tools, and readable files support the same planning model. A drag on the board and a tool call from an agent run the same operation and write the same history.

CLI, API, and MCP

The CLI gives agents stable local commands for setup, Status changes, moving Items into Groups, and documents. The API and MCP expose the same structured actions, so the UI is not the only way to manage the board.

Local state

Repo discovery stays in `.planban/`; live board state stays on your device, readable and writable by you and local agents.

Portable references

Copy Reference puts one line on the clipboard: the Item's title and its planban: id. Paste it into any Codex or Claude thread and the agent resolves the board, Status, Spec, Plan, and next action instead of rediscovering the project.

Where it runs.

Planban runs in Codex and Claude Code today, and any MCP host can use the same tools and open the board as a link. Online Mode, remote access to your own board, is in design.

Codex desktopAvailable

Board in the in-app browser. /pb, /planban, /planban-create.

Codex guideClaude Code desktopAvailable

Board in the browser pane. /planban:pb and friends.

Claude Code guideAny MCP hostVia MCP

Same tools; the board opens as a link. Cursor and others fit here.

MCP host guide
Online ModeIn design

Remote access to your own board. Local Mode stays complete and permanent.

Questions.

What is Planban?

Planban is a local-first, agent-native Kanban board that installs as a plugin in Codex and Claude Code, so your agents keep the plan current and you see the whole project at a glance. Agents write and update Items, Specs, Plans, and next actions. You own intent, priority, and acceptance.

Which agents does it work with?

Planban works with Codex and Claude today. In the Codex desktop app the board opens in the in-app browser with /pb, and in the Claude Code desktop app it opens in the browser pane with /planban:pb. Both installs share the same boards on your device.

Where is my planning data stored?

Your planning data stays on your machine. Live board state lives under ~/.planban, separate from your repo, and only small discovery files sit in .planban/ in your project. Planban does not upload your boards.

Is Planban free and open source?

Yes. Planban's local core is open source under the MIT licence, and the code is on GitHub at piercekearns/planban. It is not published on npm; you install it from GitHub as a plugin.

Does it replace Linear, Jira, or Trello?

No. Planban is built for one person directing project work with agents, not for team project management, sprints, or reporting. If you use those tools, you can ask your agent to turn their context into draft Planban Items for review.

Does it work offline?

Yes, once it is installed. The board, local API, and MCP server run on your machine against ~/.planban. Installing and updating need access to GitHub, and the open board checks GitHub for new versions when it can.

Can other MCP hosts use it?

Yes. Any host that can run a local stdio MCP server can use the same Planban tools by pointing at plugins/planban/scripts/start-planban-mcp.mjs in a clone of the repo. Those hosts have no slash commands, and the board opens as a link.

How do I install it?

Ask your agent to install it with one prompt from the README, or run the commands yourself. In Claude Code the key commands are claude plugin marketplace add piercekearns/planban and claude plugin install planban@planban, and in Codex they are codex plugin marketplace add piercekearns/planban and codex plugin add planban@planban. Planban needs Node.js 22.12.0 or later, and the full steps are on the Codex and Claude Code pages.