ERROR codex_api::endpoint::responses_websocket: failed to connect to websocket: UTF-8 encoding error: failed to convert header to a str for header name 'x-codex-turn-metadata' with value: "{"session_id":"...","thread_source":"user", "turn_id":"...","workspaces":{"/Users/kamer/Agentlar\xc4\xb1m":{...}}, "sandbox":"seatbelt"}" url: wss://chatgpt.com/backend-api/codex/responses

TL;DR

The issue can be mitigated by percent-encoding the workspace path values in the x-codex-turn-metadata header or using a separate header that supports UTF-8.

Guidance

• Verify the issue by checking if the workspace path contains non-ASCII Unicode characters and if the x-codex-turn-metadata header is being set correctly.
• Use the provided workaround by running Codex outside the affected workspace with cd /tmp && codex exec --skip-git-repo-check to avoid triggering git workspace discovery.
• Consider using a separate header that supports UTF-8, such as x-codex-turn-metadata-b64 with base64-encoded JSON, to avoid encoding issues.
• Test the fix by creating a workspace with non-ASCII characters and verifying that the WebSocket connection is established successfully.

Example

No code snippet is provided as the issue is related to the Codex CLI and its interaction with the WebSocket connection.

Notes

The issue affects all users with non-ASCII characters in workspace paths, which is common in non-English locales. The workaround provided avoids the issue but may not be a permanent solution. A proper fix would require changes to the x-codex-turn-metadata header serialization code.

Recommendation

Apply the workaround by running Codex outside the affected workspace until a patched version is available, as it provides a temporary solution to the issue.