If you spend your day bouncing between terminal tabs, websites lookups most of them filled with annoying ads, spreadsheets files spreading like forest and half-written incident notes, you know the real cost: missed details and slower RCA.
What s your single most annoying context-switch during troubleshooting?
e.g. copy/paste config snippets into chats/group conversations/docs
e.g. jumping from CLI to websites like what's the ip or PeeringDB/IANA than jumpt to tickets then back to CLI than maybe chats with colleagues
e.g. saving ping/traceroute outputs and screenshots for the incident report
Most of us already live inside our IDEs. But when a network issue hits, we still bounce between terminals, browser lookups, config files, SSH tools, screenshots and notes, oh yeah and don't forget context switching is where mistakes happen specially when we have dozens of windows opened.
So I built Net Commander aimed to be a free, open-source network engineering toolkit built inside VS Code, designed to keep troubleshooting data-driven and consistent.
What it includes today:
Ping + traceroute, supercharged (single host, multiple targets or entire CIDRs for convenience)
Lookups: IANA ports, ASN/public IP info, PeeringDB
Calculators: RFC-compliant CIDR + “what-if” subnet simulation
Wi-Fi quick surveys + capture workflows (for wireshark deeper analysis later)
SSH profiles for fast host jumps
Network config colorizer with inline detection + useful tooltips for private/public IPs
Root Cause Analysis checklist ready to use with platform-specific commands (Cisco, Arista, Ciena, Azure, AWS, GCP)
I’d love your feedback:
Which workflow would save you the most time inside VS Code?
What tool should I add or integrate next?