Status: in development. The desktop shell builds and mounts the engine; the engine's per-feature port status is tracked honestly in the zreq-core port report. Nothing here claims a capability that is not in the codebase.
zreq is a from-scratch API client (Postman port) written in Rust — a Tauri v2 desktop application behind a cyberpunk HUD. Collections, environments, variables, auth, request bodies, multi-workspace management, history, per-request last-response restore, a collection runner, code generation and curl/Postman/OpenAPI/HAR/Insomnia/Bruno/HTTPie import all run locally, with no cloud account. Its engine is extracted as zreq-core, an embeddable library so the same engine can be reused inside the other MenkeTechnologies GUI apps. It is a paid product, created by MenkeTechnologies.
Rust + Tauri v2
A native desktop shell rather than an Electron app — the UI is a Tauri v2 WebView, the HTTP egress and all logic are Rust.
Embeddable core
The API-client engine lives in zreq-core, decoupled from the GUI, so the same code embeds in other MenkeTechnologies apps over one JSON command surface.
Local & owned
No cloud workspace, no sign-in. Collections, environments and history persist as JSON on your machine.
Cyberpunk HUD
The same HUD design language used across the MenkeTechnologies desktop stack — Orbitron / Share Tech Mono, CRT scanlines, neon accents, embedded terminal, file browser, stryke hooks editor. ⌘Enter sends the request from anywhere in the window, Postman-style.
Protocol panels
Beyond HTTP: interactive WebSocket and gRPC panels, a GraphQL Explorer that introspects a schema and runs queries, an OAuth 2.0 token manager (client-credentials / password / refresh) and a structural JSON response-diff panel.
Tools workbench
Local-only utilities beside the request pane — JWT decode/sign, encode/decode converters, hashes and HMAC, JSONPath/JMESPath, JSON↔XML, JSON-Schema validate/infer, secret scan, PKCE, CBOR/MessagePack/protobuf codecs, assertions, fuzzing, HAR analyze, OpenAPI diff/mock, cache and retry simulation, collection lint and export.
Causal Session Replay
Mines the recorded session's real request-to-request data flow by value provenance, then pins one edit and re-executes only the requests it actually reaches, diffed against the recording — session.provenance / blastradius / counterfactual in the engine.
Localized
The interface localizes through the shared zpwr-i18n runtime; every locale it ships is selectable from Settings → ZREQ · Interface → Language, switching live and remembering the choice.
Architecture
zreq splits into two layers: the desktop application (zreq, this repository) and the engine (zreq-core). The application owns the Tauri v2 shell, the HUD front-end and the subsystems that sit beside the API client — an embedded terminal, a file browser, a stryke hooks editor with its own language server, a clip sequencer and an in-process system monitor — and wires user actions to the engine. The engine owns the API-client logic (collections, requests, environments, auth, HTTP execution, history, codegen, import/export) and is designed to be embedded by other host GUIs without dragging in any GUI or platform dependencies.
'zreq (desktop app)'
└── Tauri v2 shell + cyberpunk HUD front-end
+ embedded terminal · file browser · stryke hooks editor + LSP
+ clip sequencer · system monitor
└── consumes 'zreq-core' (embeddable API-client engine)
Where it goes next
See the engineering report for the current status and roadmap. The engine and its Postman-feature port coverage are tracked separately in zreq-core.