A Chrome devtools sidepanel that captures every request to /graphql, parses operations, and puts the Authorization header one click away.

Hey PH 👋 I built GraphPeek because I was tired of the same ritual every day at work: open Network tab, see five identical rows all named "graphql", click each one, expand the payload, find the operation name. Repeat. GraphPeek is a Chrome sidepanel that parses every GraphQL request as it happens — operation name, query/mutation/subscription, status, timing. My favorite feature is the one-click Bearer token copy, because pasting auth headers into curl was the other half of my daily ritual. It's 100% local. No server, no telemetry, no account. Your tokens never leave your browser — by design. Works with Apollo, urql, Relay, Hasura, anything that POSTs to /graphql. WebSocket subscriptions too. Free, forever. Would love your feedback — especially if there's a debugging annoyance I haven't covered yet.

Does it keep the captured operations local in the browser, or do they get sent to a backend for any kind of analysis?

@hamdisdan2s3o All captured operations stay local to your browser. They're kept only in memory while the extension is running and are never sent to a backend or external service for analysis.

Mine was: open Network tab see 12 identical rows named "graphql" click each one expand the JSON find the operation name.
Every day. It's the whole reason GraphPeek exists.

Curious what everyone else's is worst DX pain when debugging GraphQL? Genuinely asking, because the best feature ideas so far have come from complaints, not requests.

Mine was: open Network tab see 12 identical rows named "graphql" click each one expand the JSON find the operation name.
Every day. It's the whole reason GraphPeek exists.

Curious what everyone else's is worst DX pain when debugging GraphQL? Genuinely asking, because the best feature ideas so far have come from complaints, not requests.

Does it keep the captured operations local in the browser, or do they get sent to a backend for any kind of analysis?

@hamdisdan2s3o All captured operations stay local to your browser. They're kept only in memory while the extension is running and are never sent to a backend or external service for analysis.

GraphPeek

Make sense of every GraphQL request your app makes.

Make sense of every GraphQL request your app makes.

Forum Threads

What's your most annoying GraphQL debugging ritual?

Forum Threads

What's your most annoying GraphQL debugging ritual?