How can we help you?
Search troubleshooting solutions, test your local proxy connection, or connect with the Reex community.
Report a Bug
Found an issue or unexpected response? File a report on GitHub with your reproduction steps.
Feature Requests
Share ideas for new SDK generators, UI workflows, or integrations directly with the team.
Documentation
Learn how to configure proxies, generate clients, manage environments, and customize settings.
Source & Releases
Inspect source code, track version release notes, or star the project on GitHub.
Developer CLI & Proxy Toolbox
Reex Local Proxy CLI
Bypasses browser CORS restrictions for local API endpoints without needing backend configuration changes.
npx reex-proxyReex Code Generator
Generates strongly-typed TypeScript clients and models from your workspace collections automatically.
npm install -g reex-cliTest Local Proxy Status
Verify if reex-proxy is active and accessible on http://localhost:3001.
Frequently Asked Questions
Showing 7 of 7Why do localhost API requests fail with Network or CORS errors?
Web browsers enforce strict Cross-Origin Resource Sharing (CORS) security rules that prevent web applications from sending requests to localhost endpoints unless the target server explicitly returns permissive CORS headers (such as Access-Control-Allow-Origin: *).
To bypass this seamlessly without altering your backend code or security configuration, Reex includes a zero-config local proxy bridge:
npx reex-proxyOnce started, the proxy runs locally on port 3001 and forwards studio requests directly to your services with full header and body fidelity.
Where are my collections, environments, and API keys stored?
Your API data never leaves your computer. Reex operates on a strict local-first architecture with zero remote databases:
- Collections & Endpoints: Persisted in your browser's isolated
IndexedDBdatabase on your machine. - Workspace Preferences & Theme: Kept in your browser's
localStorage. - Zero Telemetry on Payloads: Headers, authorization keys, request bodies, and responses are never sent to any external server.
You retain 100% control and ownership of your API specifications and secrets.
How do I generate TypeScript SDKs and definitions from my endpoints?
Reex allows you to generate end-to-end type-safe TypeScript interfaces, request bodies, response schemas, and typed fetch helpers directly from your collections into your codebase.
npm install -g reex-cliNavigate to your project directory and run reex start. Any modifications you make in the studio will immediately sync and regenerate your TypeScript client definitions.
What is Private Network Access (PNA) and why does Chrome prompt for local permissions?
Modern Chromium-based browsers (Chrome, Edge, Brave) enforce Private Network Access (PNA) security when a website hosted on a public domain attempts to communicate with your private loopback IP (localhost or 127.0.0.1).
If prompted, click Allow to grant permission for Reex Studio to dispatch requests to your local servers. If you decline, requests will fail with a connection error until permissions are reset in site settings.
What keyboard shortcuts are available in Reex Studio?
Accelerate your workflow with these built-in keyboard shortcuts:
On macOS, replace Ctrl with Cmd (⌘).
How do I import collections from Postman, cURL, or OpenAPI?
Reex supports importing existing API specifications so you can transition friction-free:
- Postman Collections (v2.1): Click the Import button in the workspace sidebar and drag-and-drop your Postman export JSON.
- Raw cURL Commands: Paste any valid
curl "https://..."directly into the URL bar and Reex will parse method, headers, query parameters, and body automatically. - OpenAPI / Swagger: Import JSON or YAML schemas to generate complete folder structures.
How do I back up or clear my workspace data?
You can export collections anytime into a portable JSON format through the sidebar collection options menu.
If you wish to wipe local data and reset Reex Studio to a pristine state, clear your browser site data for this domain via your browser Developer Tools (Application > Storage > Clear site data), or visit the Workspace Settings.
Tips for Faster Support
- Include reproduction steps: Explain what you clicked or sent, expected behavior, and actual result.
- Sanitize sensitive tokens: Strip private API keys, bearer tokens, or company secrets from cURL or logs.
- Provide system diagnostics: Copy the diagnostic report from the panel on the right.
- Check existing GitHub issues: Your issue may already have an active fix or workaround.