GDP does not expose arbitrary folders from your computer. A repository becomes an AI target only when it is intentionally open in GDP Desktop and visible through the current GDP connection. Refresh the exact target identity instead of guessing a path or reusing a stale repo_id.
Check GDP Desktop and the gateway first
Confirm GDP Desktop is running on the computer that owns the repository.
Open Settings > MCP Bridge and confirm the remote gateway is connected.
If the gateway is disconnected, reconnect it before diagnosing repository targeting.
If ChatGPT shows an old GDP tool surface after a connector or approval-mode change, reconnect the ChatGPT GDP connector before re-authorizing it.
A connector that exists in ChatGPT and a repository that is exposed by the current GDP Desktop session are separate facts.
Make sure the repository is actually open in GDP
GDP’s AI-facing repository tools are intentionally limited to repositories already open as GDP Desktop tabs. They are not a general filesystem browser and do not accept an arbitrary local path as a replacement target.
Open the intended Git repository in GDP Desktop, then ask the connected AI client to list repositories again.
Seeing the folder in another editor does not automatically expose it to GDP.
Opening the repository in GDP is the deliberate local boundary that makes it eligible for repository tools.
Do not paste a random absolute path into the AI and expect GDP to retarget itself.
Refresh repository targets instead of reusing a stale repo_id
repo_id is a stable identity for one open GDP tab during the current GDP app session. tab_index is only the current visual order. Closing a repository invalidates that target, and restarting GDP creates a fresh set of repo_id values for the tabs that are restored or opened.
If the repository was closed, GDP restarted, or the target is otherwise uncertain, call list_repos again and select the current repo_id. GDP should reject an unknown or closed repo_id rather than silently redirecting it to another repository.
Never invent a repo_id from an old conversation or screenshot. Use the current value returned by GDP.
Separate connector visibility from device or workspace selection
The ChatGPT GDP connector is account-level, while local repositories live on specific GDP Desktop nodes. If you use more than one computer and multi-device routing controls are available, confirm that the intended Desktop and workspace are selected before treating a missing repository as a repository bug.
If GDP tools themselves are missing or stale, repair the connector or gateway path first. If the tools are present but the repository is absent from the fresh repository list, return to GDP Desktop and verify that exact repository is open there.
Connection problem: GDP tools or the current Desktop gateway are unavailable.
Target-exposure problem: GDP is reachable, but the intended repository is not one of the currently open GDP tabs.
Stale-identity problem: the repository is open, but the AI is still using an old or closed repo_id.
Multi-device selection problem: the account is connected, but the intended Desktop or workspace is not the selected execution target when those controls are enabled.
