ChatGPT Integration

ChatGPT.com compatibility

Project Constellation treats ChatGPT’s web UI as a changing provider surface, not a stable internal API.

Current verified contracts

Live compatibility was checked against https://chatgpt.com/ on 2026-08-24. Current conversation turns use data-testid="conversation-turn-N" containers with nested data-message-author-role and data-message-id. The composer exposes a visible contenteditable element with role textbox and accessible name Chat with ChatGPT; the similarly named textarea can be hidden. Streaming exposes a visible Stop answering control and/or busy/streaming attributes.

Current agent activity uses legacy generic group/tool-message rows alongside concise step summaries styled with tertiary text classes; the active summary uses loading-shimmer-tertiary. Constellation prefers the active concise summary (for example, an observable “Inspecting…” or “Implementing…” label), deduplicates nested copies, and keeps generic Called tool rows only as bounded step-count evidence.

The selector strategy prefers top-level conversation-turn containers, then falls back to role/message IDs. This prevents duplicate capture from nested current markup. Root-path anonymous conversations receive an in-tab session ID so they are not mistaken for the empty Home screen.

What Constellation observes

• chat links and route changes;
• rendered user/assistant turn containers and structured links/code;
• attachment/download/link evidence;
• visible status, approval, delivery failure, rate-limit, auth, and unavailable surfaces;
• visible agent/tool step summaries, tool-state evidence, and sanitized passive request lifecycle from the service worker;
• a bounded local activity ledger for response DOM changes, page status, tool progress, handoff/recovery, and request start/response/completion.

The content script makes no network calls, does not patch ChatGPT JavaScript, does not remove messages, and does not depend on undocumented ChatGPT backend APIs. It cannot see private chain-of-thought and never pretends otherwise. Request URLs and prompt content are not placed in the HUD ledger; only a sanitized category, lifecycle phase, method/status, and duration are exposed. History/sidebar/session traffic is auxiliary and cannot prove that the model is alive.

The Pulse's Branch & continue control uses only an explicit user click, the normal ChatGPT new-chat route, and the visible native composer. It waits for the usable composer/send control, dispatches native input events, confirms a send from observable composer/route changes, and then links the resulting chat ID to the source checkpoint. It does not call a hidden conversation API, overwrite existing draft text, or claim success from a click alone.

Approval and recovery

Approval Recovery searches accessible dialogs/menus for connected-app approval semantics. Always-allow behavior is disabled until the user explicitly acknowledges its risk. Delivery failures request a controlled browser refresh; Constellation never loops on ChatGPT’s Retry button. Rate-limit signals enter the provider request governor and stop Constellation-originated background work during cooldown.

Maintaining compatibility

When ChatGPT changes:

1. Reproduce on the live site without inspecting cookies, session storage, passwords, or private profile data.
2. Capture accessibility and non-sensitive DOM attribute evidence.
3. Update provider-specific selectors with semantic fallbacks.
4. Add a minimized current-DOM fixture under tests/smoke/.
5. Verify exactly-once turns, composer preservation, status/tool behavior, no content-script fetch, and bounded message counts.
6. Run the complete suite and update the “current verified” date.

tests/smoke/chatgpt_current_dom_smoke.py is the compatibility sentinel for the current markup.