The new workbench
A rebuilt editor: reading by default, nodes as tabs, a command palette on every surface, docs for every node kind, and an explorer that leads with endpoints.
In this release
- New
Read by default, edit on purpose
The editor opens in a reading mode with docs for every node kind, and editing is a deliberate switch — browsing a schema can no longer change it by accident.
- New
Nodes open as tabs, with ⌘K to jump
The explorer opens each node in its own tab, the command palette jumps to any node from anywhere, and a relationships map sits under the docs.
- Improved
The explorer leads with endpoints, grouped by tag
Paths come first and group under their tags, and the tree stays responsive at a hundred endpoints and beyond.
- Improved
One dark workbench palette
Panels, graph, tabs and headers share one set of design tokens, and schema resolution no longer blocks the interface while it runs.
Most time in an API tool is spent reading, not writing. The old editor was built the other way round: every surface was an input, and finding something meant knowing where it lived.
This release rebuilt the workbench around reading.
Reading is the default
The editor opens in a reading mode, with rendered docs for every node kind — endpoints, schemas, responses, parameters, security schemes. Editing is a deliberate switch rather than the state you land in, so browsing someone's schema can no longer change it by accident.
Tabs, and a way to reach them
Nodes open as tabs, the way files do in an editor. Clicking through the explorer stacks up what you are working on instead of replacing it, ⌘K jumps to any node from anywhere in the app, and a relationships map under the docs shows what points at the node you are reading and what it points at.
An explorer that matches how you think
Endpoints come first, grouped by tag, because that is how an API is discussed. Components sit below, by kind. The tree was rewritten to stay responsive on documents with hundreds of paths, where the old one visibly stalled.
One surface, not several
Panels, graph, tab strip and headers now draw from a single set of design tokens, so a schema is the same colour in the tree, the palette and the tab it opens in. Schema resolution moved off the main thread, so a large document no longer freezes the interface while it loads.