Quick start
Install from the plugin marketplace inside Claude Code:
/plugin marketplace add malcolm1232/WorkBoard
/plugin install board-steward@workboard
Prefer to install from source? git clone it and run ./install.sh — same result, no marketplace step:
git clone https://github.com/malcolm1232/WorkBoard
cd WorkBoard
./install.sh # sets up + auto-detects your projects and bootstraps a board
Requirements: Claude Code · Python 3.9+ (standard library only, no pip install) · macOS / Linux / Windows. No account, no cloud, no API key required. (History Replay's optional bootstrap uses Claude Haiku — the cheapest tier — as a one-time, detached subprocess.)
The problem
| # | Problem | How WorkBoard solves it |
|---|
| 1 | Agent memory is for the agent only — invisible to you. | WorkBoard is a visual knowledge-graph for both users and agents — you see your work as a live board; the agent walks the same graph. |
| 2 | We can't keep track of our code. | WorkBoard tracks live what Claude is working on and what it just shipped — without you typing anything. |
| 3 | You're generating ideas faster than you can act on them. | Card them on the spot — as cards or subtasks. Later, just say "Do #426" — or chain them: "Do #426, #123 and #99." Each one picks up exactly where it was left. |
| 4 | You're getting more done than ever — but how do you remember what shipped, why, which files? | Every card has a title (the gist) and a short description; the deeper work (subtasks, writeup, files, commits) hangs off as leaf nodes. Future Claude reads a tiny digest first and traverses only the leaves it needs — answering "what did we do on OAuth in May?" costs a handful of tokens, not a re-read of every chat log. |
The workflow
-
Every Task is Captured. Before any work begins, the request is captured as a card in the Task column.
-
Immediately know what Claude is working on. The moment Claude starts working on it, the card glides into In Progress and pulsates — so at a glance you know exactly which card it's on. Working on multiple projects at once? WorkBoard knows which board belongs to which project and updates each accordingly.
-
Shipped → Done, with a write-up. Once finished, Claude writes a description of what was done, why this problem existed in the first place, and ✓ a write-up of how it was done. The card flies to Done.
-
Bug? Back to In Progress. If something breaks — or more changes are needed — the card animates back out of Done with a 🐞 bug tag, or with an added subtask if it's just a follow-up.
-
Re-shipped → Done. Once fixed, the card returns to Done — with the full ship → bug → fix → ship arc preserved in its history… ready for traversal.
Features
1. 🏷️ Filter by tag — find what you need fast
When a card is created, it's automatically tagged with the work-type it belongs to (e.g. UI, security, bug, refactor). Click any tag chip to filter the board down to only that slice — answering "what's open on the UI side right now?" in one click.
2. 📅 Calendar View
See what shipped — and what's still open — laid out by date. Catch missed work from yesterday, spot productive streaks, or look back at your wonderful week of progress at a glance! You can use it to show your boss what a Teacher's pet you've been (or not).
3. ✅ Subtasks track the real work, step by step
The live tick. Each card breaks down into the steps the agent will actually take. Subtasks tick off one by one as the work progresses — so even mid-task you can see exactly how far along Claude is (e.g. 2/4), not just "in progress."
