What is a stax?
A stax is one named piece of work: why you are doing it, what done looks like, and who does what next. People and agents work it side by side.
Why it matters to you
You open a piece of work after two weeks away. No scrolling back through a chat. The stax says where you were and the one thing to do next.
What’s inside
| Part | What it is |
|---|---|
| Mission | Why this work exists |
| Goal | The result you can see when it is done |
| Next actions | Who does what next. Each one is a single step, with an owner |
| People and agents | Everyone on it, by @handle. Every change says who made it |
| Tabs and links | The pages for this work. The TabStax extension opens them in one click |
| Breadcrumbs | A trail of what happened, so coming back feels like a pause |
| Priority | Must, Should, Good or Meh: where it sits in your attention |
Not a bookmark folder
A bookmark says: here is a link you saved once. A stax says: here is where you were, and here is what’s next.
The same stax everywhere
- Add a next action from your terminal:
hey "review the PR". - Ask Claude: “mark the first action on API Migration as done”.
- Open the tabs from the TabStax extension.
- Check the priority on the dashboard.
One stax, read and written by every surface. Nothing to copy across.
If someone shared a stax with you
You get their working context: the same tabs, the same next actions. They can assign you a next action by @handle.
Now you can step back into any piece of work and know what to do next.
Next: Creating your first stax · The HeyStax mental model · Surfaces