Please support Handoff for long-running/paginated Codex chats

What variant of Codex are you using?

Codex desktop app on Windows; cross-host Handoff between two Windows PCs

What feature would you like to see?

I’m replacing my main PC and temporarily working from a backup computer. I have several long-running Codex chats that contain real project work: decisions, debugging history, constraints, and context that would take a lot of time to explain again.

Both Windows PCs are connected through Codex Remote Connections and use the same account and repository. But when I try to move an important older chat, Handoff stops with:

Le chat paginate non possono ancora essere continuate su un altro host.

(English: Paginated chats cannot yet be continued on another host.)

This feels backwards: the chats I most need to preserve are exactly the ones I cannot move.

Please support Handoff for paginated chats, or give us an official lossless export/import option. We should not have to manually reconstruct weeks of work just because we need to replace or repair a computer.

Additional information

Simple reproduction

1. Connect two Windows PCs through Codex Remote Connections.
2. Configure the same repository on both.
3. Open a large, long-running chat with paginated history.
4. Try to hand it off to the other PC.
5. Codex refuses because the chat is paginated.

Expected: continue the same chat on the other PC with its context and Git state intact.

Related: #39968 reports Handoff failing with a large chat; #40416 also discusses pagination and reliable continuation state.

Start by reproducing the refusal with a large paginated chat across the two Windows PCs, then read related issues #39968 and #40416 for existing Handoff and continuation-state context. No files or tests are named; done means continuing the same paginated chat on the other host with its context and Git state intact, or providing a lossless export/import path.