Common Questions

Privacy, pricing, supported tools, and how ERRase actually works.

Q.Is it free?

Yes. ERRase itself is free. You bring your own Groq API key — Groq's free tier covers typical daily dev usage comfortably. No credit card, no subscription.

Q.Is my code sent to ERRase servers?

No. Your files are read locally by the CLI running on your machine. Only a ±15 line snippet around the error line is sent to Groq for analysis. ERRase's backend acts purely as a relay — it never stores or logs your code.

Q.What frameworks are supported?

Next.js (App Router) is fully supported today. Vite and Create React App support is in progress. The core pipeline — source map resolution, file patching — is framework-agnostic, so more are coming soon.

Q.Does it work with TypeScript?

Yes. ERRase resolves source maps to map bundled output back to your original .tsx / .ts files. You see your actual TypeScript, not compiled JavaScript.

Q.What AI model does it use?

Llama 3.3 70B via Groq. It's a production-grade model — fast on Groq's hardware, free on their developer tier, and strong at reading and fixing code. You can swap the model by changing one line in the backend.

Q.Do I need to keep a backend running?

No. ERRase's backend is deployed on Railway and always live. The only thing you run locally is the CLI — one command, keeps running in the background while you develop.

Q.What if the fix is wrong?

You review every fix before it's applied — nothing touches your files without your approval. If the suggestion is off, click Dismiss and fix it manually. A Request Revision flow is on the roadmap.

Q.Why does ERRase need a local CLI at all?

Chrome extensions are sandboxed — they can't read or write files on your machine. The CLI runs locally, gives ERRase filesystem access, fetches source maps from your dev server, and writes fixes back to disk. The extension handles UI. The CLI does the real work.