Microsoft Edge and Google Chrome extension

Chat Bridge support

Use this page to install the required local companion, verify the 8/8 tool boundary, understand confirmation controls, and prepare a safe support report.

The browser Store installs only the extension. PLwC Windows Setup must separately install the Gateway, loopback Bridge, and Native Launcher. Adding the extension never installs or silently enables the native application.

1. Before you start

Use a supported Windows 11 system and a current Microsoft Edge or Google Chrome browser.
Install PLwC through the official Windows Setup path linked from the PLwC website or Store listing.
Include the optional Chat Bridge component during Setup.
Add/Get the extension through the browser's own confirmation flow.
Sign in to ChatGPT through the normal ChatGPT page. PLwC does not request or store your ChatGPT credentials.

Open PLwC website Read the security overview View source and documentation

2. Verify the local connection

Open https://chatgpt.com/.
Choose the PLwC icon beside the composer or at the right edge.
Open the Status tab and choose Reconnect if the Bridge is offline.
Confirm that the endpoint is ws://127.0.0.1:3007/message, the build identity is valid, and tool validation reports exactly 8/8.

If the panel reports that the Native Launcher is unavailable, rerun PLwC Windows Setup and choose Repair with the Chat Bridge component selected. Reinstalling the browser extension alone cannot repair native registration.

3. Start a Bridge conversation

Open the Primer tab.
Choose Generate, review the generated primer, and choose Insert Bridge Primer.
Submit the visible primer in ChatGPT.
Describe the task in ordinary language. The AI should use the explicit plwc_tool_call wrapper and consult plwc_describe rather than guessing an uncertain operation.

4. Confirmation and safety

Read-only calls may run automatically after the visible delay. Recognized writes and sandbox calls require individual confirmation by default. Their automation options are separate, off by default, and carry red warnings. Unknown operations always remain manual.

Review the operation name, arguments, target path, and confirmation warning before choosing Run. PLwC has no public delete operation. Workspace deletion requests use the governed Trashcan path where supported, and the extension does not automatically clean temporary workspace data.

5. Results and recovery

Result cards distinguish policy denial, validation failure, missing data, unavailable services, gateway failure, and transport failure. Artifact results show origin and validation state. Large results use complete, ordered chunks with hashes rather than silently dropping content.

If ChatGPT does not accept automatic insertion, use Insert Result or Copy Complete Result and paste the text manually. The extension writes to the clipboard only after the Copy action and never reads clipboard data.

6. Troubleshooting checklist

No PLwC icon: confirm the extension is enabled and the active URL is chatgpt.com or chat.openai.com, then reload the page.
Bridge offline: choose Reconnect. If the native host is missing, use PLwC Setup Repair.
Not 8/8 tools: stop and repair/update PLwC. The extension intentionally blocks execution when the local contract or build identity differs.
Call awaits confirmation: review the call, select its confirmation control, and choose Run. Unknown calls cannot be automated.
Composer contains a draft: automatic result return pauses to protect your text. Clear or send your draft, then use Insert Result.
Old calls appear in a reopened chat: reload once. Existing content should become the quiet baseline and must not execute as new work.

7. Request support safely

For reproducible defects, open a GitHub issue. For a report that cannot be public, email info@plwc.de.

Include the browser name/version, Windows version, extension version name, PLwC build ID, the visible error class, and minimal reproduction steps. Replace real profile names, usernames, conversation IDs, and local paths with synthetic values.

Never send: passwords, session cookies, API keys, publisher tokens, recovery codes, payment data, identity documents, private ChatGPT conversations, or confidential workspace files. Support will not ask for these items.

8. Privacy

Read the PLwC Chat Bridge privacy policy for the complete permission, data-use, local-storage, retention, and Limited Use disclosure.

The PLwC security overview describes the broader local Gateway and workspace security model; it does not replace the extension-specific privacy policy.