ZREQ // DESKTOP API CLIENT IN RUST

// a from-scratch API client — Tauri v2 desktop shell · cyberpunk HUD · powered by zreq-core

Engineering Report GitHub

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, history, code generation and curl/Postman/OpenAPI import 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.

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 an embedded terminal, 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
        └── 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.