| name | repo-harness-chatgpt-browser |
| description | Use when the user wants Codex to consult their logged-in ChatGPT Web session through repo-harness browser engine for planning, architecture review, PRD critique, or Codex goal generation. |
repo-harness ChatGPT Browser
Use this skill when the user asks to consult ChatGPT Web, GPT Pro, browser GPT, or a logged-in ChatGPT account through repo-harness.
Rules
- This uses the user's logged-in ChatGPT Web browser session, not the OpenAI API.
- Do not ask for or handle passwords, SSO secrets, 2FA codes, cookies, browser storage, or tokens.
- Before a non-dry-run consult, state that it may create or continue a real ChatGPT Web conversation.
- Prefer dry-run first when files are involved:
repo-harness chatgpt browser-consult --repo . --dry-run --prompt "<prompt>" --file <path>
- For Oracle provider readiness, run:
repo-harness chatgpt browser-doctor --repo . --provider oracle --json
- Oracle's published CLI requires
node >=24, but that requirement belongs to the resolved Oracle binary. Do not raise repo-harness' overall runtime floor or add Oracle as an implicit dependency just for a GPT Pro consult. If the Oracle doctor reports nodeCompatible:false, fix the Oracle install/runtime and rerun doctor.
- If the Oracle doctor JSON includes
agent_actions such as chatgpt-oracle-install-pinned, chatgpt-oracle-upgrade-pinned, or chatgpt-oracle-fix-configured-source, run them only when the user has explicitly asked to set up or repair GPT Pro browser consults. Do not run Oracle bootstrap from default repo-harness install or unrelated setup checks.
- If the user wants Oracle to use an existing signed-in Chrome profile, record the selected profile metadata first:
repo-harness chatgpt browser-setup --repo . --profile-dir <user-selected-chrome-profile-dir> --browser-channel chrome
repo-harness chatgpt browser-doctor --repo . --provider oracle --json
The Oracle path must fail closed rather than silently falling back to an unbound/default browser session. Do not route through the removed Chrome extension provider or browser-bind.
9. Use browser consult for planning, review, critique, and goal generation. Do not use it as the executor for code edits.
10. Save useful results into repo-harness artifacts with repo-relative, timestamped --write-output paths such as:
.ai/harness/handoff/chatgpt-review-<timestamp>.md
.ai/harness/handoff/codex-goal-<timestamp>.md
plans/prds/*.prd.md
plans/sprints/*.sprint.md
- If login, captcha, workspace picker, or SSO is required, stop and ask the user to complete it in the browser.
- Do not enable remote CDP unless the user explicitly asked for remote browser control and the security boundary is documented.
- For MCP usage, require the server to be started with:
repo-harness mcp serve --repo . --enable-chatgpt-browser
- Do not rely on provider stdout
Artifact: / Output: paths being imported. Browser engine session records save prompt, transcript, output, metadata, and trusted provider IDs; ordinary stdout paths are ignored.
- The native provider uses the current ChatGPT Web model selection. Do not pass
--model or --thinking with --provider native; use Oracle when model selection is required.
Common Commands
Dry-run consult:
repo-harness chatgpt browser-consult \
--repo . \
--dry-run \
--prompt "Review this sprint and return execution risks." \
--file plans/sprints/example.sprint.md
Oracle provider consult:
stamp="$(date -u +%Y%m%dT%H%M%SZ)"
repo-harness chatgpt browser-consult \
--repo . \
--provider oracle \
--prompt "Review this PRD and return risks plus a smallest next step." \
--file plans/prds/example.prd.md \
--write-output ".ai/harness/handoff/chatgpt-review-${stamp}.md"
Native diagnostics for a non-default automation profile:
repo-harness chatgpt browser-setup --repo . --profile-dir <non-default-automation-user-data-dir> --browser-channel chrome
repo-harness chatgpt browser-doctor --repo . --provider native --validate-session
Use native only when the user is ready for a visible ChatGPT Web diagnostic run. If login is required, have the user complete it in the selected non-default browser profile; do not request or handle credentials.
Read the result:
repo-harness chatgpt browser-list --repo .
repo-harness chatgpt browser-session --repo . <sessionId>
repo-harness chatgpt browser-open --repo . <sessionId>
Continue from a saved session:
repo-harness chatgpt browser-followup \
--repo . \
--session <sessionId> \
--prompt "Challenge the previous result and return the smallest next step."
Plan cleanup before deleting local session records:
repo-harness chatgpt browser-cleanup --repo . --status dry_run --limit 20
