Work your stax from Claude Code
Partly works today
The HeyStax plugin connects a Claude Code session to the role its folder works as. When a session opens, it tells Claude who it is working as and which cards are waiting. Two commands take those cards and report back to the stax.
Why it matters to you
You open Claude Code at 08:00. You don’t scroll back through yesterday’s chat or paste the card in. Claude already knows it is @timebreez-builder, that two cards are waiting, and what it was halfway through.
Close the laptop mid-card and the card goes back to the role with its last note. Nothing is left stuck as “working”.
Do you need it?
| You want | Use |
|---|---|
| Cards picked up while you are away | Not the plugin. Run heystax listen --install --agent claude in the folder. Connect a worker. |
| Claude to take cards in a session you are watching | The plugin: /heystax-work or /heystax-loop. |
| Work you start yourself to show up on the stax | The plugin’s standing order, or just heystax connect (it writes the same order for Codex). |
Install it
- Connect the folder first: Connect a worker, steps 1 to 3.
- In a terminal, add the HeyStax repo as a plugin source:
claude plugin marketplace add Hulupeep/tabstax. - Install it:
claude plugin install heystax@heystax. To update later, runclaude plugin marketplace update heystax, thenclaude plugin update heystax@heystax. - Open a new session in the connected folder. The first thing Claude sees is the role and what is waiting.
Check it any time with /heystax-connect. It says who this session works as, and what to do if the folder is not connected. It never asks you to paste a key into the chat.
What it does
| When | What happens |
|---|---|
| Session opens | Claude is told which role and stax this folder works as, the standing order, any card already open in this folder, and how many cards are assigned to the role. If the owner paused the role, it is told not to pick up new cards. |
/heystax-work | Takes the oldest card assigned to the role, claims it, does it, and reports: notes with the branch and PR as it goes, blocked if it needs a person, done with a one-line result. |
/heystax-loop | The same, card after card. Waits up to 50 seconds for each new card. Stops after 10 cards (or the number you give), or after about 8 minutes with no work. |
| You start your own work | The standing order makes Claude put it on the stax first (heystax task start), then note and finish it there. |
| Session closes | A session summary goes on the card: what was asked, what changed, the result, what is next, and the branch and PR. A session with no card that changed files gets a done card of its own. Then an open card is handed back to the role, so another worker can pick it up and read what happened. |
Claude only ever runs the heystax command, and heystax reads its own key. No key enters the chat.
Sam goes to lunch
Sam types /heystax-loop 3 and leaves the session open. Claude works three cards in a row. One needs a price decision, so Claude marks it blocked with the question and moves on. The question waits on the card, not in a scrolled-away chat.
When it goes wrong
| You see | What to do |
|---|---|
| “this folder is not connected” | Run heystax connect in a terminal in that folder, not in the chat. |
| “the heystax CLI is not installed” | Install it once: Connect a worker, step 1. |
| “The owner has paused this role” | The role is paused on the board. Unpause it there, or leave it. |
| Cards wait but nothing happens while you are away | The plugin only works in an open session. Use heystax listen --install. |
Coming next
Planned Install from a public plugin directory, without a copy of the HeyStax repo.
Now you can open Claude Code and start on the right card, and every move lands on your stax under the role’s name.
Read next: Connect a worker to a role · Roles, workers and their keys