Ranger

Visit Website

Introduction

Ranger is a verification tool built for coding agents. The official site says it gives “your coding agent the tools to check itself and keep going”: running ranger go spins up a browser, tests the feature, and returns a verdict.

When Ranger finds a bug, the agent can pick it up, fix it and re-test with Ranger, with no human in the loop. Every review becomes a shareable record with screenshots, video and verdicts. For the wider suite, Ranger recommends end-to-end tests for each feature, triages failures and keeps tests maintained.

Features

1. One command: ranger go starts a browser, tests the new feature, and returns a verdict and a demo.
2. Evidence per change: Screenshots, recordings and traces are attached to each agent change.
3. Agent fix loop: Failures are handed back to the coding agent, which fixes and re-runs.
4. Request changes: People can leave feedback on any scenario; the agent pushes a fix and Ranger re-verifies.
5. Shareable proof: Each review is a record you can attach to a pull request.
6. Smart test selection: Before each deploy, Ranger selects end-to-end tests and triages failures.
7. Self-maintaining suites: Ranger recommends tests for shipped features; once approved they join the suite and are maintained.
8. Parallel browsers: Hundreds of parallel browsers on demand, available to all plans according to the site.

Pros

1. Built for agent workflows: Verification happens where the agent works, which shortens the build-check loop.
2. Evidence, not just pass/fail: Recordings and traces make a verdict auditable.
3. Free tier: A free-forever plan with 5 reviews lets you try it.
4. Simple pricing: Growth is a flat per-user monthly price with unlimited reviews.
5. Human review stays possible: Change requests on scenarios keep people in control.

Cons

1. Auto-fix loops need limits: An agent fixing and re-testing its own work can converge on the wrong behaviour; keep humans reviewing.
2. Hosted browsers: Runs use Ranger’s infrastructure; check data handling for your app.
3. Newer product: Fewer public case studies than established test platforms.
4. Web focus: Published material centres on browser testing.
5. Enterprise is usage based: Large-team pricing needs a sales conversation.

Usage and Links (Example)

The site’s quick start installs a CLI with a shell script and then runs one command:

curl -fsSL <install script from ranger.net> | sh
ranger go

Use the exact install command shown on ranger.net and the docs. After a run, open the review to see the verdict, screenshots and recording, and attach it to your pull request.

Resources:

• Ranger website
• Pricing

Pricing

From Ranger’s pricing page:

1. Free: Free forever. 5 reviews, self-serve install.
2. Growth: $50 a month per user. Unlimited reviews, self-serve install, support via Slack or email.
3. Enterprise: Usage based. Contact sales.

Recommended for?

1. Developers working with coding agents who want each feature checked in a browser before review.
2. Small teams that want unlimited agent reviews at a flat per-user price.
3. Teams that value evidence such as video and traces on every pull request.
4. Not a fit for mobile-native or desktop-heavy products.

Conclusion

Ranger turns browser verification into a step a coding agent can call by itself, and it records evidence for people to review. The free plan and flat Growth price make it easy to try.

Keep a human in the loop for auto-fix cycles, and pair it with deterministic tests for critical paths.