Dedicated Git worktree
Your chosen agent edits a task-specific worktree. The developer's main checkout remains untouched.
ProPR prepares a separate worktree, branch, and Docker runtime for every task. The agent edits inside that boundary. ProPR then validates the result and returns it through commits and a pull request.
Your chosen agent edits a task-specific worktree. The developer's main checkout remains untouched.
The agent runs in a standard Docker container with bridge networking and no elevated privileges — no --privileged flag and no added network capabilities. For hardened deployments that can grant NET_ADMIN, an optional allowlist firewall (off by default) restricts outbound traffic to the model provider's API, GitHub, and DNS.
Each task receives its own branch, leaving the main checkout untouched.
The PR is where generated code becomes team-visible work and where follow-up refinements continue.
Prompts, reports, commits, changed files, logs, review notes, and usage stay attached to the task.
Stop, delete, retry, follow up, or revert a task when a run goes wrong.
Use the CLI for task list/get/stop/delete/revert commands in terminal automation.
Every task runs in three phases. ProPR controls workspace preparation and delivery; the agent owns implementation inside the task boundary. Branching, commits, pushes, and pull-request creation follow deterministic application code.
ProPR updates the repository, creates the task worktree and branch, and prepares the workspace deterministically.
The coding agent reads context and edits files inside the isolated workspace. It inspects its own worktree while ProPR retains control of branching, pushing, and PR creation.
ProPR validates the result, commits, pushes the branch, opens the linked pull request, and records logs, diffs, and usage on the task.