Ask and change
Ask questions and request changes in a desktop thread, attach files, dictate, use a colleague, answer Ysra's questions and steer the work.
On this page
A message in a thread is either a question Ysra answers from the code, or a change Ysra makes in the folder; you don’t pick a mode. Type in the message box and press Enter (Shift+Enter for a new line). This page covers what each kind of message does, and what you can add to one; for the options in the box itself, see Start a thread.
The rule#
Only a change starts paid work. When it’s unclear whether a message asks for a change, Ysra treats it as a question.
Question or change?#
| You write | Ysra treats it as | What happens |
|---|---|---|
| “where do we decide whether an invoice is overdue?” | A question | An answer and the files Ysra read. Nothing changes; click a file name to open it beside the thread |
| “retry failed invoice emails with backoff, at most 5 attempts” | A change | Ysra reads the code, edits it, runs your checks, reviews the result against what you asked, and reports |
| A question and a change together | A change | The task answers the question in its reply |
| “show me the preview” | Preview only | The preview starts. Never a task, never charged |
Asking for a change is the go-ahead: the work starts directly. (If your workspace's owner turned on Ask before paid work, the first change shows Start paid execution? once.) The change stays in your folder as ordinary edits until you commit or undo.
Tip
Say what must not change as well as what should: “keep the public interface as it is”, “don’t touch the migrations”.
Give Ysra a brief#
Type @ to pick a file from the folder. A lone @brief.md (Markdown or
text) sends it as a brief: checklist items and anything under “Acceptance
criteria” become the points Ysra checks the work against.
@ also mentions your own things: an Ask conversation, another thread, a
routine or a colleague. See
Mention your own things.
Attach files#
+ → Attach files in the message box attaches files; you can also paste or drop them. This works in the box on Home too, before the thread exists.
| Limit | Value |
|---|---|
| Files at a time | 10 |
| One file | 100 MB |
| Types | PDF, Word, PowerPoint and Excel files, CSV and TSV, Markdown, text, HTML, JSON, RTF, and images (PNG, JPG, WebP, GIF) |
| What you see | Meaning |
|---|---|
| The file’s chip shows progress | It is being read; a long scan can take a few minutes |
| handbook.pdf is 140 MB. The most one file can be is 100 MB; split it and upload the parts. | Refused before anything is sent |
| The chip says why it can’t be read | Unreadable, or an old format such as .doc (save it in the newer format) |
See Files you can upload for how Ysra reads them.
Dictate#
The microphone button records; click again to stop. The text lands in the message box for you to edit before sending. The first time, your system asks whether Ysra may use the microphone.
Plan first#
For a larger change, choose Plan first in the message box’s access control (see Access). Ysra writes a read-only plan; nothing changes until you choose Approve & build. See Plans.
Work with a colleague#
Choose a colleague under + → Colleague in the message box: one of your workspace’s colleagues, or No colleague. The chosen colleague shows as a chip in the box’s row; its × works without it again. The change applies from your next message, and the thread notes it: I’m working with the “Billing reviewer” colleague from here on. Colleagues are set up under Team on the rail.
When Ysra asks you something#
| What you see | What to do |
|---|---|
| A card headed Needs your input, with options as buttons and …or reply below. | Pick an option, or reply in the box. The card then reads Answered and the work goes on |
| The box reads Reply to continue… | Ysra waits on a card above; see Approvals |
| A notification: “…” is waiting for your answer. | The thread is listed under Needs you in the sidebar |
While Ysra is working#
The message box reads Steer or ask while it works…. What you send then is either a question Ysra answers, or a steer it picks up at the next safe point. You don’t need to stop it first. To stop it, see Stop and continue.
Related#
- Start a thread: where it runs, access, the model.
- How a Code thread works: how a message is classified.
- The working timeline: following the change as it happens.
- Approvals and auto mode: what Ysra asks before doing.