Runtime

Runtime is OxideTerm’s operational view for live SSH work. It consolidates the former connection-pool, connection-monitor, and system-health pages into one reusable tab with three sections: Overview, System Health, and Connection Matrix. The adjacent Host Tools companion panel uses the same live connection context for host-level inspection and supported remote operations.

Open Runtime from the activity bar or Command Palette. Opening it again reuses the existing Runtime tab and refreshes its current state.

Overview

Overview summarizes the managed SSH connection pool while Runtime is visible:

• Connection counts by Active, Idle, Reconnecting, and Link Down state.
• Total terminal, SFTP, and port-forward consumers sharing managed SSH connections.
• Pool summary information, including its idle-timeout and capacity state.

The page deliberately shows aggregate state rather than a separate card for every connection. Configure connection behavior from connection settings and the relevant connection workflow; use Runtime to see the result across the current workspace.

System Health

System Health samples one live SSH connection at a time. Select a connection from the picker to inspect the metrics that host actually supports.

When resource sampling is available, Runtime can show CPU, memory, swap, disks, network traffic, GPU information, load averages, top processes, and SSH round-trip time. Availability depends on the remote operating system, permissions, and supported probes. If detailed sampling is unavailable, Runtime falls back to SSH round-trip measurement instead of presenting invented host metrics.

Sampling begins for the selected live connection and can be stopped or retried from the panel. Historical sparklines are available while the full Runtime view is open.

Connection Matrix

Connection Matrix visualizes the live SSH routes currently managed by OxideTerm. A direct live connection is a root node; a connection opened through a managed jump host appears beneath that parent.

[ alice@bastion.example ]
              |
              v
[ alice@internal-db ]

The matrix comes from the current connection registry, not from every saved connection. Nodes show the account and host, and lines represent parent-child SSH routes such as a ProxyJump hop. Only active, idle, connecting, and reconnecting connections are included; disconnected and failed routes are not retained as historical nodes.

Matrix Interaction

Interaction	Result
Scroll	Zoom around the pointer.
Drag empty canvas	Pan the matrix.
Double-click a node	Open its action menu.
Click outside a menu	Close it.

The canvas reduces visible state to Connected for active or idle connections and Connecting for establishing or re-establishing connections. A route is emphasized when both endpoints are connected. It does not independently test reachability or preserve a failure history.

Every node menu can navigate to that node’s active session. Connected nodes also offer a new terminal and SFTP. These actions reuse the current live connection; they do not create another route configuration surface.

Host Tools Companion

Host Tools is an independent right-side activity-bar panel, not a Runtime section. It shares the selected live SSH connection, so it complements Runtime during investigation: Runtime explains connection-wide state while Host Tools inspects the remote host itself. See Host Tools for its available modules and remote-action boundaries.

Reconnect Investigation

Runtime shows the current state, while the Event Log records the lifecycle timeline. When a connection drops:

1. Use Overview to identify the affected pool state and consumers.
2. Check System Health or Host Tools for the selected host’s available context.
3. Inspect Event Log for reconnect phases and failure details.

Connection Matrix is useful for confirming the live jump-host route before or after recovery, but it is not a history of disconnected nodes.