Common Questions

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.

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.

React + Vite and React + webpack (dev bundler) are confirmed working as of 1.1.0. Next.js is not yet supported — the source-map resolver has a known issue with Turbopack's output (see Known Limitations below). The core pipeline — source map resolution, file patching — is framework-agnostic in design, but each bundler's source-map format needs its own handling to work reliably.

In an automated end-to-end test run against a real React/Vite project, ERRase detected 11 of 13 realistic error categories. Detection is the strong part — fix quality is more mixed: most generated fixes are safe, guard-clause-level patches (e.g. an optional-chaining check) rather than true root-cause rewrites. Treat every suggestion as a starting point, not a verdict, and review the diff before applying.

The biggest one: Turbopack's source maps are sparse around HMR/refresh boilerplate, which can cause the resolver to confidently map an error to the wrong file. This is a diagnosed, known issue — not a silent failure — and is why Next.js isn't supported yet. Separately, as noted above, most AI-generated fixes are guard clauses rather than root-cause fixes, so review before applying.

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

openai/gpt-oss-120b 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.

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.

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.

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.