Migration drops subagent history

“A background legacy-to-paginated rollout migration appears capable of causing silent loss of persistent task history.”

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/9501/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 and thumbs-up in the last two weeks, down from 3 a week at the mid-September peak.

Paginated rollout migration drops subagent thread history without backup. The legacy_to_paginated_v1 migration rewrote rollouts in place, keeping only inherited context for threads with thread_source subagent.

Is this your bug?

File my report

Where: rollout migration
Versions: 0.154.0
Platforms: Linux, Windows
How bad: Loses work: code or files lost or damaged. Some reports say it used to work.

Related: Thread history missing or unopenable

Not quite your bug?

Threads fail to open3 people

Original reports3, newest first

Oct 9, 2026legacy_to_paginated_v1 dropped the own history of threads marked thread_source=subagent (incl. user-created threads); no backup keptOn GitHub#52411
Sep 19, 2026[Data Loss] Background legacy-to-paginated migration can replace persistent subagent history with bounded resume context without preserving the originalOn GitHub#46713
Sep 14, 2026Persistent app-created tasks lose original transcripts on bounded subagent history migration (source=vscode)On GitHub#45500