Connection Matrix
The Connection Matrix (also called Topology View) is an interactive graph that visualizes your active SSH session tree — jump hosts, target servers, and the tunnel chains between them — in real time.
It is not just a decorative graph. The topology reflects the same route model OxideTerm uses for ProxyJump, auto-route, and reconnect orchestration.
Opening Connection Matrix
Section titled “Opening Connection Matrix”Click Connection Matrix in the sidebar, or open a new tab and select the topology tab type.
What It Shows
Section titled “What It Shows”Each active SSH node appears as a labeled card on the canvas. Lines between nodes represent SSH tunnels (ProxyJump hops):
[ Local Machine ] │ ▼[ bastion.example.com ] ←── Active (2 terminals, 1 SFTP) │ ▼[ prod-db-1 ] ←── Active (1 terminal) │ ▼[ internal-cache ] ←── IdleThe graph is built from your active sessions and saved jump relationships:
- Direct connections appear as root-level nodes
- Imported
ProxyJumpchains from~/.ssh/configpreserve their parent/child structure - Reusable bastion hosts can serve both as standalone sessions and as parents for downstream routes
- Link state (
active,idle,link_down,reconnecting) comes from the connection pool, not from a static diagram
Node Status Colors
Section titled “Node Status Colors”| Color | State | Meaning |
|---|---|---|
| Green ● | Active | Connected with consumers attached |
| Blue ● | Idle | Connected but no active consumers |
| Red ● | Link Down | Connection lost, awaiting reconnect |
| Orange ● | Reconnecting | Reconnect attempt in progress |
| Gray ○ | Disconnected | Not in connection pool |
Canvas Controls
Section titled “Canvas Controls”| Interaction | Action |
|---|---|
| Scroll | Zoom in/out |
| Drag canvas | Pan the view |
| Click node | Select and view details |
| Right-click node | Open context menu |
| Fullscreen button | Toggle fullscreen view |
Node Context Menu
Section titled “Node Context Menu”Right-clicking a node opens actions:
- Open Terminal — open a new terminal tab for this node
- Open SFTP — open SFTP browser for this node
- Port Forwarding — add forwarding rules for this node
- Disconnect — disconnect this node
- View Details — show connection statistics panel
Link-Down Cascade Visualization
Section titled “Link-Down Cascade Visualization”When a jump host loses connectivity, the topology immediately reflects the cascade:
- The bastion node turns red (link_down)
- All downstream nodes (servers behind the bastion) simultaneously turn red
- The reconnect orchestrator starts — nodes that can recover show a pulsing reconnect indicator
- On recovery, nodes return to green in sequence as each reconnect phase completes
This makes it immediately clear which servers are affected by a bastion outage.
Route Planning & Auto-Route
Section titled “Route Planning & Auto-Route”When multiple paths to a target exist, OxideTerm can pick an appropriate route automatically from the saved connection graph.
- ProxyJump routes are modeled as edges in the topology
- Auto-Route chooses from the currently reachable path set
- Parent jump nodes are reused instead of re-dialing duplicate SSH tunnels
- The canvas helps you see why a target is reachable, degraded, or blocked behind a failed hop
This is especially useful when your SSH config and saved connections describe several bastion layers.
Grace Period Recovery
Section titled “Grace Period Recovery”Topology status also mirrors OxideTerm’s reconnect behavior:
- A parent node going down marks downstream children as
link_down - During the 30-second Grace Period, OxideTerm probes the old transport before tearing it down
- If the old path recovers, the graph returns without rebuilding the entire chain
- If recovery fails, reconnect proceeds parent-first so child routes can reattach in order
Status Bar
Section titled “Status Bar”The bottom status bar shows:
SYSTEM_STATUS: ONLINE- Number of active connections and maximum chain depth (e.g., “3 active connections, max depth: 2”)
Use Cases
Section titled “Use Cases”- Multi-datacenter overview — see all your bastion → server chains at a glance
- Incident response — immediately identify which servers are affected by a jump-host failure
- Onboarding — visually explain your infrastructure topology to new team members
- Debugging — verify that connection chains are set up correctly before starting work