Planban v1.1.6

Planban v1.1.6, released on 26 September 2026, adds Claude Code desktop support, makes the agent's board-link handoff work the same way in every host, and resolves boards from linked git worktrees.

This release makes Planban feel native in Claude Code desktop. Codex behaviour is unchanged.

What is new for Claude Code?

  • Planban installs as a Claude Code plugin, from GitHub or from a local clone, with claude plugin marketplace add piercekearns/planban and then claude plugin install planban@planban. See Install Planban in Claude Code.
  • The six commands are /planban:pb, /planban:planban, /planban:planban-create, /planban:planban-help, /planban:planban-tutorial and /planban:planban-feedback.
  • The board opens in the Claude Code browser pane beside the session. Every open, and every material change, ends with the clickable verified board URL.
  • A session-start hook tells Claude when the current project tracks its work in Planban and where its board is.
  • The Planban runtime resolves correctly when Claude Code runs the plugin from its cache, as it already did for Codex.
  • Every MCP result from creating or changing Items, and from planban_status and planban_get_board, now carries boardUrl, boardUrlVerified and a ready-made userReply link. Agents in any host can return the board link without the skills installed.
  • Results of changes are compact: they report itemCount instead of every Item, which keeps large boards well within host output limits. planban_get_board is still the full read.
  • The MCP server's instructions to the agent now state the essential rules: one change at a time, Complete only when you say so, one attempt to show the board per batch of changes, and the clickable link in the final reply.
  • The pb, planban, planban-create, planban-help and planban-tutorial skills and the protocol share one path for every host, with separate steps for Codex desktop, Claude Code desktop and other hosts.
  • A project's generated .planban/agent-context.md and the managed AGENTS.md block now give the board URL, the Planban tool names, the handoff rule, and what an agent should do when Planban is not installed for its host: say so once, point to the install steps, and carry on.

See the MCP tools reference.

What changed for git worktrees?

  • Sessions that run in a linked git worktree, in Claude Code desktop or Codex, now open the board owned by the repository's main checkout, even though .planban/ discovery files are usually ignored by git. Discovery never looks above the top of the repository.
  • planban_status and the CLI's status report requestedCwd and discoveredVia when this happens.

See Planban in git worktrees.

How do I update to v1.1.6?

Dependencies are unchanged, and existing boards keep their storage format, so no migration is needed. Refresh the marketplace and reinstall the plugin so the cached skills and hook scripts update, then start a new session. See Update Planban for the commands in each host.

To pick up the new generated guidance in an existing project, run set-up again with the project's board id.