Managed
Connect the repo. Read the PR.
Parsemend runs the fix on its own infrastructure with its own model credentials. It needs a GitHub App installation with read access to the repository and write access to pull requests. This is the least setup and the only mode where your source is read by Parsemend's servers.
The four questions
- Where the run executes
- Parsemend
- Who pays for tokens
- Parsemend (included in the plan)
- Model choice
- Chosen by Parsemend
- Source seen by Parsemend
- Read via GitHub App
How the data flows
Parsemend reads the repository through its GitHub App, runs the fix on its own infrastructure with its own model credentials, and opens the draft pull request.
- Your infrastructure
- — nothing runs here
- Parsemend
- source codeerror eventsfix queuefix run
- Model provider
- model call
What Parsemend contributes
Context bundles
The stack trace, the in-app frames, the surrounding source, the breadcrumbs and the recent commits that touched those lines — assembled into one payload an agent can act on without crawling the repo.
Fix-run state machine
Root cause, then solution, then coding, then change description. Each step is a checkpoint. A run that dies at step three resumes at step three rather than starting over.
Confidence gating
Every step emits a confidence score. Below the project's threshold the run pauses and waits for a human instead of confidently shipping a wrong patch.
Draft PR post-back
The patch arrives as a draft pull request against the right branch, with the root cause and the reasoning in the description. It never merges itself.
Who this is for
Teams who want the outcome and are comfortable granting repository access.