Add another computer of yours as a device so Ysra can work on its folders with the real hardware, and control what it may do there.

On this page

A device is another computer of yours with Ysra installed and signed in — an edge box with a GPU and camera, a build server, a lab box — where Ysra works on a folder on that computer, with its real hardware and interpreter, while you follow and approve from your own. Use one when the work has to run where the hardware is. This page covers adding a device, modes, hardware, offline behaviour and security; for installing, see Install on a server or edge device.

The rule#

A device connects out to Ysra and is never reached from outside. It works only on the folders it shares, every change waits for your OK when it is in change mode, and auto mode never covers changes on a device.

Device or machine?#

Device Machine
Ysra installed there Yes No
How Ysra reaches it It connects out to Ysra Your SSH or command-line tool, from a gateway (your own computer can be one)
Good for Project folders, benchmarks, real hardware Looking around, careful changes, runbooks
Can’t install anything (network gear, ESXi, a locked server) — Use this

Add a device#

  1. On the device, install Ysra (full steps):

    curl -fsSL https://ysra.ai/install.sh | sh -s -- --device
    
  2. Ask to sign in. The device shows a code such as ABCD-EFGH, valid for 10 minutes:

    ysra login --device
    
  3. On your computer, open the desktop app → Settings → Devices → Approve a device. Type the code, choose Find it, check the name and system, then Approve.

  4. Share a folder:

    ysra serve --folder /opt/app
    

The folder appears under Settings → Devices in the desktop app.

YOUR COMPUTER YSRA THE DEVICE ysra login --device shows a short code You approve the code Settings, Devices ysra serve --folder connects out; no port is opened The folder is listed under your devices You start a thread on the device's folder The work happens there with its real hardware 1 the code 2 3 4 your request
A device signs in with a code you approve, connects out, and does the work on its own folder.

Approving a device

Approving a device by its code

Modes#

Set in Settings → Devices. Switching is always your action.

Mode What Ysra does there
Observe (the default) Looks around and runs checks; no edits. A change request is refused, with a pointer to switch the mode
Change Also edits files there, with your OK

In either mode, heavy or disruptive work asks first and names the impact: a benchmark (“this runs the model for about 2 minutes at full GPU”), restarting the app, installing packages.

Work on a device folder#

From How
Your laptop Keep ysra serve --folder /opt/app running on the device (or the service). In the desktop app, Settings → Devices → Folders on edge-01… → New thread next to the folder
The device itself SSH in, cd to the folder, run ysra

The thread behaves like any other — timeline, approval cards, review, commit and push, undo — and the work happens on the device.

What happens when …#

A task needs the camera or GPU#

By default Ysra’s commands can’t see any hardware. The first time a task needs it, Ysra asks: “Let my commands use the camera and the GPU on edge-01 in this session? Only for this session; nothing else on the device opens.” with Allow for this session or Not now.

Rule Value
Asked Once per thread, for the hardware named
Lasts That thread only
Auto mode Never answers it

This is what makes real measurements possible: a before/after benchmark on the actual GPU, or a detection run against the real camera.

The device goes offline#

The device is online while ysra serve (or ysra in a terminal there) is connected. If the connection drops while Ysra is working, it pauses and carries on when the connection is back. Starting new work on its folder meanwhile says “The machine this folder is on isn’t connected right now.”

You choose Continue after a pause#

Guarantee Detail
Same starting point Ysra continues from the state its saved work was made against, not a fresh copy of the folder
Files it wrote Remembered, even across restarts
Files you changed meanwhile Never touched

You remove the device#

Settings → Devices → Remove → Remove it. The device is signed out at once, and anything still running there can no longer reach your work. On the device itself, ysra uninstall does the same and removes the program; see Remove a device.

Security: what a device can and can’t reach#

A device can A device can’t
Work on the folders it shares with ysra serve, or the folder you run ysra in See or change your account, balance, sign-in or other devices
Run commands in a contained space: writes only in that folder, no network except package registries during installs Reach your laptop’s folders or your machines
Use hardware, with your OK per thread Be reached from outside: it only connects out, no port is opened

If a device is lost or compromised, remove it in Settings. Its sign-in is tied to that one device, expires on its own and is renewed regularly, and stops working the moment you remove it.

The rest is as on your laptop: Git changes only when you ask, history is never deleted, undo is exact, and only what Ysra reads to do the work leaves the device. See Security & privacy.

YsraDocs