For developers · VS Code
Run and debug tests without leaving the editor.
Click play in the gutter, set a breakpoint, and read the trace beside the code. The output stays real TypeScript in your repo.
Inline play buttons
Run one test, one file, or the whole workspace from the editor gutter.
Breakpoint debugging
Step through real TypeScript and inspect variables — not terminal guessing.
Trace beside the test
Requests, responses, assertions, and traces open next to the code.
Trace diff
Compare two runs with native diff to see exactly what behavior changed.
Environment switching
Move across local, staging, and production from the status bar.
Git-native files
Everything stays TypeScript, so review, branching, and refactoring just work.
For Explore · Chrome
Send requests no browser fetch can.
A privileged request executor for the Explore Debug/Send harness. It sends from the extension's background context — not subject to the page's CORS policy — so QA and support can hit real, authenticated APIs straight from the browser.
How a request travels
No CORS preflight · cookies attached · response read back with the real Set-Cookie jar.
Privileged fetch — no CORS
Background requests reach any API: CORS-closed, localhost, intranet. No per-domain config, no preflight.
Reuses your session
Your existing login cookies for the target domain ride along — the one thing a plain fetch or cloud proxy can't do.
Faithful request headers
User-Agent, Origin, Referer, Cookie — the wire request matches exactly what you asked for.
File & multipart upload
Blob bodies bridged from the app; binary-safe responses decoded or returned base64.
Auto-detected
The app routes Debug/Send through it when present, and falls back to a direct fetch when it isn't.
Two surfaces, one workspace
Developers run and debug in VS Code. QA and support explore real requests in the browser. Both feed the same runs, evidence, and agent in Cloud.