01
A session is a conversation
Every curio session is a Sudo chat with its own sandbox. /workspace is your configuration as files: endpoints, AI tools, agents, schemas, tasks.
curio · The command line for Curiosity Studio
Sudo's sandbox,
in your terminal.
Claude Code works through curio · click the screen to type a request · Esc gives the keys back
Install / 01
Two lines, and you are in.
The first run asks for your Studio address, opens the browser to sign you in with any login the workspace supports, SSO included, and drops you into the two panels. It needs a system administrator account.
Install script
The self-contained build for your system, checked against the release and put on your PATH. No .NET needed. Run it again to update.
$ curl -fsSL https://curiosity.sh/install.sh | bash
$ curioPS> irm https://curiosity.sh/install.ps1 | iex
PS> curioInstalls to ~/.curiosity/bin · read the script
.NET tool
With the .NET SDK installed, curio is a global tool. dotnet tool update keeps it current.
$ dotnet tool install --global Curiosity.Shell
$ curioOr take the single file for your system from the releases
What it is / 02
The same sandbox as the admin dock. Your keyboard, your editor.
02
Edits wait for you
What you write into /workspace stays in the session, marked in the panel, until a commit is staged and approved.
03
One session, two windows
A session opened in curio is listed in the admin dock, and the other way round. Sudo can edit while you watch the panel change.
The loop / 03
Edit. Build. Commit. Approve.
F9 opens the changes: every file the session touched, its diff, and the buttons that take it to production. Try it on the laptop above.
- F4
Edit
In the panel, in the command line, or in your own editor with
curio getandcurio put. - Build
Check
The changed definitions compile against the workspace before anything is staged.
- Commit
Stage
The same diff and the same commit Sudo stages in the dock, waiting for a person.
- Approve
Apply
The workspace applies it and streams the log. Until then, nothing changed.
Keys / 04
A two panel commander, the way your hands remember it.
Typing anywhere starts a command. It runs in the sandbox, in the active panel's directory: build, commit, graph, query, uid, tasks and the rest. help lists them.
Tabswitch panel; on the command line, complete
Enteropen a directory, view a file, run the command
Spacemark files; Ctrl+A marks them all
F2sessions: switch, create, rename, delete
F3F4view and edit, with a conflict check on save
F5F6copy and move, local to sandbox and back
F7F8make a directory, delete
F9changes: diff, build, commit, approve
Ctrl+Othe console behind the panels
Ctrl+Lswitch a panel between sandbox and this computer
Ctrl+Uswap the panels
F10quit; the session stays
One shot / 05
Every panel action is also a command, for scripts and CI.
Exit codes carry through: the sandbox command's own for run, 77 not signed in, 78 not allowed, 75 conflict, 64 usage. For CI, set CURIOSITY_SERVER and CURIOSITY_TOKEN; nothing is stored.
curio login [--server URL] [--approve|--no-approve]
curio logout | whoami
curio sessions [list | new [name] | use <id|name> | rename <name> | rm | reset | stop]
curio run -- <command line> curio run -f script.sh
curio status | diff
curio commit [show | approve | discard]
curio ls [path] | cat <path> | get <path> [local] | put <local> <path> | rm [-r] <path>
curio upload <files...>
curio skills [list [--all] | search <words> | show <name> | install [folder] [--global]]Your coding agent / 06
Claude Code writes it. Sudo checks it. You approve it.
curio is a command line, so every coding agent that can run a shell command can work on your workspace through it. The agent never gets more than a session: its edits wait in Sudo's sandbox until a person approves them.
01 · Claude Code
Writes the change
Reads Sudo's skills, edits the files and runs the build, all as curio commands in a session of its own.
02 · Sudo's sandbox
Builds and stages it
The change is a file in the session, built against the workspace and staged as a commit, the same one Sudo stages in the dock.
03 · You
Approve it
On Sudo's review screen in your browser, or in curio when you allowed it to. Then, and only then, the workspace runs it.
Claude Code
Reads the skill where it looks for skills. --global puts it in ~/.claude/skills for every project.
$ curio skills installOpenAI Codex
Install the skill into a folder of the repository and name it in AGENTS.md, the file Codex reads.
$ curio skills install ./.agentsMistral Vibe
The same file, in a folder of your choosing; point the project instructions Vibe reads at it.
$ curio skills install ./.agentsAny other harness
If it can run a shell command, it can run curio: plain output, exit codes that mean something, and one skill that says how.
$ curio skills show curioTry it on the laptop at the top of the page: the default view is a Claude Code session working through curio.
Approving / 07
You decide whether curio may approve on its own.
Not allowed · the default
Approve opens your browser
Approving opens the commit on Sudo's own review screen and curio waits until you approve or discard it there. The workspace enforces it: a token issued to such a curio is refused by the approve routes, and stays refused when it is renewed.
Allowed
Approve applies it
curio commit approve and the Approve button in F9 apply the commit and stream the apply log. The sign in page shows the choice as a checkbox, and that is what decides. Sign in again to change your mind.
Signing in / 08
Your login, your keyring, revocable in one click.
01
The browser signs you in
An OAuth loopback flow with PKCE. curio listens on 127.0.0.1, the workspace asks you to confirm, and the code that comes back is worthless without the secret curio kept.
02
The token stays in your keyring
Windows Credential Manager, the macOS Keychain or the Secret Service on Linux. Where there is none, a file only you can read.
03
Listed, and revocable
It shows up under Manage, Tokens as curio on user@machine. Revoking it there signs curio out; curio logout revokes it too.
04
A live connection
A WebSocket to the session carries commands out and every change back: Sudo editing in the dock, a commit staged, an approval in the browser. Behind a strict proxy it falls back to server sent events.
Open a terminal. Sudo is waiting.