Share the same auth, config, and domain types. Reach for whichever matches the task.
Scriptable CLI for automation, CI/CD, and AI workflows. Strict grammar, typed exit codes, structured JSON / markdown output, machine-readable help.
plnk card find --title "bug" --board $BOARD --output json
Live tree explorer for projects, boards, lists, and cards. Single-board websocket subscription for real-time updates. Edit titles inline, descriptions in $EDITOR.
plnk-tui --server $PLANKA_SERVER --username you
Released 2026-04-26.
Press y on any selected node to copy its full ID hierarchy to your system clipboard as compact JSON. Press Y for a paste-ready plnk <resource> snapshot --output json command with a breadcrumb comment. Built for handing context off to an AI agent in one keystroke — works locally, in tmux, and over SSH via OSC 52 with no native clipboard dependency.
Build from source today. Prebuilt binaries are on the roadmap.
Requires a Rust toolchain (1.87+). Tested against self-hosted Planka.
Release binaries with a curl | sh installer are tracked on the
roadmap.
Planka already does kanban well. plnk wraps it in a tight, typed surface agents and scripts can drive.
project → board → list → card. Every find demands a scope. No global flat queries, no surprising results.
table for humans, json for scripts and agents, markdown for reports. JSON is a strict projection of the serde model.
Scripts branch on 0 success, 2 validation, 3 auth, 4 not-found, 5 server. No stderr parsing.
plnk <cmd> --help --output json emits a schema agents can bind to before ever running a command.
One board live at a time. Edits from the browser appear in the terminal in near real time. No polling, no drift.
plnk-core is usable on its own. Build your own Planka integration in Rust without depending on the CLI.
No account service to sign up for. No config files to hand-edit. You already have a Planka instance — plnk just talks to it.
Grab plnk and optionally plnk-tui with cargo install.
Run plnk init. Prompts walk you through server URL, API token, and optional HTTP tuning. Both binaries share the same config.
I use a self-hosted Planka for everything — technical and non-technical.
What I care about is the artifact. By the time a card hits Done, it contains what I did, the decisions I made, and why.
Many tools in this space are building AI task managers — AI sub-agent drivers, new kanban boards, TODO.md skills, bolting MCPs onto various products. For me, Planka already solves the fundamentals: UI, hierarchy, self-hosting, and a working API. Replacing that felt unnecessary.
I was already driving agent workflows through the REST API. It worked, but it was inefficient — lots of curling, constructing large JSON payloads, and chaining calls for simple operations like finding a card by name. Hard to read, token-heavy, and noisy in the agent's context.
I didn't go the MCP route either. Others are doing it, it inflates context, and I've found it slow.
So plnk doesn't replace Planka — it wraps it in a strict, predictable interface. It reduces token usage and keeps the agent's context lean: the surface is learned on demand through plnk <cmd> --help --output json, not preloaded at session start.
It exposes Planka as a disciplined CLI and SDK — tight grammar, typed exit codes, structured output, strict hierarchy, machine-readable help. Give an agent a rigid surface, and it stays on the rails.
plnk-tui started as an experiment — a live terminal explorer for the same hierarchy, sharing plnk's config and auth. It's fit into my terminal-driven workflow better than I expected, so I'll keep expanding it.