debug-tunnel-network

Diagnose Local Coding Agent tunnel, DNS, TCP, TLS, proxy, organization, and office-network blocking issues.

IndexedAGPL-3.0★ 57

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/longngn204-debug-tunnel-network

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Diagnose Local Coding Agent tunnel, DNS, TCP, TLS, proxy, organization, and office-network blocking issues.

Use cases: agent-building

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/debug-tunnel-network

What's inside

Skill name: debug-tunnel-network
Description: Diagnose Local Coding Agent tunnel, DNS, TCP, TLS, proxy, organization, and office-network blocking issues.
License: AGPL-3.0
Instructions: 37 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# Debug Tunnel Network

Use this when the customer says the agent works on mobile hotspot but fails on
an office, school, VPN, or internal network.

## Rules

- Do not print or commit API keys.
- Do not change firewall, VPN, or proxy settings without asking.
- Collect diagnostics first; avoid guessing.

## Steps

1. Verify the local server:
   - `http://127.0.0.1:8787/healthz`
   - `http://127.0.0.1:8790/ui`
2. Run basic network doctor:
   - `node scripts/network-doctor.mjs`
3. If the customer can provide tunnel details, run a tunnel smoke test:
   - Windows PowerShell:
     `node scripts\network-doctor.mjs --tunnel-bin "tools\tunnel-client.exe" --tunnel-id "tunnel_..." --organization-id "org_..." --duration 30`
   - macOS/Linux:
     `node scripts/network-doctor.mjs --tunnel-bin "tools/tunnel-client" --tunnel-id "tunnel_..." --organization-id "org_..." --duration 30`
4. Ask the customer to send `network-doctor-report.txt`.

## Interpret Results

- DNS failure: company DNS may block or misresolve the endpoint.
- TCP 443 failure: outbound HTTPS is blocked.
- TLS/certificate failure: corporate SSL inspection or custom CA may interfere.
- HTTP 401 from OpenAI API: network path works; credential may be missing/invalid.
- `forcibly closed`, `ECONNRESET`, or `poll failed`: long-lived tunnel/WebSocket
  traffic is likely closed by firewall, proxy, VPN, or TLS inspection.
- `tunnel_active_organization_required`: provide the Organization ID that owns
  the tunnel.

From LongNgn204/local-coding-agent, AGPL-3.0.

Signals

Stars: 57
Forks: 32
Open issues: 1
Last commit (this folder): Jul 1, 2026 (3 months ago)
Last release: Oct 6, 2026 (23 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License: AGPL-3.0
Repository: github.com/LongNgn204/local-coding-agent
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

Same skill elsewhere

Copies of this SKILL.md published by others; search shows only one of them.

More from LongNgn204

Cite this page

debug-tunnel-network skill. Agent Mart. https://agentmart.dev/skills/longngn204-debug-tunnel-network (last updated 2026-10-24)