Terminals & Processes

The Terminals and Processes dashboard provides full visibility and control over background shell processes, persistent terminal sessions, and development servers managed by Orbicus.

Process Orchestration

When an agent executes terminal operations (such as running test runners, building project assets, or launching development servers like npm run dev or docker compose up), it runs them within isolated sub-process environments.

The Terminals dashboard ensures these background processes remain transparent and controllable:

Isolated Process Lifecycles: Child processes remain bound to their specific workspace directory.
Persistent Output Buffering: Orbicus captures both standard output (stdout) and standard error (stderr) streams continuously, allowing you to review build output or server logs at any point.
Exit Code Reporting: Automatically captures process termination signals and exit codes (0 for success, non-zero for failure), feeding diagnostic output back to the agent if an unexpected error occurs.

Inspecting Active Terminals

Under Monitoring $\rightarrow$ Terminals, you can inspect each active process:

Command Line: The full command invoked (e.g. npm run test:watch, cargo check).
PID & Status: The underlying operating system process ID and runtime state (running, terminated, or errored).
Console Log Stream: Click on any terminal card to open the streaming console view and inspect live outputs.

Terminating Background Processes

To prevent orphaned processes or runaway background servers from tying up system ports and memory:

Kill Specific Terminal: Click Kill next to any active process entry to send a termination signal (SIGTERM followed by SIGKILL) to that specific child process tree.
Stop All Terminals: Click Stop All Terminals to safely shut down every active background process spawned by Orbicus across all workspaces.