Shared Playground State for GraphQL | Cosmo by WunderGraph - WunderGraph
Share any GraphQL session with a single URL
Generate a link that encodes the complete session — operation, variables, and headers. Recipients open it and see the exact playground state, ready to run.
No external storage. The session state is encoded directly in the URL.
The problem
GraphQL context gets lost in translation
Sharing a query means sharing the operation, the variables, and the headers. Without all three, the recipient cannot reproduce the session.
Sharing queries means copy-pasting across chat tools
Queries sent in Slack miss variables. Headers are forgotten. The recipient spends time reconstructing context before they can even run the request.
Bug reports without reproduction steps waste time
An issue that says "this query returns wrong data" cannot be investigated without the exact query, variables, and headers. Getting that context requires back-and-forth.
Onboarding requires walking through query setup manually
A senior engineer cannot hand a new team member a working example without a meeting. There is no way to pre-configure a playground session for someone else.
Our solution
A URL that encodes the complete session
Shared Playground State generates a URL that encodes the operation, variables, and headers from your current session. Recipients open the link and see the exact state you configured, ready to execute.
From session to shareable link
- Click the Share icon in the playground toolbar.
- Choose which elements to include: the operation is always included. Variables and headers are optional.
- The playground compresses and encodes the selected state into a URL.
- Copy the link and send it via Slack, email, or a documentation page.
- Recipients open the link. The playground restores the session into a new tab.
- The session opens ready to execute — no manual setup required.
Before & After
| Before Cosmo | With Cosmo |
|---|---|
| Copy query text into Slack, hope variables are remembered | Share a single URL that includes the complete session |
| Bug reports lack reproduction context | Link contains the exact query, variables, and headers |
| Manual onboarding for every new query example | Reference queries linkable from documentation or wikis |
| Headers and auth context must be re-explained | Headers included in the shared link (optional) |
Link contents
What's included and what's not
Included
Always: operation.
Optional: variables, headers.
Not included
Pre-flight scripts, pre-operation scripts, and post-operation scripts are never included in shared links.
How Shared Playground State works
01
Operation required. Variables + headers optional.
Select
Click Share in the playground toolbar. Choose which elements to include. The operation is always required.
02
Compressed URL encoding.
Encode
The playground compresses and encodes the selected state into a URL. No server is involved in storing the session.
03
Opens in a new tab for the recipient.
Share
Copy the link. Send it in Slack, add it to a ticket, or embed it in documentation.
04
Session opens in a new tab.
Restore
The recipient opens the link. The playground restores the session into a new tab, ready to run.
Capabilities
What you get with Shared Playground State
One-click sharing
Generate a shareable URL with a single click from the playground toolbar. No copy-pasting required.
Complete context
Include the operation, variables, and headers. Recipients see the exact session you configured.
Instant reproduction
The session opens in a new tab, ready to execute. No manual setup.
Documentation integration
Link to example queries in internal wikis, engineering tickets, or team documentation.
Share your next query in one click
Generate a URL that encodes the full session. Send it in Slack, add it to a ticket, or embed it in documentation.
FAQ
Shared Playground State on Cosmo
- How do I share a playground session?
- What is included in a shared link?
- Can anyone open a shared link?
- Are headers safe to include in shared links?
- Does the session open in the same tab?
- Are scripts included in the shared link?
More in the shared playground state documentation.