Node Center and Remote Hosts
Node Center and Remote Hosts
Section titled “Node Center and Remote Hosts”Node Center (◎) is the global view of your remote hosts. Open it from the sidebar. When you run services on more than your own machine, this is where you check that the remote side is healthy before trusting its logs.
The header summarizes the fleet: N nodes · M abnormal services, and whether the live status stream is connected.
Reading a Node Card
Section titled “Reading a Node Card”Each card is one host:
- Health badge —
HEALTHY, degraded, or disconnected when the node is unreachable. - agent
<version>— the installed superdev-agent version (or “agent unknown”). - Service count — how many remote services this node runs; per-service status dots underneath, with CPU / MEM / uptime / restart counts.
- A node with no services shows no remote services.
If a node is unreachable, its card shows disconnected and you should treat its logs as stale until it reconnects.
Adding a Remote Host
Section titled “Adding a Remote Host”When you have no hosts yet, Node Center is empty and points you to Settings to add one. Adding a host is two phases:
- Connect — provide SSH connection info for the host (you enter the credentials).
- Install the agent — SuperDev uploads the agent binary over SSH and keeps it running as a systemd / launchd service. It does not touch your business processes and can be reinstalled at any time.
The agent is what makes the host’s services and logs visible here and in the sidebar’s env groups.
Drive this through your agent: ask it to walk you through adding a remote host and installing the agent. You enter SSH credentials in the UI; the agent explains the steps. See the Getting Started flow in the Desktop app tour.
- Project overview and ingress — runtime status, pipelines, config, ingress.
- Configure tier 2: remote debugging — what to prepare for remote work.