1
qckfx gives your agent a baseline. Record a simulator session once. Every tap, scroll, and network response gets captured. On replay, each screen is compared against the original.
With our MCP, your agent triggers the tests and gets back visual diffs of exactly what changed. Updating the baselines is one click.
Under the hood:
- Full network replay (HTTP & WebSocket)
- Initial disk & keychain state captured during recording and restored on every run
- Precise scroll positioning (built from scratch; XCUITest only exposes this on macOS and iPad)
- No AI in the loop at runtime, fast execution
No SDK or code changes needed. Nothing to commit to git. Just download the app and go.
Everything runs locally. Your data stays on your machine.
qckfx records what you're already doing. You tap through the simulator to check your work, and it replays those sessions to catch visual regressions and crashes. No SDK, no code changes, no test files.
How it works: finish a feature, click around in the simulator, hit Cmd+Shift+S. That's your test. Cmd+Shift+T to run it before you push.
It's free, runs locally, and installs via Homebrew: brew install --cask qckfx/tap/qckfx. I'm a solo dev (10 years iOS, ex-Meta) and this is early. Feedback welcome.
The hypothesis I'm exploring: oncall workflows were designed for small teams where everyone knows the codebase. They break at scale because of specialization and context loss before volume becomes a problem.
Some patterns I've heard so far:
- Oncall engineers spending 10-20% of time just routing bugs to the right owner
- Bug reports from CS/sales teams missing critical context (no logs, vague repro steps)
- "Couple hours" average per bug, mostly on investigation not fixing
- Session replay tools too expensive to run at meaningful coverage
I'm trying to figure out:
- Is this universal, or just specific to certain tech stacks/org structures?
- What's the actual breaking point - team size, user scale, something else?
- Has anyone solved this well? What worked?
If you're currently running oncall at a growing company, I'd love to hear:
- What percentage of oncall time is triage/routing vs. actual fixing?
- What broke first as you scaled?
- What have you tried?