ancienttwo/repo-harness/repo-harness-chatgpt

repo-harness-chatgpt

Bot entrypoint. Select the explicitly requested integration mode. Assign only its technical reference to the worker. Require explicit setup; ChatGPT is never implied by either install profile.

Mode Selection

• First-time Oracle browser or MCP Connector configuration -> references/setup.md.
• Explicit GPT Pro orchestration -> read the setup lane in

references/setup.md, then references/orchestrate.md.

• Start a new local -> ChatGPT Web browser consult -> references/consult.md.
• Continue, read, or clean up a saved browser session -> references/continue.md.
• Verify or accept a ChatGPT MCP tool call as real evidence -> references/read-back.md.
• Operate the MCP Connector bridge (planner/executor/orchestrator/coding) -> references/bridge.md.
• Delegate a self-contained task to GPT Pro and independently accept the result -> references/delegate.md.

Boundaries

• Product planning never implies this package; ChatGPT discovery requires explicit setup.
• Never request or handle ChatGPT passwords, 2FA codes, cookies, browser storage, or session tokens; login/captcha/SSO stop and hand back to the user.
• Setup, consult, and bridge modes share these safety rules by reference; none shares secrets, auth state, or tokens with another mode.
• Consult stays planning/review/critique only, never the code-edit executor; delegate is the sole approved path for code deliverables, and GPT Pro still never executes edits.
• Orchestrate is explicit opt-in advisory planning/review; GPT Pro never owns

task, lease, writes, shell, or acceptance authority.

• A missing or unreadable canonical reference fails the calling command closed; it never synthesizes replacement prose.
• Do not enable remote CDP unless the user explicitly asks and the boundary is documented.