Setting up an environment on the right branch to repro is slow and flaky.
Use cases
For QA & testers
Generate a test plan, execute it on the real app, and gate every PR.
Turn a feature into a test plan you review, run it against a live sandbox with video proof, and wire it up so every pull request runs the same checks — failing tests are fed back and fixed automatically.
Gently handles the project setup. Each thread gets its own isolated environment and running preview, so you can work without local installs or waiting for a shared environment to be fixed.
A test plan generated from the real feature — you review it, then run it.
Execution on a live sandbox with screenshots and video as evidence.
A PR test gate that runs the plan and feeds failures back to be fixed.
The request and the working result
Test a successful and a failed delivery.
QA asks
A courier accepts a route, delivers one order, and cannot deliver another. QA needs to check what happens next.
Task prompt
Test that a courier can accept a route, deliver an order, and mark another delivery as failed. Check the customer emails too.
Read the full task prompt
Test that a courier can accept a route, deliver an order, and mark another delivery as failed. Check the customer emails too. Follow-up: Re-test accepting a route, delivering one order, and marking another delivery failed in the browser. Use demo orders with customer email addresses and check both emails. Follow-up: Summarize the completed browser checks and the two verified emails in a short checklist.
Crosstown is a fictional delivery app. This capture comes from actual work in Gently.
Test plans live in a doc; nobody executes them consistently.
Manual smoke tests don’t run on every PR, so regressions slip through.
What you can do
QA & testers, in one workspace.
Generate test plans
A plan built from the real feature — happy path plus the edge cases.
Execute on the real app
Run the plan on a live sandbox and capture screenshots + video of failures.
Bug or expected?
Settle it from the real code instead of escalating to engineering.
PR test gate
Every PR runs the plan; failing tests are fed back and fixed automatically.
Test plans Live sandbox Browser capture Test gate Auto-fix CI
Gently for every team
Product managers
Feasibility → an approved plan → a working prototype + PR.
Designers
Wireframe to align, live preview to verify, PR to ship the polish.
Engineering
Implement to a verified PR, then auto-fix CI and address review comments.
Operations
Jira/cron triggers, auto-triage, and internal scripts as PRs.
Give qa & testers a safe way to work with the product.
Start with questions. Grow into plans, previews, tests, and pull requests when your team is ready.
Request access