ChatGPT Pro planner

Plan with ChatGPT Pro, execute with Claude or Codex. repo-harness can expose only your workflow artifacts — plans, sprints, contracts, checks — to ChatGPT through a local MCP sidecar, so the planner reads state without touching source.

Start the planner sidecar

repo-harness mcp setup chatgpt --repo .
repo-harness mcp serve --transport http \
  --host 127.0.0.1 --port 8765 --profile planner

Connect the printed /mcp URL as a ChatGPT Connector. The planner profile is read-only over workflow files.

Hand a plan to the executor

repo-harness mcp prepare-goal \
  --prd plans/prds/auth.prd.md \
  --sprint plans/sprints/auth.sprint.md
# › .ai/harness/handoff/codex-goal.md

Safety boundary

The planner profile makes hard guarantees:

• no source writes,
• no arbitrary shell,
• no default runner,
• separate from your API quota.

It is plan-and-review only — Codex or Claude stays the executor.

Full setup

For the complete Connector flow — OAuth, tunnel endpoints, Codex stdio, the opt-in dev runner, and troubleshooting — see MCP Connector. To drive ChatGPT Web through Oracle instead of the API, see the ChatGPT browser engine.