Four things the FAQ used to list under "What's missing today?". Each was the thing people moving from Paw hit most, and each works the way the rest of Retriever does: local files, variables everywhere, and responses you can chain from.
A cookie jar
Log in once and the session cookie comes along on the next request, as it would in a browser. Cookies a server sets, including on the redirect after a login and on WebSocket handshakes, are kept per domain and path and sent back only where they belong, and only over HTTPS when they're marked Secure. Request → Cookies… (⌥⌘K) shows them by domain; edit, add or delete any of them. A request that should stay cookie-free can switch the jar off in its Docs tab, and a Cookie header you type yourself always wins. The jar lives in cookies.json beside your workspace, readable only by you, and the MCP server uses the same one.
GraphQL, with the schema at hand
GraphQL is now a body type: a query editor that highlights and auto-closes braces, and a separate pane for variables, which can use {{variables}} like anything else. Fetch Schema introspects the API with the request's own headers, auth and cookies. Browse the queries, mutations and types, press Use on a field to get a complete operation with a variable for every argument, or Insert to add a field to what you have. A 200 that still carries errors gets a badge, so it doesn't pass for a success.
WebSockets
Switch a request's method pill to WebSocket, press ⌘↩ to connect, and send text or JSON messages, as many as you like. The response side becomes a conversation: what you sent, what came back, timestamps, a filter, and a ping that times the round trip. Headers, params, auth and cookies all go with the handshake. When the socket closes, the transcript is saved to History, and other requests can chain from it.
gRPC
gRPC requests call a service method over HTTP/2, with TLS or, for a server on your own machine, without. Retriever asks the server for its services through reflection, or reads your .proto files and whatever they import. Pick a service and method, press Template for an example message, and write it as JSON: 64-bit numbers as strings, enums by name, timestamps as dates. Unary and server-streaming calls are in; client streaming takes a JSON array of messages. The status shows by its gRPC name, NOT_FOUND rather than 404, and still counts as its HTTP equivalent, so chains, failure explanations and the OAuth token refresh behave the way they do for HTTP. Copy as cURL gives a grpcurl command instead.
Retriever speaks HTTP/2 itself for this, because the system's networking can't reach a plaintext local gRPC server or read the status gRPC sends after the body. There are still no third-party libraries in the app.
For agents
The MCP server has four new tools: list_cookies, clear_cookies, graphql_schema and grpc_describe. create_request and update_request accept GraphQL variables, WebSocket and gRPC requests, and sending a WebSocket request returns the conversation.
Good to know
- A workspace with GraphQL, WebSocket or gRPC requests needs 0.8.0 or later. An older version refuses to open it rather than change it.
- Not yet: Server-Sent Events, GraphQL subscriptions, interactive client and bidirectional gRPC streaming, and compressed gRPC messages.