GraphiQL 6 redesigns its workspace and changes how requests are sent
· BehindLines newsroom
GraphiQL, the in-browser tool for writing and testing GraphQL queries, has reached version 6. According to the announcement posted on graphql.org on 7 November 2026 by Trevor Scheer, the project was paid for by the GraphQL Community Grant scheme. The GitHub release page dates version 6.0.0 to 1 November.
An interface rebuilt around the editors
The editors had already moved to Monaco in version 5. Version 6 reworks the whole workspace: navigation, tabs, menus and dialogs. The release notes mention light and dark themes, an endpoint bar, a resizable side panel and a status bar. The announcement adds that keyboard focus markers are easier to see and that the team's test suite now includes automated accessibility checks.
Three additions for daily use
- Query builder: tick fields from the schema and the operation writes itself into the editor. Users can switch between the builder and plain text, extract fields into a reusable fragment, or promote an argument to a variable.
- Collections: operations are saved under a name, shared as JSON and imported without creating duplicates. By default they live in the browser; an organization can plug in its own storage.
- Three response views: raw JSON, a collapsible tree, or a table. The choice survives a page reload.
The transport API gradually replaces fetcher
The most technical change concerns how requests leave the page. The new `transport` API returns HTTP details with the result: method, status, elapsed time and response size. To pick a method, it first sends an OPTIONS request and reads the `Allow` header. For read operations it prefers QUERY, then POST, then GET; if discovery fails it falls back to POST, and mutations always use POST. The project recommends migrating, but `fetcher` still works and is only deprecated.
What to check before upgrading
The announcement does not list breaking changes and points to a migration guide. The release notes do list several: graphql-js versions 15 and 16.0 to 16.10 are no longer supported, the Explorer plugin gives way to the query builder, the `operationName` prop is removed, and the old `--color-*` CSS variables no longer style the interface, replaced by OKLCH tokens. For an existing integration, the announcement advises starting with the migration guide.