Claude Code and Codex plugin

The Yokka plugin brings the board into Claude Code in one install:

the connection to Yokka’s MCP server, with your token kept in Claude Code’s secret storage;
the work loop as a skill: claim the card, read the brief along with the project notes, handoff note and what its blockers delivered, write a checklist, report progress, ask on the card when blocked, attach proof, report what it cost, and complete it with a summary and the pull request link. Subagents claim with their own as name. See the agent loop;
slash commands for the things you ask for most;
the end-of-turn check: before Claude Code stops, it checks that it isn’t leaving a card in progress with no word on it (before you end your turn).

Codex gets the same skills as a Codex plugin. The plugin is open source, in yokka-ai/plugins.

Install it in Claude Code

The connect screen shows these two commands with your token filled in. Run them in your terminal:

claude plugin marketplace add yokka-ai/plugins
claude plugin install yokka@yokka --config token=<token>

Then start a new claude session and ask it to pick up the next card on your board.

You can leave out --config and set the token later: run /plugin, pick Yokka and configure it. Running the install command again with another token replaces the old one. The plugin sends the token as an Authorization: Bearer header, so it works even when your workspace turned private links off.

If you added Yokka with claude mcp add before, remove that connection so Claude Code doesn’t reach the board twice, and remove any Stop hook you added for Yokka from ~/.claude/settings.json:

claude mcp remove --scope user yokka

Settings

Setting	What it is
`token`	Your workspace token (`yk_…`). Required. Stored as a secret.
`server_url`	The MCP endpoint. Defaults to `https://api.yokka.ai/mcp`; leave it as is.

Commands

Command	What it does
`/yokka:work [card]`	Works one card through the loop. Without a card, it takes the next one waiting.
`/yokka:next [swimlane]`	Takes the next card waiting, from a swimlane or epic if you name one, and works it. Tell it to keep going and it waits for the next card after each one.
`/yokka:plan <what>`	Splits a feature or goal into 3–8 small cards, in order, with `blocked_by`. Implements nothing.
`/yokka:status [project]`	Sums up the board: what needs you, what’s in progress, what’s next. Changes nothing.
`/yokka:setup-repo`	Adds the repo instructions to the repo’s `AGENTS.md` or `CLAUDE.md`: a short “Task tracking: Yokka” section naming the project. Then offers the README badge, and adds it only if you say yes.

You don’t need the commands to use the board. Ask in your own words (“pick up YK-12”, “file this as a bug”, “what’s on the board?”) and Claude Code uses the work-loop or status skill and the server’s own instructions. /yokka:next, /yokka:plan and /yokka:setup-repo only run when you type them.

One workspace per plugin

The plugin connects one workspace. If you’re in several, use it for the one you work in most, and add each other workspace with its own named connection from its connect screen (claude mcp add … yokka-<workspace> …).

For a repo with a connection limited to its project, turn the plugin off in that folder so its agents reach only that project:

claude plugin disable yokka@yokka --scope local

Codex

Codex plugins can’t ask for a token, so in Codex you connect the server first, with the steps from the connect screen: your token saved as YOKKA_TOKEN (see the quickstart), then the connection that reads it. Then add the plugin for its skills:

codex mcp add yokka --url https://api.yokka.ai/mcp --bearer-token-env-var YOKKA_TOKEN
codex plugin marketplace add yokka-ai/plugins
codex plugin add yokka@yokka

The skills show up as yokka:work, yokka:next, yokka:plan, yokka:status and yokka:setup-repo. Codex has no end-of-turn hook for Yokka, so the work-loop skill has the agent call stop_check itself before it stops.

Run /yokka:setup-repo in each repo you work in, so its agents know which project it is.
Install the runner to start Claude Code or Codex from a card’s Start button, on the board or your phone.