Launching today
Probe
Native API client for humans and agents
14 followers
Native API client for humans and agents
14 followers
Probe is a fast, native, local-first API client for HTTP, GraphQL, and WebSocket APIs on macOS, Windows, and Linux. Use one OpenCollection workspace across desktop, CLI, CI, and coding agents — without accounts, cloud workspaces, Electron, or WebViews.
Hey Product Hunt 👋
I built Probe because I wanted an API client that worked the same way whether I was using a desktop app, scripting requests in a terminal, running them in CI, or handing the task to a coding agent.
Probe is a native, local-first API client built with Rust and GPUI. Your API workspace is stored as OpenCollection YAML, so it stays on your filesystem, works naturally with Git, and can be used by both the desktop app and CLI.
There’s no account, no cloud workspace, and no telemetry. The desktop app also doesn’t use Electron or WebViews.
Performance was another reason I wanted to build Probe natively. On my M4 test Mac, it restores an empty session in a median 265 ms, a 1,000-request collection in 296 ms, and even 10,000 requests in 538 ms. It typically sits at around 80 MB of RAM. I’ve published the benchmark methodology and raw results on the website rather than just calling it “fast.”
Probe supports HTTP, GraphQL, WebSocket, environments, variables and secrets, response inspection, Postman and Yaak imports, plus a CLI designed for automation and coding agents. There’s also an installable Probe agent skill so agents can learn how to work with the same API collection you use.
Probe is still a young open-source project, and that’s a big reason I’m launching it here. I’d really like to hear what feels missing, confusing, or unnecessary — and what would make you consider using Probe in your own workflow.
Thanks for checking it out 🛰️
Keeping the collection in Git while sharing it between the desktop app and CLI makes a lot of sense. I'd want a request fixed during debugging to be the same one that runs in CI.
@oleksii_sekundant Exactly! That's one of the main reasons I built Probe this way. I'm also planning to add assertion support, which should make Probe even more useful in CI. Thanks for checking it out!