Isolated execution
Every run gets a disposable cloud workspace. Your laptop never becomes the runtime.
Managed PR repair inside disposable E2B sandboxes. Critique reads the review artifact, patches in scope, validates the work, and pushes only when the branch is reachable.
+ guard stale review state before publish
+ add regression coverage for fork fallback
~ rerun lint, test, build in sandbox
Commit is allowed to touch the PR branch only after project checks clear.
A narrower blast radius
The generated reference image leaned into a gapless bento: fewer cards, bigger surfaces, and useful proof instead of decorative widgets. This implementation keeps that structure and lets each panel earn its space.
Every run gets a disposable cloud workspace. Your laptop never becomes the runtime.
If the agent reaches outside the review contract, the run stops instead of improvising.
Lint, tests, build, and project checks decide whether a patch is allowed to leave the sandbox.
The run retries once, then hands back a precise artifact instead of burning time forever.
Pick economical lanes for simple repairs and frontier reasoning for structural work.
Machine-readable finding from the Critique review — Remedy reads the structured record, not a chat comment.
Every step ran inside the e2b sandbox. Nothing touched your branch until the full bundle returned green.
From finding to branch
The reference direction uses a pinned narrative: one stable promise on the left, and a stack of artifacts moving on the right. In code, each frame scales in and fades with ScrollTrigger.
The machine-readable review output becomes an execution contract: files, findings, scope, and validation steps.
A clean E2B runtime clones the PR head and runs the fix away from your machine and shared host state.
The selected model writes the bounded fix, updates tests where needed, and leaves a reviewable artifact.
Passing runs commit back to the PR branch when the GitHub App can access the head repository.
Remedyisnotasuggestionbox.Itisaboundedrepairsystemthatturnsreviewevidenceintocode,validatestheresult,andleavesaclearaudittrailwhenautomationshouldstop.
Execution choice
Teams with existing agent subscriptions can reserve Critique credits for review and queue Cursor, Claude, or Codex from the same blueprint — or paste a Fix prompt into Copilot and Claude Code.
BYOA
Queue from a review run with your Cursor API key — same blueprint, your plan.
BYOA
Server-side Anthropic key launches a managed session on the PR.
BYOA
Queue OpenAI Responses runs or export JSON for Codex cloud / CLI.
BYOA
Paste the blueprint into Claude Code, Copilot, or any agent workflow.
Model routing
Simple lint and nullability fixes do not need the same execution lane as a behavioral security change. Remedy exposes model floors clearly, then prices the full managed run around execution and verification.
“The useful part is not that it writes code. It knows when the fix is outside the contract.”
Model selector
17 lanesSmall, cheap patches with an open Google lane.
model floor
Safety cap
2 loops maxCredits
The model floor is only the starting point. A managed Remedy run also includes sandbox setup, repository clone, validation, git operations, and optional re-review when loop two is needed.
Selected model
Run outcome
Estimated total
Connect GitHub, run Critique on a pull request, and let Remedy turn validated findings into a tested branch update.