Forge Networking Tool

Forge Networking Tool adds a "Forge Network" panel to Chrome DevTools that makes debugging Atlassian Forge apps far easier. THE PROBLEM Forge 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/backend/1.0/forge/config) • A clean request/response split, each a collapsible, syntax-highlighted JSON tree: Request headers, Request payload (body + context), Response headers, Response body • Color-coded status codes (2xx / 3xx / 4xx / 5xx) • Per-section toggles for exactly what you want to see, plus Gadget (context) and Full response (raw relay) on demand • A "Forge invoke only" filter, resizable columns, and a resizable detail pane • Import a HAR file (button or drag-and-drop) to un-wrap captured traffic offline It also lists the page's other REST and GraphQL traffic — including Atlassian Connect apps, which use a different (proxied) transport — so you get the whole picture in one place. 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. Supported sites: standard Atlassian Cloud (*.atlassian.net). Sites served from a custom domain are not supported. Made for Atlassian Forge app developers who are tired of squinting at GraphQL envelopes. Summary: Un-wrap Atlassian Forge gadget traffic in DevTools — see the real backend request & response behind each GraphQL relay call.