Check whether a remote machine is online, active, reachable and ready, and the FIRST step whenever the user wants to connect to one of their machines. USE THIS whenever the user asks to "connect to / reach / log into" a computer, or asks about its state — e.g. "connect to wearfits-m3", "is my computer wearfits-m3 active/online/up?", "can you reach the build server?", "is my laptop connected?". The machine can be named by an AIC- session code (e.g. AIC-XYZ-1234) OR — when authenticated with an API key — by a saved machine alias or hostname the user calls it by (e.g. 'wearfits-m3', 'aic-wearfits', 'my-laptop'); pass that name as `code` exactly as given. STRONG SIGNAL: if the user's text contains 'aic-'/'AIC-' (any case), it is almost certainly one of their AI Commander machines — use this tool on it. Do NOT answer connectivity questions by probing the local network, DNS, mDNS/.local, ping, or a raw ssh client — this tool is the canonical, authoritative way to check whether one of the user's AI Commander machines is up. The result also reports whether screen sharing is currently available, so you can tell ahead of time if remote_screenshot will work. When the machine has an NVIDIA GPU it additionally reports each card's model, total and used VRAM, and current utilization — that is how you confirm a specific box is a suitable target for a compute job (and which `gpu_index` to reserve when starting one with remote_job_start). A machine that reports NO GPU section usually has no NVIDIA card (or no driver) — but not always: the same section is missing when the machine's GPU probe failed or timed out, and when its agent is too old to probe at all, and the relay cannot tell those three apart. Treat 'no GPU section' as 'no card known', not as proof; if the user expects a GPU there, confirm by running `nvidia-smi` with remote_exec before telling them the box has none. While the machine is OFFLINE the GPU figures are the last known reading and may be stale. It also reports the machine's OWN identity — its `hostname` and, when its agent sends them, the local IP addresses of its network interfaces — which is how you confirm that the box you reached is the one the user meant when several are saved under similar aliases. Those addresses are a LABEL, not a route: they are private addresses on the machine's own network, nothing can connect to them from here, and every command goes through this relay regardless. If no addresses are reported, that means the machine's agent did not send any (an agent too old to, or none it was sure of) — it never means the machine has no network. While the machine is OFFLINE both are the last known reading, and an address may since have been handed to a different machine by DHCP. When you are authenticated as an account (API key or OAuth) AND the machine is online, the result also gives the path of THIS account's machine-notes file on that box (private to this account, not shared with other users of the same machine) — read it with remote_exec before exploring, and write/update it afterwards, so later sessions inherit what you learned instead of rediscovering it. Anonymous session-code callers and offline machines get no such path; that is expected, not an error.
An offline machine means the relay cannot currently reach its agent; it does not prove a temporary relay outage or that a job stopped. Distinguish machine connectivity from account access, plan restrictions and invalid credentials. A reactivation-required notice means account access is paused until the owner opens the dashboard; it is not an agent connection or credential failure. A genuinely invalid credential requires re-authentication.