In VS Code, make sure Codex chat sessions set the right timing info and status
Open 💬 1 comment Opened Mar 14, 2026 by mjbvz
What version of the IDE extension are you using?
26.5311.21342
What subscription do you have?
Copilot
Which IDE are you using?
VS Code
What platform is your computer?
_No response_
What issue are you seeing?
We're seeing Codex sessions with incorrect statues VS Code's built-in sessions UI, for example always showing as Completed even when a session is in progress. See https://github.com/microsoft/vscode/issues/281151 for example
What steps can reproduce the bug?
- Start long codex session in VS Code
- While it is still running, switch to the VS Code sessions view
- Press refresh if the session is not showing
🐛 The session is listed as completed instead of being in progress
What is the expected behavior?
_No response_
Additional information
It looks like only startTime is being sent over right now on the session. This should be fixed if you add:
- The other timing fields: https://github.com/microsoft/vscode/blob/6b8b037682d81d6e9a95be9d79b0fda6591e3ed2/src/vscode-dts/vscode.proposed.chatSessionsProvider.d.ts#L258
- Or explicitly set the status on the item: https://github.com/microsoft/vscode/blob/6b8b037682d81d6e9a95be9d79b0fda6591e3ed2/src/vscode-dts/vscode.proposed.chatSessionsProvider.d.ts#L239
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗