Background processes and PTY
Okami has process tools and CLI supervision for long-running commands: dev servers, watchers, slow tests and interactive REPLs. They are persisted on disk, visible…
Tools
params process_start tool starts a background command; supports notify, watch, interactive process_write tool sends stdin to an interactive process process_poll tool status plus recent output process_wait tool waits until completion or timeout process_log tool full or paginated logs process_list tool lists known processes process_signal tool TERM/INT/HUP/KILL/USR1/USR2/CONT/STOP/QUIT process_kill tool terminates a process group
Terminal supervision
okami ps -w workspaces/defaultlist processes in the default workspaceokami processwith no subcommand, also lists processesokami process log <id> -n 200 -fprint or follow redacted logsokami process kill <id>send TERM to the process group or docker kill when isolatedokami process signal <id> INTsend an arbitrary signalokami process wait <id> -t 60wait for completion and show exit codeokami process clean --ttl-hours 24 --dry-runshow what would be pruned past the TTLokami ps -a uiuse the workspace for agents/uiWhy this closes the gap
The agent can start a server or watcher with a tool and keep working. Outside the gateway or TUI, an operator can still list, read logs, wait, signal or kill it through okami process without depending on the original session.
Safety
In read-only sandbox mode, process_start is blocked. In normal modes, commands touching .env, .ssh, .aws, credentials, .pem or .key are blocked unless the profile is yolo.