[Bug]: Codex provider fails to initialize with "Invalid payload for method 'initialize' during 'decode-payload'"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 23k
- Forks
- 5.9k
- Avg merge
- 11h 14m
- Merged PRs (30d)
- 357
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
Not sure
Steps to reproduce
- Start t3code on Windows.
- Open the Codex provider / try to connect to Codex.
- Send a prompt or start a new Codex turn.
- The provider fails before the turn starts.
Expected behavior
Codex should initialize correctly and connect/start the provider turn without error.
Actual behavior
Codex fails to connect/start. The UI shows:
ProviderAdapterProcessError: Provider adapter process error (codex) for thread ...:
Invalid payload for method 'initialize' during 'decode-payload'
Also shown:
Codex app-server provider probe failed:
Invalid payload for method 'initialize' during 'decode-payload'.
Provider turn start failed.
Impact
Blocks work completely
Version or commit
No response
Environment
- OS: Windows - App: t3code - Provider: Codex - Version: 0.0.33
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Codex provider connection on Windows with t3code 0.0.33, then trace the provider adapter process and app-server provider probe around the initialize payload. The fix is complete when Codex initializes, connects, and starts a provider turn without the decode-payload error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100