Problem
When the same ChatGPT account is used on two PCs for the same Codex workspace, each PC needs its own reachable endpoint. ChatGPT rejects creating the second connector when the default connector name is reused (connection server name already exists). Deleting the existing connector would disconnect the first PC.
The current workflow appears to assume one connector per workspace and preserves one connector name. That works for one active PC, but it does not support two PCs concurrently.
Reproduction
- Set up
codex-with-chatgpt for the same workspace on PC1 and create the default connector.
- Set up the same workspace on PC2 with the same ChatGPT account.
- The second setup produces the same/default connector title.
- ChatGPT refuses the second connector because the name already exists.
Proposed solution
Add an optional per-machine connector name, for example:
Codex with ChatGPT · PC1
Codex with ChatGPT · PC2
The selected name should be persisted locally and reused by doctor/reconnect flows. The setup CLI and Skill should accept or generate a stable device-specific suffix, while preserving the existing single-PC behavior for backward compatibility.
A second option would be documenting an officially supported shared always-on endpoint, but separate connector names seem more suitable for two independent PCs.
Environment
- Windows 11
- Node.js 24
- codex-with-chatgpt 0.1.1 / main
- Same ChatGPT account on both PCs
Problem
When the same ChatGPT account is used on two PCs for the same Codex workspace, each PC needs its own reachable endpoint. ChatGPT rejects creating the second connector when the default connector name is reused (
connection server name already exists). Deleting the existing connector would disconnect the first PC.The current workflow appears to assume one connector per workspace and preserves one connector name. That works for one active PC, but it does not support two PCs concurrently.
Reproduction
codex-with-chatgptfor the same workspace on PC1 and create the default connector.Proposed solution
Add an optional per-machine connector name, for example:
Codex with ChatGPT · PC1Codex with ChatGPT · PC2The selected name should be persisted locally and reused by doctor/reconnect flows. The setup CLI and Skill should accept or generate a stable device-specific suffix, while preserving the existing single-PC behavior for backward compatibility.
A second option would be documenting an officially supported shared always-on endpoint, but separate connector names seem more suitable for two independent PCs.
Environment