Agents, approvals and undo
Planner, the QA agent and Triage work inside your workspace. They hold back risky steps, and every run can be undone as one change.
Key takeaways
- An agent can only do what the person who asked it can do.
- Each agent asks before its own big changes, like archiving or changing more than 10 records for Planner. Tick Ask before every change to cover every step.
- A run's edits are one change, so one Undo takes them all back.
Ask an agent
Open Ask an agent from the command palette (⌘K, then Enter asks Planner) or from an agent's page. Pick the agent and the model, add up to 10 pages or tasks as context, and press ⌘Enter. The dialog shows an estimate before anything runs.
Decide what it asks about
Each agent has an Asks before setting that owners change on its page: Big changes or Every change. Big changes are archiving, deleting or changing more than 10 records for Planner, rolling back a deploy for the QA agent, and closing or merging tasks for Triage. Tick Ask before every change in Ask an agent to cover every step of one run.
Planner asks before
Archiving, deleting, or changing more than 10 records.
- Read 42 tasks on the board
- Move 6 tasks to Next sprint
- Archive 14 done tasks
- Write the sprint plan page
When it needs a yes
When a step needs a person, the run waits with that change not made. Approve it and the agent makes the change and goes on; deny it and the run stops.
Undo a run
Every edit a run makes is one change in History, and Undo takes them all back. If someone edited one of those records afterwards, Undo is refused, so their edit is never lost.
Put it on a schedule
On Paid, an agent can run on a schedule, like a weekly inbox sweep. Pause a schedule with its switch, or start it early with Run now.