Coding agents

curio is a command line, so any coding agent that can run shell commands can work on a workspace through it. The agent works in a session, and its edits wait in the sandbox until a person approves the commit.

Give the agent Sudo's skills

Sudo's skills (the built-in ones and the workspace's own) stay on the workspace. curio reads them from there, so an agent always reads the version the workspace runs:

curio skills list [--all]          # name, kind and what each is for
curio skills search <words> [-n N] # which skills mention them, best first, with the passage
curio skills show <name>           # one skill, as Sudo reads it

--all adds the skills that travel with another; the skill they travel with names them.

curio skills install adds one skill to an agent's skills folder. It explains how to work on the workspace through curio, lists Sudo's skills, and gives the commands that read one. Nothing else is copied.

Command	Writes
`curio skills install`	`./.claude/skills/curio/SKILL.md`
`curio skills install --global`	`~/.claude/skills/curio/SKILL.md`, for every project on this machine
`curio skills install <folder>`	`<folder>/curio/SKILL.md`

Run it again to refresh the index. A copy you edited by hand is kept unless you pass --force. An install removes the files an earlier full dump of the skills wrote.

By harness

Claude Code reads skills from .claude/skills:

curio skills install            # this project
curio skills install --global   # every project

Install the skill into a folder of the repository and point the AGENTS.md Codex reads at it:

curio skills install ./.agents

AGENTS.md

Work on the Curiosity workspace through curio. Read .agents/curio/SKILL.md first.

What an agent session looks like

curio skills search "code endpoint"
curio skills show add-code-endpoint
curio cat /workspace/config/schemas/nodes/Part.cs
curio put open-notices.cs /workspace/code/endpoints/open-notices.cs
curio run -- build
curio run -- commit -m "Open supplier notices for a part"
curio commit approve        # a person answers on Sudo's review screen

Things that help an agent:

Exit codes mean something. run passes the sandbox command's exit code through; 77, 78, 75 and 64 mean not signed in, not allowed, conflict and usage. See Exit codes.
Re-read before overwriting. Sudo or an admin may edit the same session. curio get prints the file's hash, and curio put --expected-hash <hash> refuses the write if the file changed since.
Approval stays with a person. Sign curio in without the approve right (the default) and curio commit approve waits for someone to approve in the browser, whatever the agent does.

The simulated session on curiosity.sh shows Claude Code working through curio this way.