# Terminal control bar

The bar along the bottom of the terminal pane shows the selected process's status. After resource statistics become available for a running process, it also shows resource usage and any tracked-subprocess count. The bar provides focus and eligible process controls, plus any enabled previous- and next-process navigation controls, without leaving the terminal.

## Focus toggle

The left-most button toggles focus between the sidebar and the terminal content area:

- **Focus** appears when the terminal is not focused. Click it, or use the configured Focus terminal shortcut, to focus the terminal content area. The default shortcut is `Cmd/Ctrl+Right`. A selected process must be running and PTY-backed to accept terminal input.
- **Unfocus** appears while the terminal is focused. Click it, or use the configured Focus sidebar shortcut, to return focus to the sidebar. The default shortcut is `Cmd/Ctrl+Left`.

When the corresponding focus shortcut is enabled, the button shows its configured shortcut next to the label. See [Focus behavior](./focus-behavior.md) for what terminal focus means.

## Prev / Next running process

Each **Prev** or **Next** button appears next to the focus toggle only when its configured shortcut is enabled. The buttons jump to the previous or next *running* process in the sidebar and show their configured shortcuts inline. The [default shortcuts](../keyboard-shortcuts/default-reference.md) are:

| Control | Default shortcut |
|---------|------------------|
| Prev | `Cmd/Ctrl+↑` |
| Next | `Cmd/Ctrl+↓` |

The enabled controls and their configured shortcuts work whether focus is in the terminal or the sidebar, and they skip stopped processes - handy for cycling through active agents and dev servers. If you navigate with the buttons while the terminal is focused, focus follows to the newly selected process.

## Quick actions

When a process is selected and the terminal is *not* focused, the footer shows quick action buttons. Which ones appear depends on the process type and state:

| Action | Available for |
|--------|---------------|
| **Start** | Trusted, stopped commands, terminals, and PTY-backed agents |
| **Stop** | Running commands |
| **Restart** | Trusted commands |

Each button underlines its single-key sidebar shortcut (`S` or `R`) when that shortcut is currently available. See [Starting, stopping, and restarting](../commands/start-stop-restart.md) and [Trust and security](../commands/trust-security.md).

These buttons hide while the terminal is focused so the footer stays out of the way when you're typing into a process.

## Process info

The right side of the footer shows live information about the selected process:

- **Process name** - the stored process name.
- **Status** - a colored dot and label: pulsing green for running, red for failed, gray otherwise.
- **Agent status** - for a running agent process, a spinner and state label show a state such as [working or idle](../agents/idle-detection.md). Running terminal processes show the same indicator. It is omitted when the process is not running.
- **Timer indicator** - when the process has a [timer](../mcp-tools/timers.md) set (for example, by an agent), an active timer shows a countdown. A paused timer instead shows **Paused** and its remaining duration. Click the indicator to fire or cancel the timer, or to pause an active timer or resume a paused one.

### Spawned by

If the selected process was started by another process - for example, a subagent spawned by an orchestrating agent - and Solo can find the parent among the selected project's processes, the footer shows a **spawned by** link with the parent's name. Click it to jump to the parent process. The link does not appear when the parent belongs to another project. See [Agents spawning agents](../workflows/agents-spawning-agents.md).

### CPU and memory

After resource statistics become available for a running process, the footer shows live **CPU** and **MEM** figures. Both are measured across the process's entire tree - the process itself plus everything it has launched - so a dev server that forks workers reports the combined usage.

### Subprocess badge

After resource statistics become available, a running process with tracked descendants shows a **+1 subprocess** or **+N subprocesses** badge. The count collapses shell wrappers, so it reflects the processes doing actual work rather than every intermediate shell.

## Tracked processes modal

Click the subprocess badge to open the **Tracked processes** modal. It shows the full process tree descended from the selected process and refreshes it every three seconds while Solo is in the foreground. For each process you can see:

- The command line (click to copy the full command).
- The PID (click to copy it).
- Uptime, CPU, and memory usage.

Each row has a **Kill** button to terminate that specific subprocess - useful when a child process is stuck or runaway but you don't want to stop the whole tree.

The modal footer includes:

- **Open activity monitor** - jumps to Solo's [activity monitor](../activity/activity-monitor.md) and preserves its current filters.
- **Copy all PIDs** - appears when the refreshed list contains at least one subprocess and copies every listed PID to the clipboard, one per line.

---

Are you a human? Read this doc on the web: https://soloterm.com/docs/terminal/control-bar