Starting in ChatGPT
Keep your ChatGPT conversation open. Use this guide to check your computer and GWC account, then return to that conversation to connect GWC Bridge and try your first read.
1. Check your accountUse ChatGPT to connect remotely to your GWC Studio or GWC for VS Code.
Start in ChatGPT or on the GWC website, then follow the same checks. This guide does not mark steps complete or change your access settings.
Choose ChatGPT, Claude, Gemini, Grok or Muse. The official ChatGPT and Claude listings are still in review. Before you approve, review all shared folders and permissions. Start with a read-only check. Start
Connecting GWC Bridge authorizes the AI app to reach your GWC account. There are no folder, computer or tool-permission checkboxes at sign-in. Set shared folders, command access and computer safeguards in GWC Studio or GWC for VS Code; set tool approvals in ChatGPT or Claude. After connecting, confirm access with one harmless file read.
Keep your ChatGPT conversation open. Use this guide to check your computer and GWC account, then return to that conversation to connect GWC Bridge and try your first read.
1. Check your accountGWC for Web and GWC Connect show GWC Cloud sync and linked-computer status, including online/offline, registration, last seen and host activity. Computer cards can be expanded for details, and inactive computers can be removed. These pages are for monitoring and removal, not changing Bridge access.
1. Check your accountUse the same GWC sign-in on the website, in GWC Studio or GWC for VS Code and for this ChatGPT connection. In GWC for Web, use Personal for Bridge. In GWC Connect, switch to Personal only if Bridge asks. If you are already in Personal, no switch is needed. Personal refers only to your GWC account context. An active Connect Pass is required.
Use a supported release of GWC Studio or GWC for VS Code and keep the desktop app open. Choose the exact computer registration; matching names can belong to different registrations. Check desktop availability for current releases and supported platforms.
On a phone? Copy this public guide link and open it on your computer to finish setup. You do not need GWC Connect. The link keeps the guide language but carries no account, computer, folder or sign-in details. Repeat the live checks after continuing.
Check the computer's All folders or Selected folders policy, enabled tool capabilities and required local approvals in GWC Studio or GWC for VS Code. Folder and command restrictions are not chosen when signing into ChatGPT.
Return to ChatGPT and connect GWC Bridge using the same GWC sign-in. There is no per-connection folder or permission checklist. Choose the intended registered computer and a permitted folder when using the tools. An offline PC remains unavailable even with a saved connection. Confirm one harmless read before relying on access.
Choose the intended computer and folder, then a non-sensitive text file inside that folder. Ask ChatGPT to read a small, identifiable part. Confirm success only when that connection returns the file content. This setup check needs no file changes, commands or agent tasks.
Check again after changing the account, ChatGPT connection, computer, folder access or permissions. An earlier successful read does not prove current access, especially while the computer is offline.
GWC Bridge lets ChatGPT request files, documents, searches and commands from your computer. The computer's folder policy, capability switches and protected-action checks control what can run locally; ChatGPT controls its own tool approvals. Connection sign-in does not select folders or tool capabilities.
Installing GWC Studio or GWC for VS Code is not the same as authorizing ChatGPT. Check the exact registered computer and configure its shared folders and local protections there. Connecting the ChatGPT app authorizes the account but does not ask you to choose folders or tick tool permissions.
If a PC or folder is unavailable, open GWC Studio or GWC for VS Code on the intended computer, check its Bridge switch and folder policy, and verify the same GWC account. Refresh the reported computer status; do not look for extra choices on the sign-in page.
GWC for Web and GWC Connect show GWC Cloud sync and linked-computer status, including online/offline, registration, last seen and host activity. Computer cards can be expanded for details, and inactive computers can be removed. These pages are for monitoring and removal, not changing Bridge access.
Register a new computer and control Bridge On/Off on that computer in GWC Studio or GWC for VS Code. Some current desktop builds only show ChatGPT/Claude access as status, not independent On/Off switches. If separate controls are unavailable, review or revoke each app's OAuth grant under Settings → Connected apps. Check the desktop's actual state before relying on a change; switching off does not guarantee that work already running stops, and switching on cannot wake an offline computer.
In GWC for Web or GWC Connect, use Remove computer for an inactive computer registration and review its confirmation. Removing it blocks new Bridge access but does not delete files, stop work already running or revoke a separate ChatGPT or Claude connected-app grant. Revoke that grant separately under Settings → Connected apps.
Folders: In GWC Studio or GWC for VS Code, review the computer's All folders or Selected folders policy and any enabled capabilities. New supported installations use All folders unless you restrict them; older versions use Share folder. This computer policy governs Bridge use after the AI app connects.
Set when ChatGPT asks before using tools in ChatGPT's own Permissions: Always ask, Allow read-only tools, Allow low-risk tools or Allow all tools, where offered. Claude has its own connector and tool permissions. These belong to the AI clients, not GWC Bridge; GWC has no working four-level tool-approval selector or shared approval cards. Older desktop builds may still display a read-only legacy level.
The computer's Bridge switch, shared-folder policy, enabled capabilities and independent protected-file and process checks limit local access. OAuth scopes identify the connector; they are not extra folder or tool choices at sign-in. AI-app tool approvals remain in ChatGPT or Claude. Commands and agent tasks run with the operating-system user's rights and may affect data outside shared folders; AI-client approvals do not sandbox them.
These groups describe the available Bridge tool families. Use depends on the computer's current local restrictions and ChatGPT's own tool approvals; there is no scope or folder checklist during sign-in.
ChatGPT uses Bridge tools directly for files, documents and commands. Starting an agent task is optional and uses your own Taichu model setup.
Find your PCs and shared folders, check connection status and account information, and disconnect a PC from Bridge when authorized. Reconnect using the owner controls in GWC for Web, GWC Connect or on the PC, not a ChatGPT tool.
List files, check file information and read one or several files. With change permission, create folders, write or edit files, copy, move or delete them, and restore items that the file tool can restore.
Read and write documents in the formats supported by the PC, including PDF output when available. Document access follows the connection’s folder and change permissions.
Search shared files. Start a search session, retrieve its results, list searches and stop a search.
Run a command or start an interactive program. List its sessions, read output, send input and stop a session. Commands and programs run on your PC, not inside ChatGPT.
List system processes and end a selected process when system-process access is enabled. The PC’s process-identity protection still applies.
Start, check and cancel agent tasks using your own Taichu setup. Tasks can change files and may use your configured provider account or local models. Any provider charges are handled by your provider.
Read safe PC settings, recent activity and usage. When authorized, change the PC’s display name or keep its activity log for longer. Settings tools cannot turn off protections or shorten the log.
Read prompt suggestions and send a message you write to GWC. Feedback does not attach files, process output or diagnostics.
Set when ChatGPT asks before using tools in ChatGPT's own Permissions: Always ask, Allow read-only tools, Allow low-risk tools or Allow all tools, where offered. Claude has its own connector and tool permissions. These belong to the AI clients, not GWC Bridge; GWC has no working four-level tool-approval selector or shared approval cards. Older desktop builds may still display a read-only legacy level.
The computer's Bridge switch, shared-folder policy, enabled capabilities and independent protected-file and process checks limit local access. OAuth scopes identify the connector; they are not extra folder or tool choices at sign-in. AI-app tool approvals remain in ChatGPT or Claude. Commands and agent tasks run with the operating-system user's rights and may affect data outside shared folders; AI-client approvals do not sandbox them.
Disconnect is a connection control, not a general stop or undo for work already started. Use the appropriate process or agent task control to request cancellation.
Shared-folder metadata uses identifiers and labels rather than the plaintext absolute folder path. Requested file contents, command output and system-process results may themselves contain absolute paths or other personal information.
For a tool request, GWC relays the inputs and results needed for that tool. Depending on the tool, this can include folder labels, relative paths, requested file or document content, search terms and results, proposed changes, command or task instructions, process information and output. See the Privacy Policy for storage, retention and international-transfer details.
Successful read-only tools create no per-call PC activity entry and do not update the connection's last-used timestamp. GWC keeps separate connection and operational information needed to authenticate, deliver and revoke the service, as described in the Privacy Policy.
The PC activity log records GWC Bridge state-changing and elevated actions while it is on. You control it on the PC; while it is off, those actions still run within your capabilities and confirmations but are not recorded. It records targets, approval decisions and outcomes, never returned file/document contents, command/process output or Taichu answers. Retention defaults to 30 days; GWC Bridge can lengthen it but cannot shorten it or turn the log on or off.
Requested tool inputs and results are sent to ChatGPT/OpenAI, which handles them under its own terms and privacy policy. GWC Bridge does not claim that revocation can recall information already delivered.
| Problem | What to do |
|---|---|
| PC offline | Wake the intended PC, open GWC Studio or GWC for VS Code and check the correct GWC sign-in. If Bridge was disconnected, the owner reconnects through supported controls on that PC or in GWC for Web or Mobile. Wait for the PC-reported state, then repeat the selected-file read; saved entries alone do not confirm access. |
| Folder not listed | On the intended PC, check All folders or Selected folders and verify the requested file is shared. Use Share folder on older builds. The connected app has no separate Add folders approval step; do not look for folder checkboxes on GWC sign-in. Keep other local restrictions unchanged. |
| Connect Pass needed | If Bridge returns CONNECT_PASS_REQUIRED, stop that action and resolve the Connect Pass requirement for the connected account. Keep the existing connection and consent; re-check access before retrying. This error alone does not mean you need to switch accounts, sign in again or restart consent. Follow separate instructions if the connection is expired or the account does not match. |
| ChatGPT keeps asking | If access fails, check GWC Cloud sync, the computer's online status and the signed-in account. On the computer check Bridge On/Off, shared folders, enabled capabilities and protected-action prompts; in the AI app check its tool permissions. You can revoke the app connection in Settings → Connected apps, but reconnecting does not offer additional folder or permission choices. |
| Scope or capability missing | If access fails, check GWC Cloud sync, the computer's online status and the signed-in account. On the computer check Bridge On/Off, shared folders, enabled capabilities and protected-action prompts; in the AI app check its tool permissions. You can revoke the app connection in Settings → Connected apps, but reconnecting does not offer additional folder or permission choices. |
| Protected file or process refused | Do not try to bypass secret or process-identity protections. Review any protected-action prompt on the PC; blocked access remains blocked. |
| Update required | Update needed: update the supported GWC Studio or GWC for VS Code release on the intended computer, then reopen the desktop app or refresh. Check the actual folder controls; a version number alone does not prove folder-policy support. If unavailable, use the older Share folder flow. Check desktop availability for current releases and supported platforms. |
| PC relay disconnected | If access fails, check GWC Cloud sync, the computer's online status and the signed-in account. On the computer check Bridge On/Off, shared folders, enabled capabilities and protected-action prompts; in the AI app check its tool permissions. You can revoke the app connection in Settings → Connected apps, but reconnecting does not offer additional folder or permission choices. |
| Command, process or agent task did not run | Use a process-session control for a command session and an agent task control for an agent task. Disconnect is not a general cancellation or undo. |