TUI sessions tagged vscode

“A thread created by the terminal TUI should have an appropriate source such as cli.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/11891/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports in the last two weeks, down from 1 a week at the late-September peak.

TUI sessions via shared daemon recorded as vscode source. Threads created by the shared app-server daemon store source: "vscode" while originator is "codex-tui", instead of cli.

Is this your bug?

File my report

Where: session metadata
Versions: 0.157.1 to 0.162.1
Platforms: Linux, macOS
How bad: Breaks a normal workflow. Some reports say it used to work.

Original reports3, newest first

Oct 12, 2026CLI 0.162.1: daemon-backed TUI session records source as vscodeOn GitHub#53503
Oct 3, 2026Terminal-originated sessions tagged vscode in 0.160.0; recent saved conversation absent from /resumeOn GitHub#50740
Sep 26, 20260.157: TUI sessions created through the shared app-server daemon are recorded as source: vscode instead of cliOn GitHub#48400

TUI sessions tagged vscode

Is this your bug? What gets counted gets fixed. Pile on.

Is this your bug?

Original reports3, newest first

Do you work on Codex?