ShellYard
Use case · Network troubleshooting

Network diagnostics
with the context attached.

Run DNS, MTR, Nmap, TLS, SNMP, syslog, and other checks from the same workspace that holds the connection, docs, credentials, and runbook.

The shape

Diagnostics next to the connection, docs, and credentials.

Network troubleshooting is rarely "open one tool, find the answer." It's usually: SSH to a switch, look at the interface counters, pull syslog, run an MTR from one end, check DNS, inspect the TLS cert, read the IPAM record to confirm the subnet, write down what you found. ShellYard puts all of that in one workspace so the context doesn't dissolve between tabs.

01 Open

Pick the Space — lab, site, or production.

Spaces are isolation boundaries. Open the right one and the workspace is already pointed at the gear: saved SSH / serial / RDP / SSM connections, IPAM records, runbooks, and the credentials that resolve at connect time. Switching Spaces switches the entire toolkit — no risk of running an Nmap on production when you meant the lab.

02 Pick

The host or subnet from saved connections / IPAM.

Saved connections cover SSH, RDP, VNC, serial, AWS SSM, and the in-app browser. IPAM stores subnets and hosts. Pick the target from either — the diagnostic kit and the terminal both use the same identity, so a probe against fw-edge.lab.internal works whether you typed the FQDN or clicked the IPAM row.

03 Probe

DNS, MTR, Nmap, TLS, SNMP, packet capture.

DNS (forward / reverse / MX / TXT), MTR with latency, Nmap port scan, TLS certificate inspection, WHOIS / RDAP, NTP probe, SNMP browser with standard MIBs bundled, syslog viewer, packet capture, AP scanner, file transfer (TFTP / FTP / SFTP), bulk command runner, batch SSH, config backup + diff. The 80% you reach for during a troubleshooting session, in the workspace that holds the connection.

04 Ask

Hand the output to Magellan.

An MTR trace that doesn't make sense, a packet capture with a suspicious retransmit pattern, a syslog stream with errors you've never seen, two config backups that should be identical but aren't. Attach the output to Magellan and get an explanation, a suggested next check, or a draft incident report. BYO Anthropic / OpenAI / Gemini / Ollama key.

05 Save

The diagnostic becomes documentation.

When you figure out the problem — a duplex mismatch on Gi1/0/24, a stale ARP entry, a misconfigured VLAN — the fix doesn't have to disappear into terminal scrollback. Save the diagnostic output, the explanation, and the resolution into a runbook or incident report inside the Space, with version history. The next engineer who sees the same symptom finds your work.

Try it on your own network.

Free covers every diagnostic, every connection type, and Magellan with your provider key. Pro and Team add Shared Spaces, audit log export, and IT Glue / Hudu importers.