Available on NuGet Read more

curio

The command line for Curiosity Studio. It opens the sandbox Sudo works in from your own terminal: a two-panel file manager for administrators, and one-shot commands for scripts and coding agents.

Install Your first session

What is curio?

curio is a .NET global tool (the NuGet package Curiosity.Shell) for system administrators of a Curiosity Studio workspace. It connects to the same sandbox that Sudo, the admin assistant, works in:

/workspace is the workspace's configuration as files: endpoints, AI tools, agents, skills, schemas, scheduled tasks and the rest.
Next to it are the read-only mounts Sudo reads from: /reference, /docs, /sdk, /proc, /session and /stage, plus /frontend, /home/uploads and /tmp.
Every sandbox command works from curio: build, commit, graph, query, type, uid, tasks and the others.

Nothing you change is live until you approve it. An edit to /workspace stays in your session as an uncommitted change until a commit is staged and approved, which is the same diff and the same approval as in the admin dock.

dotnet tool install --global Curiosity.Shell
curio

Three ways to use it

The two-panel interface

Run curio with no command: your session's sandbox on the left, this computer on the right, the command line and F-keys below.

Scripts and CI

One-shot commands with plain output and meaningful exit codes. curio run passes the sandbox command's exit code through.

Coding agents

curio skills install teaches Claude Code, Codex or any shell-capable agent to work on the workspace through curio.

How it fits together

flowchart LR you["You, in curio"] -- "edit, build" --> session["Session sandbox<br/>(uncommitted changes)"] agent["Coding agent"] -- "curio put / run" --> session sudo["Sudo, in the admin dock"] -- "same session" --> session session -- "commit -m" --> staged["Staged commit"] staged -- "approved" --> ws["Live workspace"]

A session is a Sudo conversation. A session you create in curio is listed in the admin dock, and the other way round. See Sessions and the sandbox.
Approval stays with a person. When you sign in, you choose whether this curio may approve changes by itself. By default it may not, and approving opens the commit on Sudo's review screen in your browser. See Approving changes.
The connection is live. curio keeps a WebSocket open to the session, so edits Sudo makes in the dock appear in your panels as he makes them. See The live connection.

In this documentation

Installation: the dotnet tool, or a single-file binary.
Signing in: the browser sign-in, where the token is kept, and how to revoke it.
Your first session: from curio to an approved change.
Command reference: every command and option, and the exit codes.
Keys: the keyboard map of the two-panel interface.
Configuration and environment: environment variables and the files curio writes.

The product page for curio, with a simulated session you can try in the browser, is curiosity.sh. The older curiosity-cli is a different tool: it tests connections, ingests folders and promotes definitions between workspaces, and it does not open a sandbox.