Chatgpt Routing

# ChatGPT Routing And IO

## Terminology Basis

- [Projects in ChatGPT](https://help.openai.com/en/articles/10169521-using-projects-in-chatgpt)
  documents Projects across free and paid plan types; use `project` for durable
  project context rather than inventing another product surface.
- [ChatGPT Enterprise workspaces](https://help.openai.com/en/articles/8265430-what-is-a-workspace-how-can-i-switch-workspaces)
  documents account environments with separate conversations and files. Verify
  and record workspace identity independently from Project identity.
- [ChatGPT desktop built-in browser](https://help.openai.com/en/articles/20001277-using-the-built-in-browser-in-the-chatgpt-desktop-app), [cloud browser](https://help.openai.com/en/articles/20001280-using-cloud-browser-in-chatgpt), and [ChatGPT agent](https://help.openai.com/en/articles/11752874-chatgpt-agent/) document distinct reviewer browser surfaces. Treat their browser state and limits separately.

## Authorization Before Routing

Do not resolve or open a browser route for requests that only say prepare,
build, draft, package, or create review material. Generate
`<repo-root>/review-package.md` and stop. Continue below only when the user
explicitly authorizes an external send, use of ChatGPT now, or a bounded number
of external review rounds.

## Routing Order

1. Explicit user surface or URL and any browser mode explicitly selected in the current request.
2. Session, repository, or user `chatgpt_default_url` through the desktop built-in browser.
3. A standard chat through the desktop built-in browser at `https://chatgpt.com/`.
4. Current Chrome or standalone Playwright only when explicitly selected in the current request and controllable.
5. Package-only when the built-in route cannot be proven and no explicit user-browser override exists.

If generic ChatGPT is used, report that the review is not project-bound.

## Surface Resolution

- Resolve `project` for repository-bound, persistent, or multi-round review when a verified Project URL exists.
- Resolve `standard-chat` for one-off review or when no durable Project route exists.
- Resolve `codex` only as the executor or as an explicitly requested separate-agent review. Never count self-review as an independent ChatGPT pass.
- Treat UI labels as presentation details. Route by verified capability and URL so a label change does not silently change behavior.
- Verify and record the active account workspace independently. A Project is
  available across plan types, and its URL does not establish personal or
  organization workspace membership.

## Default Configuration

Default new review records to `desktop-built-in-browser`. Legacy
`capability-auto` means built-in-first and must not silently select Current
Chrome or standalone Playwright. Availability is not proof of authorization.

Runtime defaults may come from a durable local config file: