wuzz CLI
The interactive HTTP client lets you inspect a browser request, change parameters and explore its response in the terminal.
- 10,740 ★ on the repository
- Last commit
- AGPL-3.0
Extended access
Why this level
- Users send requests with supplied headers and may save confidential responses to disk.
Install
Manual install
Use the binary releases linked from the README and select a platform build. Do not invent a replacement for the outdated Go command. Prepare a safe test request and explain interactive controls.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Users send requests with supplied headers and may save confidential responses to disk.
This is third-party code. Review the repository files before installing.
What it does
wuzz presents HTTP requests and responses in terminal panes. Users change the URL, method, headers and body, then send and inspect the result. Curl-like arguments support inspection of requests copied from browser tools. An agent can prepare test-API parameters and explain differences while the operator sees results, saves requests or responses and repeats the experiment. Search supports HTML and JSON-specific filtering.
Who it is for. API testers reproducing individual browser requests and adjusting them interactively in a terminal.
Good fit when
- A copied browser request needs testing with different parameters.
- A large API response needs a particular field located.
- An agent discussion needs a saved reproducible request.
- Debugging runs over SSH without a graphical API client.
Not a fit when
- The test must run without an interactive terminal.
- Modified requests must not reach the selected service.
- You expect modern go get to install the binary from the first example.
Example request
Prepare a secret-free test API read request for wuzz and explain which parameters to compare manually.Limitations
The first install example uses outdated go get behavior: Go 1.18 and later do not build executables with it, so use a published binary release. The interface requires an interactive terminal, limiting fully unattended agent use. Requests execute against the service and can change data; use a test environment. Saved requests and responses may contain credentials or personal information; inspect them before sharing in chat or Git.
How to disable. Exit wuzz and remove it from debugging workflows. Saved requests and responses remain as separate files.
FAQ
How do I send a request?
Press Ctrl+R, or Enter from the URL pane.
How do I save a response?
Use Ctrl+S; Ctrl+E saves the request separately.
Where is configuration stored?
Linux uses the XDG configuration directory; other platforms typically use `~/.wuzz/config.toml`.
Can I search response bodies?
Yes. It supports regular expressions and context-specific HTML and JSON queries.
Where are keyboard shortcuts shown?
Press F1 in the interface.
Discussion
No questions or reviews yet.
Related
CLI toolswebsocat connects to WebSocket services from the terminal, sends text or binary messages and supports protocol debugging.
A headless WebKit browser verifies pages in one call, scores pixel diffs and hands the live session to a human.
An MCP server that spins up several browser agents to test a site for broken links, UI bugs and accessibility issues
One binary for agent browser automation: a CLI with browser and check skills, an MCP server and clients for JS, Python and Java
The CLI runs QA Wolf flows locally and in CI, refreshes cached tests and helps investigate traces from failed attempts.
The CLI runs HTTP request chains from plain-text files and checks response status, headers and body content.
README in short
Keyboard commands switch URL, header and body panes, with request history available in the interface.