Forge Networking Tool

About

Forge Networking Tool adds a "Forge Network" panel to Chrome DevTools that makes debugging Atlassian Forge and Connect apps far easier.

THE PROBLEM
Forge and Connect apps (dashboard gadgets, panels, custom UI, etc.) don't call their backend directly. They tunnel every request through a GraphQL relay mutation (useInvokeExtensionRelayMutation). So in the normal Network tab you only see the opaque GraphQL envelope — never the actual REST call your app made or the response it got back.

WHAT IT DOES
Forge Networking Tool un-wraps that envelope for you. For each relay call it shows:

• The real backend call — HTTP method + path (e.g. GET /rest/custom-charts/1.0/forge/config)
• The un-wrapped backend response, rendered as a collapsible, syntax-highlighted JSON tree
• Color-coded status codes (2xx / 3xx / 4xx / 5xx)
• Optional detail sections behind per-section toggles: invoke type, call headers, gadget context, and the raw relay envelope
• A "Forge invoke only" filter, resizable columns, and one-click JSON export

PRIVACY
Everything runs locally in your browser's DevTools. The extension has no servers, makes no external requests, and never collects or transmits any data — captured traffic is shown only in the panel and is discarded when DevTools closes.

HOW TO USE
1. Open any Atlassian tab (Jira, Confluence, *.atlassian.net).
2. Open DevTools and select the "Forge Network" panel.
3. Reload the page and interact with your gadget — the relay calls appear, un-wrapped.

Made for Atlassian Forge and Connect app developers who are tired of squinting at GraphQL envelopes.

Want me to also save this into the submission guide (mirkov-network-submission.md) so all your copy lives in one place? And if you need the shorter Summary field (max 132 chars), use this one — it's exactly 132 and ready:

Un-wrap Atlassian Forge/Connect gadget traffic in DevTools — see the real backend request & response behind each GraphQL relay call.