Use case · By situation
Keep your next session from starting over
For people managing their own projects with agent help.
You return to a side project and cannot remember which approach worked or what you meant to do next. Keep a Work task for the change. Write the next action, add source links and leave a comment describing the result before ending the session.
On your own
Resume the side project change
- 1
Next action
Re-run the failing check recorded in the last session
- 2
Context
Purpose of the change
- 3
Evidence
Last result and source links
What to put in the task
- Assign the task to the person responsible for the next action.
- Add evidence links and explain what they show in a comment.
- Update the task when the work changes so the next reader has the current state.
Before you rely on it
Command interception depends on your client's hooks or proxy; see the setup guide for Claude Code, Codex, Cursor and other MCP clients.
- Work must be enabled for your account. Context from other tools is not captured automatically, and moving between accounts does not promise to transfer your history.
- Work must be enabled for the selected account, and you need permission to read or change the task. Security access and device setup are separate.
Related use cases and clients
By riskSecrets and env filesThe next person can see which configuration changed and who handled it without asking for the secret in chat.By situationA new teammateThe teammate can see what to do next and where the task context came from.By clientCursorSetup requirements for Cursor.
All use cases →