See what a worker reads before it starts
Partly works today
When a worker takes a card, it gets the card’s history before it writes a line: what was said, what was tried, and who said it.
Why it matters to you
Gaia reports a bug in Telegram on Monday. By Wednesday it has two cards, three Claude Code sessions and a note from the Chief. A worker that claims the next card at 02:00 used to start blind.
Now the worker reads that history first. You did not paste your context. It was already yours, and it travelled.
What the worker reads
| Part | What it holds |
|---|---|
| The card’s notes | Newest first. Forty runs that all say “still blocked” become one line with a count. The first diagnosis and the latest note are always kept. |
| The reporter’s words | The Telegram report, with the message it answered and the screenshot link. |
| Session summaries | Five lines from each Claude Code session that worked the card or a related one. |
| Related cards | Cards on the same stax that share an issue number or two title words, plus the role’s latest cards. |
| Code history | PRs named on the card or matching its title, recent commits and branches. Read with git and gh in the worker’s own checkout. |
Each item says who wrote it and when, and links to where it came from. It is history, never orders. It stays under 8 KB, so the oldest and least related items are dropped first.
How to use it
- Connect the worker’s folder. See Connect a worker.
- Install the HeyStax plugin where you work in Claude Code, so your own sessions leave summaries.
- Assign the card to the role. The listener’s agent runs
heystax task showfirst and reads all of it. - To check it yourself, run
heystax task show <card>in the repo folder. - A worker over MCP calls
work_nextinstead. One call takes the next card with its brief and history.next_actions_contextreads the history of any card. - A worker’s key lists only the tools for its job: 12 for a builder, not 108. To see everything it may call, use
https://dash.heystax.ai/api/mcp?profile=full.
Scenario
Alice finds half the cause in Claude Code and closes the laptop. Her session leaves five lines on the card, with her branch. At 02:00 @timebreez-builder reads Gaia’s report and Alice’s summary, opens her PR and finishes it. Nobody explained anything twice.
What works today
| Step | State |
|---|---|
| Card history with folded repeats, Telegram report, related cards | live, read from a real card on 13 Nov 2026 |
work_next | live. heystax listen uses it from CLI 0.5.3, which runs from the repo: one call takes the card, and heystax task show reads it with no extra call. Measured on a real card: 2 calls instead of 7, 69% less to read before work. |
| A tool list sized to the job | live: a builder’s key lists 12 tools, not 108 |
| Session summaries from Claude Code | released 13 Nov 2026 with the HeyStax plugin, which is partial; not yet seen on a card |
Code history in heystax task show | released in the CLI, not yet seen end to end |
Every answer, in full Partly works today
A long trail of notes used to push the Chief’s reply out of the 8 KB history, so a builder asked again. From CLI 0.5.6, run from the repo, heystax task show prints every question and every comment a person wrote, whole, with the ones for this role marked. It is not on npm yet, and not yet seen on a real card.
Now you can hand a card to any worker, at any hour, and it starts where the last one stopped.