ProPR and direct agent sessions: a reviewable result

Use Claude Code, Codex, Antigravity CLI, Mistral Vibe, or OpenCode directly for live exploration. Use ProPR when the work needs a plan, isolated execution, a visible pull request, and GitHub-driven follow-up.

Direct agents

Use both paths

Keep using agents directly for exploration, then use ProPR when the change becomes a pull request with a clean review trail.

Direct agent pathTerminal or IDE → approve each edit → commit when you decidePackaging the session into a pull request is still your job.

ProPR pathPlan → isolated workspace → GitHub PR → follow-up commitScope the task, walk away, review the pull request.

A direct agent session starts where you already are: a terminal, editor, or local checkout. Use it for debugging, quick refactors, experiments, and learning an unfamiliar part of the codebase.

A direct session asks you to approve commands and edits as it goes. ProPR runs the same agents unattended in an isolated workspace and moves your approval to the pull request. Scope the task, walk away, review the PR. Paste screenshots into a GitHub comment for the next follow-up.

Some direct sessions already open pull requests. ProPR adds what they leave out: a reviewed plan, isolation per task, shared logs, a choice of agent per task, and follow-up commits from GitHub comments.

New task dialog: repository, prompt, agent and model, then Run task or Plan first — A task starts with the repository, the prompt, and the agent and model for this run, then Run task or Plan first.

Use agents directly when you are still thinking.

A terminal or IDE gives you the fastest conversation with the codebase.

Investigating a bug before you know the shape of the fix.
Trying a small local edit that may be thrown away.
Asking a model to explain code while you keep control of the checkout.

Use ProPR when the result needs a path to review.

Once the change has a destination, the plan, branch, and PR come from one flow the whole team sees. A fair cost comparison counts the packaging work a private session leaves behind.

A change needs a plan, task, branch, commits, and PR.
PR participants request fixes from GitHub comments.
Agent comparisons and handoffs keep their history.

Private agent session versus shared PR path.

Question	Direct agent	ProPR
Fast local exploration	Yes	No, unattended runs
Plan, branch, and PR in one product flow	You ask for each step in the session	Yes
PR comments become follow-up commits	Through the vendor's GitHub Action, such as Claude Code's `@claude` or OpenCode's `/opencode`	Yes
Switch agents between phases	Start a new session in the other tool	Yes

Claude Code CLI

Compare a direct Claude Code session with running the same CLI through ProPR's shared delivery system.

Codex CLI

Compare a direct Codex session with running Codex unattended through ProPR's pull request path.

Claude Code, Codex, Antigravity CLI, Mistral Vibe, and OpenCode inside ProPR

Use the same agents under a shared plan-to-PR loop. ProPR packages each session into a pull request automatically.

OpenCode

Use OpenCode locally for quick edits, or run it through ProPR to automatically package its output as a PR.

Aider

Keep Aider for fast local terminal coding, then use ProPR when the output needs a review path your team can inspect.

Verified November 2026: Claude Code GitHub Actions, OpenCode GitHub Action.