A local-first HTTP client built on GPUI.
ReqFlux reads and writes Postman collection v2.1 and environment files, runs Postman
pm.* scripts, and lets AI agents manage collections and send requests through MCP.
ReqFlux is a standalone app: opened from your desktop it shows your own workspaces, kept by
the app under ~/.local/share/reqflux/workspaces, and creates one named Personal on the first
run. A workspace is a directory of small TOML files, so one can also live in a repository
next to the code it calls, where collections diff, merge and review cleanly in git.
Status: the MVP of FEATURES.md is in place. See ARCHITECTURE.md for how it is built.
Linux, plus nightly macOS disk images.
-
Nix, prebuilt nightly (nothing compiles):
nix run github:0xErwin1/reqflux/nightly#reqflux-nightly. Use thenightlyref, notmain: only that ref holds the hash of the published tarball. The package installsreqflux-nightlyand a "ReqFlux Nightly" desktop entry. With home-manager:inputs.reqflux.url = "github:0xErwin1/reqflux/nightly"; home.packages = [ inputs.reqflux.packages.${pkgs.system}.reqflux-nightly ];
The flake also exports
overlays.default(pkgs.reqflux-nightly,pkgs.reqflux-source,pkgs.reqflux). -
Nix, from source:
nix run github:0xErwin1/reqflux#reqflux-source, or from a clonenix build .#reqflux-source. -
Nightly: once a day, when
mainhas new commits, a prerelease under the single tagnightlyis replaced with a freshreqflux-linux-amd64.tar.gz(binary, desktop entry and icons) andreqflux-macos-amd64.dmg/reqflux-macos-arm64.dmg("ReqFlux Nightly.app"); see the releases page. The disk images are not notarised: open the app the first time with right-click > Open. -
Local build: from the dev shell (
nix develop),cargo build --release -p reqfluxputs the binary intarget/release/reqflux.
nix develop # toolchain, mold and native libraries
cargo run # opens the ReqFlux window on your last workspace (Personal at first)
cargo run -- ~/billing # opens the workspace in the directory ~/billing
cargo run -- run billing-api/invoices/list-invoices --workspace ~/billing --env staging
# sends one request, body to stdout, summary to stderr
cargo run -- run billing-api --workspace ~/billing --environment staging --bail
# runs a collection or folder, one report line per request;
# --json for a machine report, exit 1 on a failed request or test
cargo run -- code billing-api/invoices/list-invoices --workspace ~/billing --lang python
# prints the request as curl, httpie, python or fetch code
scripts/lint.py # fmt, clippy, file-size and layering checks
cargo nextest run # testsWithout Nix you need the Rust toolchain from rust-toolchain.toml, mold, pkg-config
and the GPUI native dependencies (Wayland, X11, xkbcommon, Vulkan, fontconfig, freetype).
Your settings live in ~/.config/reqflux/config.toml, not in any workspace. Agents connected to
reqflux mcp can read; anything else waits in the running window's MCP approvals view
(Ctrl+Shift+M, or the bell, the rail or the status bar count): Allow once, Allow for this
session, or Deny with an optional reason the agent receives. With no window open it is refused. Allow more there:
theme = "system"
font_size = 14 # interface size in px, 8 to 32; 13 by default
[mcp]
write = "allow"
execute = "allow"
hosts = ["api.example.com", "localhost:8080"]The rail's Settings button edits the same file in the app (App > General for the theme and font size, App > MCP policy for the rules and lists). Each change saves at once and keeps your comments and key order; while the file does not parse, those settings stay read-only.
A workspace's reqflux.toml can add an [mcp] table, but it can only restrict. Every change and
execution an agent makes is logged to ~/.local/state/reqflux/audit.log. See "Configuration and
policy" in ARCHITECTURE.md.
Licensed under the Apache License 2.0.