[Bug]: ProviderAdapterProcessError: Provider adapter process error (codex) for thread ...: session ... is archived. Run `codex unarchive ...` to unarchive it first.
Open
Nobody has claimed this yet.
accepted
bug
via-triage
- 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 a chat with Codex in T3 Code.
- Archive it in ChatGPT.
- Send a new message in the same chat in T3 Code. The error appears.
Expected behavior
The thread should resume normally and accept the new message.
Actual behavior
this error toast appears
Impact
Minor bug or occasional failure
Version or commit
No response
Environment
No response
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
Reproduce the issue by starting a Codex chat, archiving it in ChatGPT, and sending another message from T3 Code. Trace the provider adapter process error from that reproduction; done means an archived thread resumes normally instead of showing the error toast.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100