Browser Companion is the external-browser compatibility surface for supported provider conversations. It relays bounded GDP text, prepares context and GDP Branch handoffs, and keeps repository execution authority in GDP Desktop.
Connect the visible provider conversation
The current Companion connects GDP Desktop to visible ChatGPT, Gemini, and Claude conversations through a loopback relay. The relay host stays on 127.0.0.1, and the extension and Desktop must agree on the configured port and authentication value.
Use Copy or Fill when you want to review relay text before it reaches the composer.
Enable auto-fill only when you want GDP text appended to the visible supported-provider composer.
Keep diagnostics and large command output in GDP evidence rather than expanding every browser relay message.
Continue long work with GDP Branch
GDP Branch opens a targeted fresh conversation and prepares a compact continuation seed plus a redacted Full Context Markdown archive. The destination is not considered ready until the expected handoff artifacts are available.
The public-package contract keeps final provider Send manual. A separately loaded local development profile may use trusted GDP Send only behind its explicit opt-in gates; GDP Branch also requires the source tab’s Auto-complete choice before that local automated path can submit.
Know what the Companion cannot authorize
Browser visibility and relay state do not grant repository mutation or fleet-scheduling authority. The Companion works with visible conversation state and bounded GDP metadata; it is not a source of hidden model reasoning.
It cannot apply patches or run terminal commands.
It cannot commit, push, reset, clean, or roll back a repository.
Neither public nor local profiles bypass provider login, CAPTCHA, or protective controls.
Store publication and local source readiness are separate release facts. Do not infer public availability merely from the presence of the extension source or release candidate.
