You’re everyone’s search engine — interruptions shred your focus.
Use cases
For engineering
Ground the answer, ship the PR, and let it close the review loop itself.
Map an unfamiliar repo, implement to a PR verified in a sandbox — then Gently fixes failing CI and addresses reviewer comments on the PR automatically, so it merges while you focus elsewhere.
Answers grounded in real code and git history — onboarding and debugging, fast.
Every change is a reviewable PR, verified in a sandbox — not a guessed diff.
Failing CI and reviewer comments are addressed automatically on the PR.
One real thread, start to finish
Add login rate limiting — and close the PR loop
northwind / api
P
PriyaAsk
Where is login handled, and why does it skip our rate limiter?
Worked for 11s · 7 tools
The limiter only wraps the API router; login posts to a separate route that bypasses it:
- Login — server/routes/auth/login.post.ts — no limiter
- Limiter — middleware applied in server/api/[...].ts only
References
server/routes/auth/login.post.ts:1
server/middleware/rate-limit.ts:18
P
PriyaImplement
Add a 10/min/IP limiter to login with a 429 path, plus tests. Open a PR.
lint
test
commit
push
pr
Add rate limiting to the login route#438
open 18/18 passed
P
PriyaPlan
Before I pick a backend — compare an in-memory limiter vs Redis in parallel.
Fan-out — Compare two rate-limit backends
in-memory limiterimpl
redis limiterimpl
Synthesis posted: Redis for multi-instance correctness; in-memory fine for a single node.
P
PriyaAsk
Where is login handled, and why does it skip our rate limiter?
Worked for 11s · 7 tools
The limiter only wraps the API router; login posts to a separate route that bypasses it:
- Login — server/routes/auth/login.post.ts — no limiter
- Limiter — middleware applied in server/api/[...].ts only
References
server/routes/auth/login.post.ts:1
server/middleware/rate-limit.ts:18
Ask, plan, or build anything…Auto
After the PR opens
Gently closes the loop on your PR — automatically.
Failing CI and reviewer comments come back into the same thread as follow-up runs. Gently handles each one and pushes, so the PR moves toward merge while you’re elsewhere.
Add rate limiting to the login route#438
18/18 passedCI failed — a flaky-looking timeout in the limiter test
Gently made the window deterministic and pushed — CI re-ran green
Reviewer left 3 comments — Gently called ListReviewThreads
Addressed 2 (committed + replied + resolved); declined 1 with a reason
Today this plays out as separate follow-up runs in the thread, with a guard so it never loops forever.
PR review and CI babysitting eat the day after the code is written.
Repetitive “fix the failing check / address this comment” loops are pure toil.
What you can do
Engineering, in one workspace.
Codebase archaeology
“Where is X / why does Y happen” — grounded in real code and git history.
Verified diffs
Implement to a PR that ran lint, tests, and a sandbox — review a working change.
Auto-fix CI
A failing check comes back into the thread; Gently fixes it and re-runs.
Address review comments
It reads every open review thread, fixes or replies, and resolves each one.
Ask mode Plan mode Implement → stages → PR Auto-fix CI Address review comments Fan-out
Gently for every team
Give engineering 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