Use Ysra Code to change, fix or build software on your computer, a device or Ysra's cloud — where it runs, what it may do on its own, what a thread and a task are, and how a task ends.

On this page

Ysra Code is the part of Ysra that writes code: you give it a goal and a place to work, and it reads the code, changes it, checks the change with your project’s own commands and an independent review, and hands you the change to keep. This page is for developers starting with Code: where it runs, what it may do on its own, the words it uses and how a task ends. To have a project reviewed without changing it, use Mayz reviews; the details of each state are on How a Code thread works.

Where Code runs#

Where Start it from Works on See
Your computer The desktop app or the CLI A folder, with or without Git Start a thread
One of your devices The desktop app or the CLI A folder on a server, a VM or an edge device Devices & machines
Ysra’s cloud The web app, the desktop app or the phone A GitHub repository, or a new cloud project with no repository In Ysra’s cloud

On the phone, Code starts and follows threads on a repository, a folder on one of your computers or a new cloud project; see Mobile app. Code threads on your computer don’t appear in the web app; threads in Ysra’s cloud do.

  • Ysra Desktop

    Work on a folder in a window: the timeline, the diff and approvals.

  • Ysra CLI

    The same work from your terminal, and on servers and edge devices.

What Code may do on its own#

Each thread has an access mode, set from the Access chip under the message box and changeable at any time:

Access What Ysra does
Auto Works through without asking; still asks before deleting, deploying or system installs.
Asks first Asks before commands and changes. The default until you pick another.
Read only Reads and explains; changes nothing.

Plan first, a switch in the same menu, has Ysra write a plan for you to approve before any change. Your last choice becomes the default for your next thread. See Access modes.

Two things in the web app shape every Code thread: your rules and instructions and your settings.

What Code uses#

When What it can use
Replying in the thread Read-only: the project’s files, web search, reading a page, the real browser, PDFs from a link, Ysra’s docs and your connected tools. “What’s in this folder?” or “open this link” is answered straight away, without starting a task.
Working on a task Project files and commands, a preview, the app test browser, screenshots of the app it built, web research and the real browser, PDFs from a link, Ysra’s docs, route links, up to 6 made images, saved web images, and your connected tools, in every task. Publishing and deploying wait for you.

The browser it tests with, the browser it reads other sites with, and watching either:

Browser What it is for
App test browser Clicks through the app the task built, to check it works. Screenshots of the built app are checked by default, so a page that looks broken is seen, not only one that fails.
Real browser Opens other websites (a business’s own site, a library’s docs, a page you linked), runs their scripts and reads them. Read-only, isolated, never your own browser. Its time is charged with the work.
Watch Lets you see Ysra’s browser live while it works.

See What Ysra can do for every part’s tools.

Words Code uses#

Word What it is
Thread A conversation about one piece of work in one place: its messages, plans, steps, credits used and results.
Task One change you asked for in a thread. Each runs to an end state.
The change Everything a task changed in the files. Every check is tied to one exact version of it. Nothing is committed or pushed until you say so.
Saved point An exact saved version of the work. A thread keeps up to 32, to resume after an interruption or go back. See Steering and saved points.
Deploying Putting a change live. A separate step, only after you say yes. See Publish or Deploy and Deploy from your computer.

Task states#

State What it means
Queued Waiting for a machine or a slot.
Working Reading, changing and running commands.
Needs your input Ysra asked something; the same task continues when you answer.
Checking The change is made and the checks run. A failed check is repaired and checked again.
Done The work is built and the project’s own checks pass. Anything worth knowing comes as a short note.
Needs you A question or approval is waiting, or part of what you asked is still to build: say go on and Ysra continues.
Didn’t work The result doesn’t work yet: a check fails or the app doesn’t start. What failed is shown. The work so far is kept.
Stopped You stopped it. The work so far is kept.
NEEDS YOU YSRA WORKS HOW IT ENDS Queued waiting for a machine or a slot Working reading, changing, running checks Needs your input the same task continues when you answer Checks run the ones the work needs or you asked for; a failure is repaired Done the checks that ran pass; one line says what ran Didn't work checks fail or it doesn't start; changes kept Stopped with a problem it couldn't go on Stopped you stopped it; changes kept starts asks you change made checks pass still failing can't go on you stop it
Every end state keeps the changes; the last four are end states.

What moves a task from one state to the next, repair rounds, lost machines and credits running out are on How a Code thread works.

How a task ends#

Each task ends with a card in the thread.

The card says What you can do
Done Review changes, then commit, push or open a pull request; Undo changes… on your computer; Go back… Notes, if any, are listed under the summary.
Needs you Answer the question, approve, or say go on to finish the rest.
Didn’t work Continue: Ysra picks up from what failed and fixes it. You can still review or deliver the work so far.
Stopped Continue, or send the next message.

A paused task (waiting for an answer, or for credits after they ran out) waits in the thread instead. In the desktop app, see Review the diff, Commit and push, Undo and Stop and continue; in the CLI, see Commit, push and undo.

A finished thread is still a conversation: ask for another change and the next task starts from the same files.

What people use it for#

Job Where it usually runs
A feature or a bug fix in an existing repository Your computer, or a GitHub repository in the cloud
A new website, API or app from a written brief An empty folder, or a new cloud project
A migration or dependency upgrade, proven with your checks Your computer
An evidence-backed explanation of a failure, with no code change Any; a question is answered read-only
A UI change checked in a browser Any; see Try the change yourself or Previews

Before editing anything, Ysra reads the place it works in: languages, frameworks, packages, layout, and the commands the project already uses to install, lint, type-check, test, build and preview.

YsraDocs