The problem
You have 500 saved API requests. You need to find "that one where I was testing the auth flow." Every API client gives you keyword search. If your request URL was /api/v2/sessions and your response body said "token_type": "Bearer", searching "authentication login" finds nothing.
The fix
Recon uses local semantic embeddings (all-MiniLM-L6-v2, runs on your machine, no cloud) to index every request and response. Search by meaning, not keywords.
"authentication login"
→ POST /api/v2/sessions
"user account profile"
→ GET /api/users/42
"comments feedback"
→ GET /api/posts/7/comments
Switching from Postman?
Export your collection from Postman (Collection > ... > Export > Collection v2.1), then click the import button in Recon's sidebar. Your requests, headers, and bodies come with you. No manual re-entry.
Why local-first
- No account required — download and run
- No telemetry — your API requests and responses never leave your machine
- SQLite storage — your data is a file, not a service
- Source is MIT — you can verify all of the above yourself
Features
- Semantic search over full request/response history
- Collections for organizing requests
- Environment variables with
{{var}} substitution
- Import from Postman (Collection v2.1 export)
- Export collections as Git-friendly
.http files
- Save requests without sending
- Sample data on first run — try semantic search immediately
- Named requests
- All standard HTTP methods
- JSON response formatting
- Ctrl+Enter to send
- Copy response body to clipboard
Free
Download and use. No account, no subscription.