Turn plans into code in isolated workspaces.

Every task gets its own Docker workspace, Git worktree and branch. The agent edits there. ProPR validates, commits, pushes and opens the pull request.

Isolation boundary Main protected

Repositorymain checkout

Task workspace Arunning

propr-1689branch Docker containeragent runtime

Task workspace Brunning

propr-1690branch Docker containeragent runtime

Pull request Areviewable result

Pull request Breviewable result

ProPR moves the task from repository to isolated workspace to pull request; the main checkout never changes.

Dedicated Git worktree

Each task gets its own checkout. Parallel tasks never collide, and your main checkout never changes.

Docker workspace

The agent runs in a standard container with a read-only GitHub token. Optional restricted network mode limits it to an allowlist of hosts.

Separate branch

Each task gets its own branch. ProPR owns every commit, push and cleanup.

PR review boundary

The change reaches your team as a pull request, with your checks, approvals and merge policy in GitHub. The guide to getting an AI coding agent to open pull requests from GitHub issues follows one task from label to merge.

Skip the plan when the change is clear.

New Task sends one instruction straight to implementation. Describe the change, attach files, and run it. ProPR files the GitHub issue, runs the task in isolation and links the pull request back to it.

Broad or risky changes start in planning. Longer objectives run as Goals.

New task dialog: repository, prompt, agent and model, then Run task or Plan first — One instruction, one repository, one pull request.

Choose the agent, model and PR path before the run starts.

For each approved plan, pick one Epic PR or a pull request per issue, the agent and model, Ultrafix and auto-merge.

Executing a plan as individual tasks: one issue running with its pull request, two waiting, and Queue Remaining to start them in order — One issue running with its pull request, two waiting their turn.

Every task leaves a complete audit trail.

The exact prompt, agent logs, model usage and file changes stay on the task after the run ends. Reviewers see what the agent did, in the web UI or the CLI, and what each AI-written pull request cost.

→ Explore the read-only demo dashboard

A public integry/propr pull request showing its implementation summary, linked issue, branch, commit, agent, model, duration, token usage, cost, and verification. — The public PR keeps the implementation and execution record.

Follow the agent while it works.

The task page streams the run live: why the agent makes a change, the files it edits and the tests it runs. The trace stays on the task afterwards.

The execution trace of a live run in plain language: why the time-zone fix is needed, the new DST test cases, and all 14 checkout tests passing — The live log: the agent explains the fix, edits the file and runs the tests.

See the change before you open the branch.

Visual previews put a screenshot or video of the changed screen on the pull request, and every follow-up commit posts fresh ones.

Visual previews switched on for storefront-web: images and videos, the detected GitHub attachment limits, and capture instructions

Opt-in per repository

Choose images, videos or both, and tell the agent which pages or viewports to show.

Visual evidence on a task: the agent’s capture of the changed stop card, under its title and description

Only real captures

The agent records the running change with the tooling your repository already uses, such as Playwright or Storybook.

A visual preview from the goal’s draft PR, loaded from GitHub into the goal console

Private repositories included

The web UI and desktop app show private PR media, and Connect Plus keeps the full-resolution originals.

The repository sets the rules for every run.

Commit a .propr/ folder and every run follows it. Change a rule in a pull request and the next run picks it up. propr init scaffolds the files.

`.propr/workflow.yml`

Setup hooks, agent instructions, the validation commands ProPR runs after the agent exits, a parallel task limit, a per-run spend cap and the network mode.

`.propr/pr-template.md`

Shape the title and body of every pull request ProPR opens, with placeholders for the issue, model, cost and changed files.

Auto-merge with protected paths

The auto_merge block picks the merge method and lists the paths that always wait for a person.

Repository workflow documentation

Check the change before people spend attention on it.

Once the PR opens, /review posts structured findings and a score before a person looks.

See automated review →