A bug list Claude Code works through

Claude Code and Pando, for a bug list across sessions.

You find three bugs while fixing a fourth, and they have to wait. Said in the chat, they go with the session: "Each Claude Code session begins with a fresh context window." Auto memory carries notes forward, but one repository at a time, and in Anthropic’s words "Auto memory is machine-local."

Connect Claude Code to Pando and have it write each bug as a todo under a Bugs bullet, with the steps to reproduce it in the note. The next session searches for layout:todo is:incomplete under Bugs, works through what comes back, and ticks each bug it fixed.

Set it up

In a terminal: claude mcp add --transport http --scope user pando https://pando.ink/mcp
Start claude, run /mcp, select pando and choose Authenticate.

With --scope user the server is "available across all projects on your machine". A second computer needs the same two steps once, and its sign-in adds a second agent that starts with your whole outline again. When Pando asks, choose Read and write your outline, or hold it to Bugs as below, which lets it write there either way. Then give every session the habit, in ~/.claude/CLAUDE.md, which Claude reads at the start of every session:

At the start, search Pando for layout:todo is:incomplete
inside this repository’s bullet under Bugs.
File a bug you are not fixing now there, as a todo:
the symptom on the line, the repro steps in the note.
When you fix one, tick it and append the commit to its note.

Anthropic’s docs say Claude treats CLAUDE.md "as context, not enforced configuration", so this is a request, not a guarantee. If a session skips it, ask.

What the list looks like

- Bugs
  - billing-api
    - [ ] Refund webhook retries forever after a 500
          note: Repro: npm test -- refund-retry, or send a refund
                with the stub returning 500 and watch the queue.
                Seen: retries every 2 s, no cap. Consistent.
    - [x] Invoice PDF drops the last line
          note: … Fixed in 4e1c9a2, 2026-09-22.
  - pando-web
    - [ ] Sign-in button does nothing in Safari 17

Only the bug lines have the todo layout, which draws a checkbox on that bullet. Bugs and the repository bullets stay plain. The note carries what Anthropic’s own debugging advice asks for: the command that reproduces it, the steps, and whether it is intermittent or consistent. You can file one yourself by typing [] and a space on an empty line, and tick one with a tap.

The next session

search  q: "layout:todo is:incomplete"  focus: <the repository’s bullet>
update  id: <the bug>  done: true  appendNote: "Fixed in <commit>"

layout:todo is what keeps the list to bugs: is:incomplete alone matches every unticked bullet, plain ones included. Every hit comes back with its note, so the repro steps arrive with the bug. appendNote adds the commit at the end of the note and leaves the steps as they were, and the fixed bug stays in the list, ticked.

The same query works in Pando’s search box: open Bugs and search layout:todo is:incomplete for everything open, or layout:todo is:complete for what was fixed. Open a repository’s bullet to search that repository alone. An operator Pando does not know, such as is:open, is refused rather than answered with an empty list.

What it can reach

A connector you approve on Pando’s consent page starts with your whole outline, read and write or read only. To keep Claude Code to the bug list, open the Bugs bullet, open Agents and API keys in Settings, tap its row under Your agents, and press Let it reach only “Bugs”, the bullet you are in. It then reads and writes Bugs and everything under it, even after a read-only approval, and reaches nothing else, and what it remembers lands under Bugs too. Its old memory bullet stays where it was, out of its reach, so press it only if Claude Code uses Pando for bugs alone.

An agent you create under Agents and API keys with both boxes unticked reaches nothing until you give it a bullet the same way. Its key begins with pf_ and goes in an Authorization: Bearer header, which claude mcp add takes with --header. A protected bullet refuses every change from an agent, but a lock stops changes, not reading.

Where this is not the answer

One repository’s bugs. A file in the repository, which Claude Code reads and edits and git carries to every computer, is enough.
A list that stays on one computer. Claude Code’s own task list does that: "To share a task list across sessions, set CLAUDE_CODE_TASK_LIST_ID to use a named directory in ~/.claude/tasks/". On models its docs do not list, it stays empty unless you opt in, for example with CLAUDE_CODE_ENABLE_TODO_TOOLS=1.
A team’s bugs. They belong in the team’s issue tracker. GitHub Issues let you "assign yourself and teammates to issues", and "using keywords, like fixes:, in your pull requests will automatically close the associated issues". GitHub Projects plan and track work "at the user or organization level".

What this page is for is one person’s list across repositories and computers, in the same outline as the rest of their notes, tickable from the phone without a repository open.

Deeper

Connect an agent, about two minutes · The twelve tools · Which note apps an agent can reach · Who runs this