Connect the repo
YCall reads the codebase, recent changes, failing jobs, and the task thread before touching code.
YCall investigates urgent codebase tasks, writes focused fixes, runs validation, and hands you a clean PR while you keep building.
Investigate why OAuth refresh fails after the latest session middleware refactor. Patch and prove the fix.
Read failing job, recent commits, and auth middleware
Narrow session refresh guard and update regression test
npm test auth/session-refresh.spec.ts -- --runInBand
Diff is 42 lines, risk notes attached, reviewer requested
$ npm test auth/session-refresh.spec.ts
✓ refresh token survives middleware redirect
✓ expired cookie path returns reauth state
✓ no regression in GitHub provider callback
diff --git app/auth/session.ts
- refreshOnRedirect: false
+ refreshOnRedirect: isTrustedReturn(url)
Fixes refresh handling in authenticated redirects. Includes regression coverage and a note on untested SAML providers.
Why now
Engineers now produce more code, tests, and dependency churn per week.
Small urgent fixes steal deep work from the person best positioned to move product.
The hard part is no longer typing code. It is proving the change is safe.
Workflow
It behaves like a careful teammate: reads context, shows its work, validates changes, and keeps the final merge under your control.
YCall reads the codebase, recent changes, failing jobs, and the task thread before touching code.
Send the bug, flaky test, upgrade, or cleanup request while you stay in your current task.
It investigates, patches, explains tradeoffs, and exposes logs instead of hiding behind magic.
You get a focused diff, test evidence, and a merge-ready summary with human approval preserved.
Use cases
Trust model
Runs in isolated task environments with explicit repo access boundaries.
Every proposed fix ships with commands run, outputs captured, and gaps named.
YCall can draft and validate, but developers keep approval over the final code path.
Private beta
Early access is focused on developers with active repos, frequent CI failures, or recurring maintenance work that keeps breaking flow.