#Running your own commands

Type the ordinary commands you already know, run them in a session, and watch the output stream back live — with your permission level still in force.

#Overview

The Shell is a real command line, which means you are not limited to natural-language requests or built-in session helpers. You can type the everyday commands you already know — the ones you would type in any terminal — and run them directly inside a Shell session.

What makes this different from a bare terminal is everything around the command. Output streams to you live as it runs, the session keeps a lasting record of what happened, long jobs keep going in the background, stopping always works immediately, and the permission level you chose stays in force for every command you type. You get the directness of a command line with Nourva's safety and control wrapped around it.

#What you can do

  • Type any ordinary command you already know and run it in the session, exactly as you would in a normal terminal.
  • See the output stream back live, line by line, as the command runs.
  • Run inside your workspace — the project or folder you are working in — so your commands stay where you intend them.
  • Choose where the command runs: locally on your own machine, or in a secure, isolated environment kept separate from your system.
  • Keep your chosen permission level in force, so a command that would make a change waits for you exactly as you set it to.
  • Stop a command the moment you want to — stopping always works immediately, regardless of the permission level.
  • Leave a long command running in the background and come back to it; nothing is lost if you step away.
  • Mix your own commands with the built-in session commands and with plain-language requests, all in the same session.

#How to use it

  1. Open a Shell session inside Arachne, and choose where it runs — locally on your machine, or in a secure, isolated environment.
  2. Set the permission level that fits what you are about to do. Lower levels keep you in the loop for each change; higher levels let the work flow.
  3. Type your command at the prompt — the same command you would type anywhere else — and run it.
  4. Watch the output stream in live as it runs. You see exactly what is happening, not just a result at the end.
  5. If a command would make a change and your permission level holds for approval, approve it when you are ready, or stop it if you have changed your mind.
  6. For a long-running command, let it continue in the background and carry on with other work. You are told when it finishes, and you can return to check on it.
  7. Use the built-in session commands alongside your own — context to review recent steps, cost to see what the session has used, kill to stop a running command — without leaving the session.
Note

Your permission level applies to every command you type, the same way it applies to everything else in the session. At a cautious level a command that would change something pauses for your approval; at a higher level the work runs through. You can change the level at any time.

#Examples

What you ask

text
list the files in this folder

What you see: The listing streams back live in the session, line by line, and the lasting record shows that you ran it.

What you ask

text
git status

What you see: The current state of your workspace streams in line by line as the command runs, so you can read exactly what changed before deciding what to do next.

What you ask: "Install the dependencies for this project and then run the tests."

What you see: The session runs the install, streaming its output live, then runs the tests; if your permission level holds for approval, it pauses for you before acting, and stopping is available at any point.

#Tips

Tip

Start a session at a cautious permission level — Look only or Ask before acting — when you are exploring or running something unfamiliar. Give more freedom once you trust the task and know what each command will do.

  • Keep your commands inside the session's workspace so their effects stay where you intend them and do not reach outside that boundary.
  • For anything you want to keep sandboxed, choose the secure, isolated environment; choose local when you mean to work directly with your own machine and files.
  • If a command hangs or runs longer than expected, stop the running command with kill and review what happened in the live output or with context — stopping always works immediately.