curio

Sessions and the sandbox

Every curio session is a conversation with Sudo, the admin assistant, and every conversation has its own sandbox. curio and the admin dock show the same sessions: one created in curio is listed in the dock, and the other way round. You can start a change in the terminal and ask Sudo about it in the dock, or the reverse.

A session can exist on a workspace with no AI provider configured. curio creates it all the same, and Sudo does not reply in it until a provider is configured.

What is in the sandbox

Path Contents Writable
/workspace The workspace's configuration as files: endpoints, AI tools, agents, skills, schemas, tasks, NLP definitions, configuration documents. Yes, as uncommitted changes
/reference A generated example workspace showing every configurable surface. No
/docs Generated documentation: code scopes, the schema helper. No
/sdk The C# surface the workspace's code is written against, as a partial extract. No
/proc Live runtime state, shaped like /proc on Linux. No
/session What the session keeps track of, such as its to-do list. No
/stage Files an admin uploaded to the Stage area, as text. No
/frontend The workspace's own front end, as source. Yes
/home/uploads Files attached to the conversation. No (copy into it from curio to attach)
/tmp Scratch space, in memory, kept for 12 hours after the session's last command. Yes

The full description of each mount is in the admin assistant's filesystem page.

Changes, commits and approval

stateDiagram-v2 [*] --> Changed: edit, put, rm, copy Changed --> Changed: build Changed --> Staged: commit -m "…" Staged --> Changed: discard Staged --> Applied: approve Applied --> [*]
  • An edit to /workspace is a change of the session. curio status and curio diff show them; the workspace itself is untouched.
  • commit -m "…" in the session stages the changes as one commit. Only one commit waits at a time.
  • A person approves the commit, in curio or on Sudo's review screen, and the workspace applies it. See Approving changes.
  • curio sessions reset throws away every uncommitted change in the session.

Someone else may be editing the same sandbox. Sudo, or you in the dock, can change a file while curio has it open. The editor refuses a save when the file changed since it was opened, and curio put --expected-hash does the same for scripts.

Managing sessions

curio sessions                 # list them; * marks the current one
curio sessions new fix-search  # create one and make it current
curio sessions use fix-search  # switch, by name or id
curio sessions rename search-v2
curio sessions stop            # stop a running command, or Sudo's turn
curio sessions rm              # delete it: the conversation and its uncommitted changes

curio remembers the last session used on each workspace. --session (or CURIO_SESSION) picks another for one command.

Referenced by

© 2026 Curiosity. All rights reserved.