[FAQ]
Common questions.
Does GetWired need my app to be deployed?
No. GetWired tests against your local dev server (localhost). Just run your dev server and GetWired will auto-detect it.
Which frameworks are supported?
GetWired works with any web app that runs on localhost — Next.js, React, Vue, Svelte, plain HTML, etc. It uses agent-browser under the hood, so if a browser can open it, GetWired can test it.
Do I need an API key?
You need credentials for your chosen AI provider (e.g. Claude Code, Auggie, Codex). GetWired itself is free and open source.
Can I use this in CI/CD?
Yes. The `getwired test` command is designed for non-interactive use. It exits with a non-zero code if critical issues are found, making it easy to integrate into your pipeline.
What does it actually test?
GetWired simulates a chaotic human user: clicking random elements, submitting malformed data, testing XSS payloads, rage-clicking, resizing to extreme dimensions, testing keyboard navigation, and more. It's designed to find the things unit tests miss.
Is it safe to run against my app?
GetWired only interacts with your app through a browser — it doesn't modify your code or database directly. However, it will submit forms and trigger API calls, so run it against a dev/staging environment, not production.
Can I add my own AI provider?
Yes. The provider system is a simple interface. Check the GitHub repo for the provider template and submit a PR.
How is this different from Cypress or Playwright tests?
Traditional E2E tests follow scripts you write. GetWired uses AI to explore your app unpredictably — like a real user who doesn't read the docs. It finds the bugs your scripted tests never cover.