The working timeline
Follow a desktop thread while Ysra works: read the steps and command output, understand the result card, and copy what you need.
On this page
The timeline is the thread itself: every step Ysra takes appears in it as it happens, folded into stretches of work with Ysra’s notes between them. Read it to follow the work, to see why a step failed, or to check what ran. This page explains each part; for the states a task moves through, see How a Code thread works.
Work is folded into stretches, with Ysra’s notes between them.
The rule#
Nothing happens off screen. Each file read, edit, command and check is a step in the thread, and a failed step opens by itself.
Stretches of work#
| While it works | When the stretch ends |
|---|---|
| Working… 18s | One line, such as Worked 42s · read 6 files, ran 2 commands, edited 3 files. Click it to see every step |
An opened stretch: each file read, each command.
Between stretches, Ysra says what it found and what it’s doing next, in plain sentences. They are the quickest way to follow along.
Step tags#
| Tag | What it is | Click it for |
|---|---|---|
| INSPECT | Ysra read a file or searched the folder | The file |
| EDIT | Ysra changed a file | The diff |
| SHELL | Ysra ran a command | The output |
| BROWSER | Ysra opened your app in a browser to check it | What it saw |
| REVIEW | Ysra checked the result against what you asked | The verdict |
| PLAN | Ysra wrote or updated the plan | The plan |
| FAILED | A step failed | Why. It opens by itself |
Live commands#
A running command shows its output as it arrives.
npm test running, with the latest lines of output.
| What you see | Meaning |
|---|---|
| The last 20 lines | Show all N lines opens the rest; up to 2,000 lines are kept |
Ran npm test · passed in 8s |
It finished and passed |
Ran npm test · failed (exit 1) |
It finished and failed |
| A line saying it was stopped | It ran too long, or you stopped the work |
Waits for your OK: npm install |
A card is waiting for you. See Approvals |
The result card#
When a task ends, a card says how:
| Card | Meaning | Buttons |
|---|---|---|
| Your changes are ready | Done. The card shows lines added and removed, and how long it worked | Review changes · Commit… · Commit & push… · Undo changes… · Go back… |
| Didn't work | Done and kept, but the project's checks fail or the app doesn't start. The thread says what failed | The same |
| Stopped | You stopped it. What was done so far is kept | Continue · Go back… |
| Stopped with a problem | Something Ysra couldn’t get past. The thread says what | Continue · Go back… |
| Review finished | A Mayz review ended. No changes to your files | — |
Commit… and Undo changes… appear for a folder on this computer; a thread in Ysra’s cloud shows Open pull request… instead. See Review the diff, Commit and push and Undo my changes.
Copy anything#
Text in a thread can be selected. A Copy button appears on each message, each answer, each code block and each command’s output; it reads Copied for a moment afterwards.
Notifications#
When the app is in the background, your system notifies you:
| Notification | When |
|---|---|
| Ysra needs you: “thread is waiting for your answer.” | Ysra asked something, or a card waits |
| Your changes are ready: “thread finished. Review the changes.” | A task ended with changes ready |
| A thread stopped: “thread needs attention.” | A task stopped with a problem |
Needs you in the sidebar’s panel lists every thread waiting for an answer.
Related#
- How a Code thread works: task states, repairs and limits.
- Approvals and auto mode: the cards that stop a stretch.
- Stop and continue: stopping mid-step, and continuing.
- Review the diff: what to do with a finished change.


