GDP Browser is a GDP-owned Electron and Chromium workstation, not a ChatGPT-only dashboard. It combines normal web pages with dense Pane and Tab workflows while keeping browser identity separate from repository execution authority.
Work in a durable multi-pane browser
The current browser uses a Workspace → Pane → Tab → WebContents model. The default workspace is 4×3, dense layouts extend through 5×4, tabs keep durable host_tab_id identity, and normal remote tabs share a persistent Chromium profile by default.
Navigate ordinary HTTPS sites and loopback development pages from the omnibox.
Move and reorder tabs inside the workspace without redefining their durable browser identity.
Pop a Pane into a native window, reattach it, or use Pane fullscreen without recreating the selected renderer.
Use implemented Find in Page, bounded Downloads Manager, supported Site Permissions, per-tab zoom, and Auto/Desktop/Mobile presentation controls.
Use the AI surfaces without hiding the Send boundary
The trusted-shell AI Command Center can stage one draft across selected ChatGPT and Gemini targets. Write stages text and preserves existing human drafts; Bulk Send is a separate armed operation that revalidates the exact target and staged text immediately before activation.
Opening or refreshing Command Center does not wake every background provider runtime.
Closing or refreshing the panel revokes outstanding bulk-Send authority.
Ambiguous Send outcomes are not blindly replayed.
ChatGPT Conversation Vault provides separate durable conversation and asset evidence; it is not generic browser history.
Separate browser capability from GDP authority
GDP Browser also has a bounded site-agnostic observation and interaction substrate, but remote pages do not receive unrestricted JavaScript, raw CDP, credential extraction, or generic replay-any-request authority. High-impact effects remain governed.
A visible Pane, restored host_tab_id, fresh Browser topology, or Browser-local action does not grant Desktop Task, repository, binding, lease, or provider-native execution authority. Some broader native-autonomy and classic-browser features remain separate work.
