pi-task-board
v0.1.0
Published
Project task boards for pi-agent: panels, four-column tasks, and sessions that belong to one task.
Maintainers
Readme
pi-task-board
Project-level kanban for pi: multiple panels per project, four columns of tasks, and sessions that belong to exactly one task.
The ledger remembers. You enter the room. The model keeps the books and never opens the door.
Install
pi install npm:pi-task-board
# or
pi install git:github.com/<user>/[email protected]
# or, while developing this repo
pi install ./Quick test without installing:
pi -e ./extensions/task-board/index.tsUse
/board— open the task that owns this session, or the last panel/board panel— list / create panels/board panel <name|id>— open that panel; offer to create if missing/board new <name>— create a panel and open it/board T-12— open that task/board open T-12— switch to that task's newest session/board attach [T-12]— attach this session/board detach— detach this sessionCtrl+Shift+B— same as/board
Enter on a session closes the board and switches to that chat.
Ask the agent to list or attach tasks; it uses the task_board tool.
A session can belong to only one task. The agent can change the ledger. Only you can change rooms.
Layout
Project 1 ── N Panel
Panel 1 ── N Task (Backlog / To Do / In Progress / In Review)
Task 1 ── N Session
Session N ── 1 Task (a chat belongs to at most one card)V1 has no Done column. A finished review either moves or deletes the task. Session files are never deleted — only the reference is detached.
The footer shows where you are:
Board login-rewrite · T-3 · 2s
Board login-rewrite · unbound
Board 3 panelsData
The only source of truth is:
<cwd>/<CONFIG_DIR_NAME>/task-board.jsonUsually .pi/task-board.json. Conversation bodies stay in ~/.pi/agent/sessions/.
Security
This extension reads and writes <cwd>/.pi/task-board.json and can call
switchSession from /board. It does not read the board file on an untrusted
project. Review the source before installing, same as any pi package.
License
MIT
