Settings
Look up every section of the desktop app's Settings — Personal, Workspace, Integrations and Advanced — with what each control does and its default.
On this page
Settings holds the desktop app’s choices for this computer and your account, in four groups. Use this page as a reference when you're looking for a control or its default. Open it from your account at the bottom of the rail → Settings, or Cmd+,; it opens as a page beside the sidebar, and ← Back, Esc or choosing anything in the sidebar closes it. Search at the top of Settings finds a section by the words it covers.
Sections#
| Group | Section | What it’s for |
|---|---|---|
| Personal | General | Auto mode for new threads, error reports, and the tools on this computer |
| Appearance | Light, dark, or as your system is set | |
| Notifications | Which notices are also emailed | |
| Accounts | Sign in to Ysra, and see where you’re signed in | |
| Usage | Credits left, when they refill, and where they went | |
| Billing | Your plan, credits, payment methods, automatic top-ups and invoices | |
| Workspace | People | Your organisation: who is in it, their roles, and inviting people. See Organisations and roles |
| Devices | Computers that work for you, the folders they share, and the machines they reach | |
| Machines | Machines this computer reaches | |
| Approvals | Your approval key, and how gateways learn to trust it | |
| Integrations | Plugins | Connectors, MCP servers and skills |
| On this computer | Skills, MCP servers and hooks installed on this computer, for Code threads here | |
| Advanced | Code | What Code may do on this computer beyond the folder you give it |
| Advanced | The server your account signs in to |
General#
Settings → General
| Control | Default | What it does |
|---|---|---|
| Auto mode for new threads | Off | New threads start in Auto. You can still switch per thread in the message box’s access control. What it covers: Auto mode |
| Send error reports | On | Crash and error reports to Ysra |
| Send a report… | — | Sends what you write about a problem, with the end of the log. See Send a report |
| Your tools | — | The tools Ysra found on this computer, and whether it can run commands here |
| Installed tools | — | Tools Ysra installed for you |
| Commands (Windows only) | Ask before each command | How commands run. See Windows |
Error reports#
Send error reports is on unless you turn it off: “When the app crashes, stops responding or meets an error, a report goes to Ysra so it can be fixed: where in the app it happened, the app’s version and the system. Never your files, questions, answers, file paths, email address or keys.” Turning it off stops reports at once. The section also says where the app’s log is.
Your tools#
The tools Ysra found on this computer, by name and version: git, node,
docker, gh and so on. Ysra never sees paths or account names. This
section also says whether Ysra can run commands here; if it can’t, Ysra only
reads and edits files in the folder you opened.
Installed tools#
Tools Ysra installed for you with your OK (Node.js, Python, Git), in Ysra’s own folder, not system-wide. Remove deletes one; Ysra asks again the next time a task needs it. See Install tools with your OK.
Appearance#
Match System, Light or Dark. The same choice is in your account’s menu at the bottom of the rail, and under View → Appearance in the menu bar.
Notifications#
Shown while you’re signed in to Ysra. Five switches choose which notices about your routines are also sent to your email address. Every notice stays under the bell at the foot of the rail either way; Email settings in the bell’s panel opens this section.
| Switch | Default |
|---|---|
| A run fails | On |
| A routine waits for your approval | On |
| A watched address goes down | On |
| A watched address is back | On |
| A run finishes | Off |
Accounts#
Whether Ysra can be reached, and who you are signed in as. Threads from every signed-in account are shown together.
| Control | What it does |
|---|---|
| Check connection | Tests that Ysra can be reached from this computer |
| Sign in / Sign out | Sign in to Ysra with your browser; or Use a password instead; or Use the ysra CLI login if you have signed in with the CLI here |
| Workspace | The workspace new threads belong to, when you have more than one |
| Signed in on | Every app and browser signed in to your account, with when each was last used; this one is marked this computer. Sign out ends one of the others |
| Sign out everywhere… | Asks first, then signs out every app on every computer, this one too |
See Sign in and where you’re signed in.
Usage and Billing#
| Section | Shows |
|---|---|
| Usage | The credits left, the Credits used per day chart, and What used them. See See your usage |
| Billing | Everything the web app’s Billing page does: the plan, extra credits, payment methods, automatic top-ups and invoices. Cards are entered, payments made and invoices opened in a secure window of the app. See Billing in each app |
A member who doesn’t manage the account’s billing sees Billing for this account is managed by someone else. Ask them. See Who pays in an organisation.
Devices#
Computers you’ve signed in with ysra login --device.
Settings → Devices
Approve a device: on the device, run ysra login --device; it shows a
code like ABCD-EFGH. Type the code here, choose Find it, check the name
and system shown, then choose Approve.
| Control on each device | What it does |
|---|---|
| Observe / Change | Observe: Ysra only looks around and runs checks there. Change: Ysra may also edit there, with your OK |
| Folders on device… | Lists the folders that device is sharing. New thread starts work on one |
| Machines gateway reaches | Use its machines in workspace pairs a gateway’s machines with the workspace. See Machines |
| Remove | Signs the device out at once |
A device that says offline isn’t running ysra serve; start it there.
More: Devices.
Machines#
Headed Machines this computer reaches: servers and equipment Ysra
reaches from this computer, which acts as their gateway, through your own SSH
keys or command-line sign-in. They are kept in ~/.ysra/targets.json, and
their addresses and keys are stored only here. This is a different list from
the Machines page in the rail, which shows the workspace’s
machines.
With nothing added yet, the tab says No machines on this computer yet. Machines a gateway reaches are listed under Devices and on the Machines page.
Settings → Machines, with a machine’s log open
Add a machine… asks for:
| Field | Notes |
|---|---|
| Name | Lowercase letters, digits, dots, dashes or underscores, for example edge-01. A name already in use is refused: You already have a machine with that name. |
| Kind | Linux server, Jetson, ESXi host, Network gear, OSS, Other |
| How I reach it | SSH, or a command-line tool |
| SSH host alias | A host from your ~/.ssh/config. Check its host key shows the fingerprint; compare it with the server’s own, then confirm |
| Command-line tool | For example govc or kubectl. Ysra uses your existing sign-in |
| Production | Adds a typed confirmation for anything that can’t be undone |
A new machine starts in observe mode: Ysra only reads there until you switch it to change.
| Control on each machine | What it does |
|---|---|
| Observe / Change | Observe: Ysra only reads there. Change: Ysra may run changes, each one after your OK |
| Production | Anything that can’t be undone needs you to type the machine’s name |
| Log | Everything that ran there: when, the command, read / change / destructive, and whether you approved, declined, or typed the name |
| Remove | Ysra forgets the machine and its pinned host key. Its log stays |
More: Devices & machines and Machines.
Approvals#
Your approval key signs approvals ahead of time, so a gateway can carry out agreed changes without asking at each step.
| Control | What it does |
|---|---|
| Make my approval key | Creates it once. It stays in this computer’s keychain |
| Fingerprint, Public key | Shown once the key exists, with Copy |
| Copy the commands | The commands the gateway’s owner runs to trust the key |
See Approvals and automatic runs.
Plugins and On this computer#
| Section | Holds |
|---|---|
| Plugins | Connectors, MCP servers and skills on your account, which Ask, routines and Code threads can use. See Plugins |
| On this computer | Skills, MCP servers and hooks installed on this computer, for Code threads here |
Code#
What Code may do on this computer beyond the folder you give it, kept on this computer only.
| Control | What it does |
|---|---|
| Let Ysra look at this computer | Lets a thread look at your home folder or the whole disk to answer questions about the computer, including from a thread on a project folder: what's installed, what fills the disk. It only looks: nothing there is ever changed or deleted. It takes effect in open threads at once. See Questions about your computer |
| Allow changes on this computer | Offered only where available: “Each change still asks you first. Ysra never deletes anything on this computer.” Otherwise the section says Changes on this computer aren’t available yet. |
When looking at the whole computer isn't available, Code works only on the folders you give it.
Advanced#
| Control | Default | What it does |
|---|---|---|
| Server | Production | Leave it as it is unless Ysra support asks you to change it. Changing it signs you out. |
Version and help#
The bottom of Settings shows the version, for example
Ysra 1.23.1 (build …), and Version N is available ·
Download when a newer one is out. See
Update and uninstall.
The Help menu has Send a report… (see Send a report), then links to these docs: the desktop guide, Settings, Machines and the install page.
Related#
- Approvals and auto mode: what Auto mode for new threads changes.
- Ysra Desktop on Windows: the Commands choice.
- Devices & machines: adding a device or a machine.
- Troubleshooting: when something doesn’t work.


