Steering and saved points
Steer, answer, stop, continue or undo a Code task, or go back to a saved point, and see what happens in each case and when undo is refused.
On this page
Steering is changing what a running Code task does without restarting it; a saved point is an exact saved version of the work that a task can resume from or go back to. Use this page when a task is heading the wrong way, when you want to stop or continue it, or when you want to undo what it did. The states a task goes through are on How a Code thread works.
The rule#
Nothing done is thrown away by stopping. The change, the saved points and everything that was checked are kept in every case; going back restores an exact earlier version, byte for byte, and never re-creates old work from a description.
What you can do#
| Action | When | What happens |
|---|---|---|
| Steer | The work is heading the wrong way, or you know something Ysra doesn’t. | Type in the thread while it works (“Steer or ask while it works…”). Applied at the next saved point; up to 3 messages can wait at once. |
| Answer | The task is in Needs your input. | Pick an answer on the card or reply below it. The same task carries on. Answers never change the scope. |
| Stop | You want it to stop now. | It stops at a safe point. The work so far is kept. |
| Continue | The task ended Stopped or Stopped with a problem. | It carries on from where it stopped, with the same goal and the same change. |
| Allow | It asks to install something, or to do something outside your computer. | Approve once on the card. See Approvals and auto mode. |
| Undo changes… | You don’t want what the task did, on your computer. | Changed files go back, created files are removed. See Undoing a task. |
| Go back… | A later change made things worse. | The work returns to an earlier saved point. See Going back to a saved point. |
| Ask about the evidence | You want to understand a result. | Answered from what was recorded (“why did the test fail?”), read-only. If an answer uses credits, Ysra asks first. |
Steering a running task#
Steer early and specifically:
Use the existing
DateRangetype rather than a new one.Don’t touch the checkout module — the bug is in the cart.
| Situation | What happens |
|---|---|
| A steering message arrives | It waits for the next saved point, then applies. Nothing restarts. |
| A fourth message while 3 wait | Refused: “Three steering messages are already queued; wait for a checkpoint.” |
| You go back to a saved point while messages wait | The waiting messages are dropped; send them again if they still apply. |
Stopping and continuing#
| Situation | What happens |
|---|---|
| You stop a Queued or waiting task | It stops at once. |
| You stop a Working task | It finishes its current step, then ends Stopped: “Stopped at your request.” The changes are kept. |
| You close the desktop app or the CLI mid-task, on your computer | The work pauses; Ysra can only work on a folder while the app runs there. It picks up where it stopped when you return. |
| You press Continue | A new task starts from where the last one stopped, and fixes what went wrong. |
| Credits ran out | The task paused before its next paid step. Add credits, then tell Ysra to continue. |
In the desktop app, stop with the round button in the message box (it reads Stop while Ysra works and the box is empty) or Cmd+.; see Stop and continue. In the CLI, see Stopping and pausing.
Undoing a task#
Undo changes… is offered on a finished task in a folder on your computer. Ysra asks first, naming the files: it puts back each changed file exactly as it was before the task started and removes the files the task created. Your own changes elsewhere stay as they are.
| Situation | What happens |
|---|---|
| Nothing was edited since the task ended | The files go back; the task is marked undone. |
| You edited one of the task’s files since | Refused, for every file: “Some of the files I changed were edited after I finished, so undoing would throw those edits away. I left everything as it is.” |
| The changes are already committed | Refused: “These changes are already committed on …, so undoing them means a new commit that reverses mine; I don't do that on my own.” |
| The task is still working | Refused: “I'm still working on this. Stop me first, then I can undo my changes.” |
| It changed no files | “I haven't changed any files, so there's nothing to undo.” |
| Already undone | “I already undid these changes.” |
When undo is refused because you edited a file, use Go back… instead, or revert the file yourself. See also Undo my changes.
Going back to a saved point#
A saved point holds the change, the plan, what was checked and the conversation so far. Tasks make them as they go: after implementation steps, after checks, after review. A thread keeps up to 32.
Go back… on a finished task returns the work to an earlier saved point. Ysra asks first, then says: “Went back to saved point N. Affected checks will run again.”
| After going back | Detail |
|---|---|
| The files | Exactly as they were at that saved point. |
| The checks | Checks and reviews that ran later no longer count: they described different code. The restored version is unchecked until they run again. |
| Steering messages still waiting | Dropped. |
| What next | Steer, run the checks again, or deliver. |
Saved points are also what make a task safe to interrupt: resuming after a stop continues from the latest one, and a lost machine is picked up again from one. See Go back to an earlier point.
When a task stops by itself#
| Situation | How it ends |
|---|---|
| Credits run out | Pauses before its next paid step: “I stopped at the limit set for this work. Your changes and what I checked are kept; add credits or raise the limit, then tell me to continue.” See When credits run out. |
| No progress | The task ends and says what blocks it. |
| The same check keeps failing the same way | Ends and says what blocks it. |
| It needs a decision only you can make | Needs your input. |
| Something outside the code failed (a revoked permission, a service down) | Waits for the outside change instead of rewriting working code. |
| The request is declined | Tried another way once; if that is declined too, it ends with a plain message. ysra exec exits with 4. |
| The task reaches 4 hours (less in the cloud on some plans) | Ends cleanly and keeps the change. |
A materially different instruction is usually all it takes to continue.
Related#
- How a Code thread works — every state and what is kept.
- Stop and continue — the same actions in the desktop app.
- Undo my changes — undo, step by step.
- Review and verification — what the checks after going back prove.