Feature status

Postguy tracks every feature in parity/postman-features.toml. That file is the source of truth for this page. Each entry has an area, a tier, a status and notes.

• cargo xtask parity validates the file. A shipped entry must cite evidence. A planned entry must not.
• Run cargo xtask parity --partial to list the partial ones.

The statuses mean:

Totals

cargo xtask parity reports: 116 features, 56 shipped, 46 partial, 13 planned, 1 na.

The one na entry (na.cloud) is in area I. It covers cloud workspaces, sync, sharing, AI assistants, monitors, mock servers, flows and the API network.

Planned

These are not started:

Partial, by area

These are the gaps listed in the notes of the file. Everything not named here is described as working.

Collections

• Drag and drop works inside the tree. Dropping files from the OS onto the app to open the import dialog is missing.
• Context menus lack Add to favourites, Sort A-Z, Collapse all and Reveal in file manager. A few actions are also missing (Run, Export/Import, Copy as cURL).
• Folder variables, auth and scripts work. Folder variables resolve in the request scope chain. Folder scripts run between the collection and request scripts.

Environments and variables

• The variables quick-look popover cannot edit a value in place or add a variable.
• {{var}} chips and autocomplete work. The hover popover has no edit or add-to-scope actions, the list has no scope badges, and it does not list dynamic variables.

HTTP

gRPC

WebSocket

• Handshake redirects, proxies and the managed-header warning are missing.
• The UI composer sends text only; binary and format-specific composers exist in the automation tools (ws_send with binary_base64).
• The timeline has no search, filters, clear/restore or time-diff.
• There is no hexdump view for binary messages.
• The reconnect policy setting is stored but not acted on. Verify, handshake timeout and max message size are applied.

Automation

• Scripts: gRPC requests run request-level scripts only (no collection or folder scripts); WebSocket requests do not run scripts. pm.cookies.jar() and pm.visualizer are missing. bru.sleep, bru.cwd and bru.runRequest are refused with an error (see the scripting API).
• Test Results: Refresh does not re-run post-response scripts.
• Script editors have no autocomplete or line numbers.
• The UI control channel works for inspect, command, set and screenshot. click, key and type are refused. See UI control channel.

Imports and exports

• The all-data zip exports workspace documents. Importing it back restores .json documents only (not files, protos or settings). There is no Settings entry point for it yet.
• Save Response and Send and Download write <workspace>/files/response-<tab>.bin, with no file picker or suggested file name. When the response was compressed, they write the decoded bytes, not the raw wire bytes.

UI shell

• Window: remembered window geometry is missing.
• The sidebar section open state, the splitter position and the two-pane toggle are not restored after a restart.
• Crash recovery restores tabs after an unclean exit. Draft text is in the tab model, but no editor writes it yet.
• Console: rows are not virtualised, and the 1 MB per-body truncation check in the viewer is missing.
• Menus: on Windows and Linux the app uses an in-app menu row (the native menu bar is macOS only). Placing windows on other monitors works on macOS only.
• The shortcut registry has no conflict check.

Platform

• Session restore does not restore window geometry, expanded tree nodes, the recent workspaces list or the certificate list.
• Documentation and releases: the Docus site, the release workflow and the licence list exist. A security review and a final gaps list for v1.0 are missing.

Known limitations

These are the open items from Known gaps, in user terms.

Other leftovers listed in the gaps page: cookie add/edit, the Save Response example picker, splitter persistence, the shortcut-conflict check and History day grouping.