USE
This page assumes LastDB is already installed.
Not there yet? [Install on the home page →]
Brain is long-term memory. Kanban is the work board. Same database, different jobs. Catalog: Apps.
BRAIN = WHY
Decisions, designs, context. Prefer updating an existing note over creating a new one every time.
KANBAN = WHAT’S IN FLIGHT
One card per unit of work. Move it as reality changes. The board is the source of truth for status.
1 Start from the board: kanban list
2 When a decision settles, write it to Brain:
brain concept new caching --title "Cache layer" --body "chose LRU; why: …" brain ask "what did we decide about caching?"
3 Track work as cards:
kanban add ship-login --title "Ship login flow" --tags auth kanban move ship-login doing
4 Keep the split honest: status on the board, reasoning in Brain.
After install (and ~/.last-stack/setup), point the agent at the home page, this page, or llms.txt.
MCP so the agent can read/write Brain and Kanban
brain mcp kanban mcp
Register those as MCP servers in your client (stdio). Or: brain mcp install for Claude Code wiring.
SKILLS
Last Stack skills teach filing cards, driving one card to a merged PR, waiting on CI, and closing out. Refresh:
cd ~/.last-stack && git pull && ./setup
HOW TO WORK WITH YOU
Start from kanban list. Put durable “why” in Brain, not only in chat. One unit of work = one card.
IF IT’S NOT RESPONDING
curl -s --unix-socket ~/.lastdb/data/folddb.sock http://localhost/health
# expect {"status":"ok"}
brew services restart lastdb # only if health fails
kanban listHealth is /health on the Unix socket (not /api/health, and not TCP port 9001).