---
title: Ask and change
description: How to talk to Ysra in a thread — questions, changes, briefs, attachments, dictation, and steering while work is under way.
---

You don't pick a mode. Type what you want in the message box and press
++enter++ (++shift+enter++ for a new line).

## Ask

```text
where do we decide whether an invoice is overdue?
```

A question changes nothing. You get an answer and the files I read to reach
it; click a file name to open it beside the thread.

## Ask for a change

```text
retry failed invoice emails with backoff, at most 5 attempts
```

I read the code, edit it, run your checks, review the result against what you
asked, and report. The change stays in your folder as ordinary edits until you
[commit](commit-push.md) or [undo](undo.md).

Say what must not change as well as what should: *"keep the public interface
as it is"*, *"don't touch the migrations"*.

## Give me 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 I check the work against.

## Attach files

The paperclip attaches files; you can also paste or drop them. Up to 10 files,
25 MB each.

## 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, start the thread with **Plan first** (in the
[trust sheet](open-folder.md#the-trust-sheet)). I write a specification, you
read it, and nothing changes until you choose **Approve & build**.

## While I'm working

The message box says *Steer or ask while it works…* What you send then is
either a question I answer, or a steer I pick up at the next safe point. You
don't need to stop me first.

When I need something from you, the box says *Reply to continue…* and a card in
the thread says what. See [Approvals and auto mode](approvals.md).