# Terminal and machine

> Use your retained shell, inspect the machine, and understand what survives leaving or restarting.

**Experimental · private access. Public signup is not open.**

<!-- SOURCE: src/lib/Terminal.svelte, src/routes/+page.svelte, internal/home/terminal.go, docs/recovery.md -->

Your Space is a Linux machine with ordinary files, installed tools, and Docker
and Compose. **Terminal** opens a shell in the current workspace. Commands use
the machine's permissions and can change its files, just as commands run by Kin
can once approved.

## Use the shell

1. Choose the workspace and open **Terminal**.
2. Confirm the working folder before running commands.
3. Run your command and inspect its output and resulting files.

For a harmless first check, run `pwd` to print the current folder and `ls` to
list it. A browser window is not a separate machine.

The shell runs in tmux, which keeps it alive when the browser disconnects.
**Rejoin shell** returns after a dropped connection. The mouse wheel scrolls
back through earlier output; dragging selects and copies text. Hold Shift
while dragging to use the browser's selection instead.

In Terminal, Ctrl+B belongs to tmux. On a phone or where the clipboard refuses
an automatic copy, use the platform's selection and copy controls. Physical
touch and installed-browser behavior can differ from desktop Chromium.

## Inspect the machine

**Your machine**, at the bottom of the sidebar, shows the machine name, uptime,
free storage, Docker readiness, running Space revision, and containers. It also
offers **Open terminal**. A failed refresh keeps the last figures visible and
labels the failure with **Try again**; stale figures are not a fresh measurement.

## What persists

| Event | What to expect |
| --- | --- |
| Leave a page or close a tab | Files and saved conversations remain; Kin and the tmux shell can continue. |
| Sign out or let sign-in expire | Browser connections close. Retained files and history remain. |
| Restart the machine | Saved files remain, but running commands and services can be interrupted. |
| Save a project in Depot | That repository's selected work is saved; this is separate from whole-machine recovery. |

After interruption, inspect the command's outcome before running it again,
especially for uploads, deployments, or other external effects. A lost reply
does not prove the operation failed.

## Recovery and maintenance

Machine backups and restores belong to the operator of your Space. Maintenance
can briefly make the home unavailable and interrupt live work. Ask the operator
about the current backup and recovery evidence for your machine; an installed
browser app, saved chat, or kept artifact does not establish a verified restore.

Save browser file drafts before maintenance. If work is missing or the machine
does not return, use [Troubleshooting](/docs/space/troubleshooting/) and report
what you observed rather than trying destructive repair commands.

_Source authority: Kinra Site (src/content/docs/space/machine.md)._