hitspec docs
Output AI-readable documentation (llms.txt) for AI agents to learn hitspec syntax.
hitspec studio
Open the keyboard-first interactive app for working with hitspec files, right in the terminal.What It Provides
- Inline
.httpand.hitspecsource editing with syntax highlighting and save - File tree, request table, response viewer, headers, assertions, and history
- Stress, mock, contract, record, import, cookies, and settings screens
- Copy/export as curl, HTTPie, Python, fetch, or Go; workspace search; environment switching
- Command palette and keyboard-first navigation
- Real-time file watching and execution progress
Flags
Themes
studio ships with five built-in color themes: Nord, Catppuccin Mocha, Dracula, Tokyo Night, and Gruvbox Dark. Switch at any time withctrl+t (or the command palette), or set one at launch with --theme:
Examples
hitspec serve
Start the REST/WebSocket API server for scripts and integrations. With no flags it openshitspec studio; pass --api-only to run just the API with no interactive UI.
What It Provides
- REST endpoints under
/api/v1/* - Realtime events over WebSocket at
/api/v1/ws - The same parser, runner, history store, and engines as the CLI
serve.
Flags
Security
The REST/WebSocket API can read/write and delete files, execute arbitrary requests (SSRF), and run shell commands when--allow-shell is set. By default it
binds to localhost only, which limits exposure to your machine. If you bind to a
network address (--host 0.0.0.0) or expose the port, set --api-token (or
the HITSPEC_API_TOKEN env var) to require a shared secret. Clients must then send
Authorization: Bearer <token> (REST) or ?token=<token> (WebSocket, which cannot
set headers on the upgrade request). Requests with a missing or mismatched token
get 401 Unauthorized.