chat-recall-taskslisted

# The task board with chat-recall The board is shared: teammates and agents on other machines see the same cards. So a card is a claim about real work, and the tools enforce that rather than trusting a status field. ## See the board `mcp__chat-recall__recall_tasks` — one line per card (title, id, assignee). Use it for "what's on the team's plate", "my tasks", or to find a task id. Pass `detail: true` when you intend to actually DO one. That returns the full brief per open card: the fix, the file locations, and the agent prompt the auto-filer already wrote. Reading the brief before starting is the difference between doing the filed work and re-deriving it. ## Create a card `mcp__chat-recall__recall_task_create` — optionally assign it to a teammate and attach it to a project. Returns the new task id. File a card when work must survive the end of the session. A leaked key to rotate, a finding worth fixing, a follow-up the user described out loud — those belong on the board, not in a reply the user has to scroll back to. Never put a real credential in a title or body. Refer to a secret by its redacted preview. See [chat-recall-security]. ## Claim it, then close it — the protocol `mcp__chat-recall__recall_task_update` changes status, assignee, title, links a session and can carry a comment. Two steps are not optional, and the server refuses the call without them: 1. **Starting.** Set `status: 'in_progress'` AND pass your own current session id as `linked_session_id`.