Open a Shell

Some work is not one command. You want to look around, install a package, edit a file, and try again until it works. Open one shell in the box and cd, exported variables, and everything else you set stay with you for the whole session.

Open a shell with the CLI

⌘Copysys9 run box create shell
sys9 run box exec shell -it /bin/sh

Inside that shell you can work normally:

⌘Copy# inside the shell:
pwd
uname -a
exit

The exec wakes the box. You do not start it separately.

Inside one shell session, cd, exported variables, and shell-local state behave the way you expect. When you exit, that shell state ends, but files you created in the box remain.

Pipe input into a command

Use -i when a command reads stdin but does not need a terminal UI, such as cat, tee, or another program that only consumes bytes:

⌘Copysys9 run box exec shell -i /bin/cat

Another way into the same box

sys9 run box exec -it ... and product SSH both attach you to the same box model. The difference is mostly which client you want in your terminal:

• sys9 run box exec -it fits well if you are already working in the run9 CLI.
• Connect with SSH fits well if a standard ssh command or an SSH config entry works better in your terminal.

For work that should keep running after this terminal closes, Keep a Task Running uses box exec-bg and an exec_id instead of one live shell session.

Exit cleanly

Exit the shell when done:

⌘Copyexit

After the box is idle, run9 can sleep it automatically. Most of the time you can simply exit and leave it there. Reach for sys9 run box stop shell only when you need the box quiet immediately.