Execute bash scripts, javascript, and python scripts natively inside a node sandbox environment directly via the agent's message loop terminal execution context.
The host application natively exports a shell coding-agent binding to the Codex CLI (codex on PATH).
For a normal interactive Codex session (REPL / TUI), the user runs the codex command in their own terminal on the machine where NanoClaw is installed (not inside the agent container). Typical flow:
cd to the project they want to work in.codex and follow the Codex UI to start a coding session.That path is separate from chat: NanoClaw does not spawn an interactive terminal for the user; it only invokes codex exec … in the background when chat triggers below fire.
Tell users who ask for “open Codex” or “spawn a Codex session in the terminal” to use codex locally; for work driven , use the chat forms below.
Ask the user-facing router to run Codex by using one of these forms (matched by the host; include a real task after the trigger):
/codex <coding task>
use codex to <coding task>
use codex for <coding task>
spawn codex to <coding task>
spawn codex for <coding task>
have codex fix <coding task>
ask codex to <coding task>