The AI Inspector

The AI Inspector shows the literal JSON request that left your browser for the turn you just sent - proof of what was sent, and of which model and settings produced it.

The prompts Big-AGI assembles are open to you: the exact bytes that leave for the AI service. It is the same packet a browser's network view would show, inside the app and without DevTools. Open, Free and Pro all carry it.

Open the inspector

How to open it	What it says
Settings -> Diagnostics -> AI Inspector	"Inspect live AI requests"
Ctrl + Shift + A	the same dialog
Before anything is captured	Ready to capture · Your next AI request will be captured here.

The dialog shows each captured frame with its transport chip, the decoded URL, and the pretty-printed body.

That request body holds the assembled system prompt and the history as it was sent. The model, its parameters, the tool declarations and each attachment part are fields of it too. The first open in a session arms capture by itself; after that the switch in the title bar controls it. Turn it on, send a message, and the frame appears. History holds 5, 10, 20 or 50 frames, 10 by default, in memory only and with no export button.

What each frame shows

Field	What it is
Request number	a counter for this session
Status	two chips: the transport - Direct Connection or Edge Server - and Done or In Progress
Date	local timestamp
URL	the upstream endpoint, decoded
Context	what asked for it: conversation, beam-scatter, chat-ai-title, and so on
Reference	the id of the thing that triggered it
Headers	the request headers block
Body	the literal JSON request, pretty-printed, with a byte-size readout
Particles	the response stream as discrete timestamped events; aborted ones flagged

The transport chip records which path the request took. For a record of a run - a methods section, a file note - copy the Body block, which copies as JSON. Take the header line with it: request number, transport chip, date, URL, context, reference. Make the copy before you reload.

Which requests carry a body

The frame	Contexts
Body present, in a production build	conversation · scratch-chat · chat-react-turn · beam-scatter · beam-gather · beam-followup
Body absent, response particles only	chat-ai-title · chat-attachment-prompts · aifn-image-caption · summarize · the follow-up diagram and chart generators

Your own turns and your Beam calls are the first list. The background utility calls are the second, and they are skipped by the frame picker's auto-selection. To audit those payloads, use the browser's own network view, below. An instance running a development build shows headers, the profiler and every context.

What the inspector leaves out

• Response headers, the raw stream bytes and the transport envelope - particles are the parsed stream, not the wire.
• Request bodies for the background contexts above, in production builds.
• Non-model traffic entirely: browsing, search, image generation, account and analytics calls. This is an AI request inspector.
• Anything the AI service does after receipt.

For the rest, read the destination in your browser's own network view:

DevTools -> Network, on the tab running Big-AGI

/api/edge/...   /api/trpc/...     the Big-AGI edge path
an AI service hostname            Direct Connection
localhost   127.0.0.1             a model runtime on your own machine
/a/ph                             product analytics, on our own domain
/api/cloud/...                    your account and cloud sync, when it is on
anything else                     not ours

The same dialog holds an AI Injector, which merges a JSON blob into the next request. A capture taken while it is armed is not a record of normal behaviour - leave it alone when you are auditing. For a request that failed rather than one you did not expect, Error messages.

Related

• What leaves the browser
• What Direct Connection does
• Keep your key safe
• Error messages