Developer

robo-nix is focused around one user workflow: prepare a robot-learning runtime with robo shell, then let uv manage Python inside that runtime.

Current command surface:

• robo shell: bootstrap missing runtime files, evaluate the Nix dev-shell environment, then launch the user's interactive shell with that environment.
• robo run [--] <command> [args...]: use the same bootstrap and environment path, then run one command with the resolved runtime environment. A single leading -- after run is stripped as the wrapper separator; later separators remain part of the child argv.
• robo search <library>: look up Nix package candidates for missing shared libraries. It does not edit project files.
• robo refresh: clear robo-owned runtime state under .robo-nix/ and request prompt-time environment refresh inside an active runtime shell.
• robo __shell-refresh <shell>: hidden prompt-hook helper used by active robo shell sessions.

The public command surface is intentionally limited to the commands above. Global utility flags such as robo --help, robo --version, and robo -V do not add runtime workflows.

Read next:

• Overview: architecture, ownership, generated files, and verification.
• CLI UX: output style, progress tree, shell launch, and prompt refresh behavior.