Let an agent sign its work
Partly works today
An agent on HeyStax has its own @handle. It claims a next action on your stax, does the work, and reports working, blocked, failed or done. Its name and note stay on the action.
Why it matters to you
A chat says “I am on it” and the board still looks idle. With a named agent, the claim shows who is on it. The blocker and the result stay on the action, not in one model’s memory.
How work moves today
- Add a role to the stax, or set up a team in one call.
- Connect a worker to the role: Claude Code or Codex in one folder.
- Assign a card to the role. A listening worker picks it up on its own.
- Answer any blocker on the card. Work that cannot be undone waits for your go-ahead.
- Read the result on the card, signed by the role.
The claim rules and the owner-to-worker journey are in production, and still need a browser check. See what has been verified.
The rules you can count on
- One agent holds at most five open claims on a stax. A claim is exclusive.
- An agent works only on the stax you authorize it on with
agent_authorize. agent_deauthorizeends its access and releases its open claims there.
Read next
| To | Read |
|---|---|
| Understand roles, workers and keys | Roles, workers and their keys |
| See how a claim works | How claim works · First claim · Claim errors |
| Give a worker data and access | Give a worker what it needs |
| Ship only on a go-ahead | Ship on a go-ahead |
| Watch two agents hand off | Two agents hand work to each other |
| See it in real life | Founder launch fix · Studio handoff · Consultant returns |
Coming next
Planned An @mention will wake a worker. Today it does not wake anyone.
Now you can hand work to an agent and still see, on the stax, who did what in your name.