Start a thread
Start a Code thread in the desktop app, choose where it runs and how much Ysra may do on its own, and change those options later.
On this page
A thread is a conversation about one piece of work, on one folder or repository. You start one by typing what you want and pressing Enter: there is no dialog to fill in. This page is for anyone starting work in the desktop app. It covers where a thread can run, the options in the message box, and the folders Ysra won't use. For what happens once it runs, see How a Code thread works.
Steps#
- Open the message box: on Home, under the greeting; or New thread at the top of the sidebar’s panel (Cmd+N, or Ctrl+N on Windows and Linux), which shows What do you want to build?. The + beside a folder or a device in the sidebar opens the same box with that place chosen.
- Check Where on the line under the box. Click it to choose another place. See Where.
- Type your request (the box reads Ask Ysra to build…) and press Enter.
The thread starts with that message. The options start from sensible defaults, and your choices are remembered for each workspace.
The message box#
Everything sits in one row inside the box, and a quiet line under it says where the thread runs.
| In the row | What it does |
|---|---|
| Do | Code (“Works on the code and shows you every change”) or Mayz review (“Reads the project and reports what to fix, with evidence; changes nothing”). A review adds Look at: Everything, Security, Code quality or Design. See Mayz reviews |
| + | Attach files (“Or paste or drop them in the box”), Colleague (No colleague, or one of your workspace’s colleagues), and, for a folder on this computer, Subagents: up to six read-only investigation roles that work in parallel |
| Access | Auto, Asks first or Read only, plus the Plan first switch. See Access |
| The model | The mode and its model, such as Forge · …, or a model you picked and its effort. It reads Loading… until the list arrives. See Code modes and models |
| The microphone | Dictate instead of typing. See Dictate |
| The round button | Send. While Ysra works and the box is empty, it becomes Stop. See Stop and continue |
@ in the box mentions one of your files, an Ask conversation, another
thread, a routine or a colleague. When the workspace has no colleagues, + says
No colleagues in this workspace yet.
Access#
| Choice | What it says | Use it when |
|---|---|---|
| Auto | “Works through without asking; still asks before deleting, deploying or system installs.” Shown in orange. See auto mode | You trust the work inside this folder |
| Asks first (the default) | “Asks before commands and changes.” | You want to OK each piece of work |
| Read only | “Reads and explains; changes nothing.” | You want to explore or understand code |
| Plan first (a switch) | “Writes a plan for you to approve before any change.” See Plans | The change is large and you want to read the plan first |
The last access you chose is the default for your next thread. With Settings → General → Auto mode for new threads on, new threads start in Auto. See Access modes.
The line under the box#
| Part | Shows |
|---|---|
| Where it runs | Local for this computer, on device for one of your devices, or Ysra cloud |
| Where | The folder, repository or New cloud project. Click it to choose another; it reads Choose a folder… when there isn’t one yet |
| The branch (a Git folder with commits) | Work on branch, or A parallel copy on a new branch (“Its own folder, so it can’t collide with other threads here”) |
| No Git (a folder without Git) | Work without Git, or Set up Git here…. See Folders without Git |
| Cloud environment (Ysra cloud only) | The cloud machine, such as Default · Trusted. See Cloud environments |
When the folder hasn’t been used on this computer before, a note under the box says what sending will also do: First thread in billing-service: sending trusts this folder on this computer. Trust is remembered for the app and the CLI alike.
Where#
Where opens one list, with its search box ready for typing (“Search folders, devices and repositories”):
| Group | What it lists |
|---|---|
| This computer | The folders recently used here |
| Ysra cloud | New cloud project (no repository needed; Ysra keeps its files between turns), then your GitHub repositories. Shown on a plan with cloud |
| Each of your devices | The folders it shares, with a dot for its state. An offline device still lists the folders it shared last time, marked offline |
| Other folder… | Any folder on this computer |
| Connect GitHub… | Shown when cloud is on but no repositories are connected |
The places you picked most recently come first. Type to filter (Nothing matches “…”. when nothing does), use the arrow keys to move, Enter to pick and Esc to close.
| Where | Runs on | Needs this app open? |
|---|---|---|
| A folder on this computer | This computer, contained to the folder | Yes. Closing it pauses the work |
| A folder on a device | The device, which runs ysra serve |
No |
| A repository or cloud project in Ysra cloud | A cloud machine of its own | No |
A cloud thread shows a one-time notice before your first one, uses credits for its machine time as well, and delivers a repository’s change with Open pull request… instead of a commit. See Code in Ysra’s cloud.
Change options inside a thread#
The same row sits in the message box inside a thread: + for files and the colleague, the access, the model, the microphone and Send. A change applies from your next message, and the thread notes it:
| You change | The thread says |
|---|---|
| The model, effort or access | From here on I’ll work with: high effort, a plan first. |
| The colleague | I’m working with the “Billing reviewer” colleague from here on. |
Work already running keeps the options it started with.
The top of a thread#
Under the thread’s title, one quiet line says how it is going: ● Running while Ysra works, then the mode and its model (or the model you picked and its effort), then what the thread has used, such as 12 credits. Point at the credits for the time as well: “Worked for 6s · 12 credits used in this thread”.
Beside the title, a chip shows when there is something to say:
| Chip | Meaning |
|---|---|
| Folder connected | The app is connected to the folder on this computer |
| Opening this folder… / Reconnecting to this folder… | On its way |
| Folder not connected · retry | Click it to reconnect. See Lose the connection |
| hardware allowed, such as GPU allowed | On a device, you allowed this thread to use that hardware |
| Docker: allowed for this session · Revoke | You allowed Docker for this thread. See Docker |
The buttons at the top right open panes beside the thread: Files (the thread’s files, read only), Preview (the app being built; see Try the change yourself) and the review.
Ysra’s own record of your changes#
Ysra keeps its own history of the changes it makes, outside your folder: in
~/.ysra, the folder the app shares with the CLI. That history is what lets
it show the diff, review the work and undo exactly.
- Ysra never adds a
.gitfolder, or anything else of its own, to your folder. - It never writes to your repository’s own Git history to keep its record.
- It never commits unless you ask, with Commit… or by saying so; not even a first commit in a repository with none. See Commit and push.
Folders without Git, and folders inside a repository#
Any folder works as it is. Nothing is asked when a thread starts, and nothing is created in the folder.
| Folder | What happens |
|---|---|
| Without Git | Works. Diff, review and undo work from Ysra’s own record; the folder stays without Git. Commit… isn’t offered |
| A repository with no commits yet | Works the same way. No first commit is made |
| Inside a larger repository | Ysra works only in that folder and never touches the repository around it. To commit to the repository, start the thread on its own folder |
Set up Git yourself#
For a folder without Git, the line under the box reads No Git. Choose
Set up Git here… (“Your own history: a .git folder and a first commit”).
A dialog asks Set up Git in this folder?: the folder gets a .git folder
and a first commit of what’s in it, and a repository around it is not
changed. Choose Set up Git, or Cancel; Ysra works on the folder
either way.
Folders Ysra won’t use#
| Folder | Ysra says |
|---|---|
| Your whole home folder | Your whole home folder can’t be opened. Pick the project folder inside it. |
A whole disk (on Windows, C:\ or a share’s top folder such as \\server\share) |
A whole disk can’t be opened. |
| A system folder | That’s a system folder. Pick a project folder. |
| Ysra’s own data folder | Refused the same way |
Where it is available, Settings → Code → Let Ysra look at this computer opens your home folder or the whole disk to answer questions about the computer; it only looks, and nothing there is changed.
Other ways to open a folder#
| System | How |
|---|---|
| macOS | Drop a folder on the Ysra icon in the Dock |
| Windows | Right-click a folder and choose Open in Ysra |
| Any | Cmd+O: a new thread in a folder you pick |
If it doesn’t work#
| Symptom | See |
|---|---|
| The folder isn’t listed, or … isn’t on this computer anymore. | Troubleshooting: a folder isn’t shown |
| No Ysra cloud in Where, or a cloud thread won’t start | Troubleshooting: a cloud thread won’t start |
| I can’t run commands on this computer yet | Troubleshooting: commands are blocked |
Related#
- Ask and change: what a message does once the thread runs.
- Access modes: Auto, Asks first, Read only and Plan first.
- Approvals and auto mode: what each access choice lets through.
- Code in Ysra’s cloud: cloud threads and environments.
- Devices & machines: threads on your own servers.