Connections that stay open, read as they happen.
A WebSocket, a Socket.IO namespace, an event stream or a gRPC stream is an item in the project like a request is. Each one has a live log you can pause, filter and copy from, saved messages to send again, and a plain-words line saying why a connection dropped.
Shared by every live pane
gRPC without a code generator.
Messages are built from descriptors at run time — from the server's reflection, or from your .proto files with their import folders and the well-known types.
Three transports
Native gRPC over HTTP/2, plain or TLS. gRPC-Web, reading grpc-web-text and gzip bodies too. Connect. The web transports need .proto files and do unary and server-streaming calls.
All four shapes
Unary, server streaming, client streaming, bidirectional. Invoke as a batch — a client stream is a JSON array — or keep a live stream open: send one message at a time, half-close when you are done sending, cancel when you are not.
What comes back
Response headers and trailers, the status code with its name and message, the time, every message sent and received, with a live sent / received counter. A skeleton of the request message written for you.
Forgiving targets
https:// or grpcs:// means TLS, a path is dropped, a missing port is 443 under TLS. dns:///, unix:, passthrough: and xds: resolver forms are passed through.
Metadata and auth
Metadata rows; bearer, basic and API key become metadata; -bin keys are base64-decoded for you.
Limits
Reflection v1 with a fall-back to v1alpha, 20 s. A call waits up to 120 s. Native gRPC trusts the Network page's CAs; client certificates apply to gRPC-Web and Connect.
WebSocket, Socket.IO, SSE, STOMP.
Four kinds of long-lived connection, each a first-class item with its own composer, log and settings.
WebSocket
ws and wss, headers and auth on the handshake, subprotocols. Send text or binary, ping by hand, answer the server's pings. Binary frames shown as hex. The close code and its reason, and the messages you saved to send again.
Socket.IO
Socket.IO v4 and v5 over Engine.IO v4. Namespace, the auth payload, a custom path. Every server event logged without subscribing by name. Emit with arguments and ask for an acknowledgement — the round trip is timed. Answer the server's own ack requests. Binary attachments shown.
Server-sent events
GET or POST with a body. Events, data, ids, retry and comment lines parsed. Browser-style reconnect with Last-Event-ID for GET only — a POST is never repeated. The server's retry honoured, 204 ends the stream, a non-2xx refusal is final. Filter by event name or data.
STOMP over WebSocket
STOMP 1.2 on a WebSocket item: CONNECT with host, login and heart-beats; SUBSCRIBE with auto, client or client-individual acknowledgement; ACK and NACK; SEND with headers and a receipt; RECEIPT and ERROR frames named. For a STOMP broker over TCP, see Messaging.