copilot --resume without an ID drops into a new empty session; the Sessions list is auto-replaced after ~2s and the trust prompt takes the first Enter #5228

Describe the bug

Since the unified Sessions browser became the default, copilot --resume without a session ID no longer lets me pick a session. Each launch creates a new empty session ("Session 1"). The Sessions list is shown for only ~2 seconds, then the UI switches to that new session's "Current" tab. In a folder that is not remembered as trusted, the "Confirm folder trust" dialog then appears on top of the empty session and consumes my first Enter, so I end up in a blank new session before I can use ↑/↓ on the list.

The list is still reachable with Tab or /resume, but this is not obvious, and it makes --resume look like it simply creates a new session.

Affected version

GitHub Copilot CLI 1.0.102

Steps to reproduce the behavior

1. cd into a local folder that has earlier Copilot sessions and is not remembered as trusted.
2. Run copilot --resume (no session ID).
3. After a "Resuming session…" spinner, the Sessions tab appears. The highlighted first row is a brand-new empty "Session 1".
4. About 2 seconds later the UI switches to the "[Current]" tab and shows "Confirm folder trust".
5. Press Enter ("1. Yes").
6. Result: I am in the new empty session. ↑/↓ does nothing here. Pressing Tab (footer: "tab next tab") or typing /resume brings back the Sessions list, where ↑/↓ works.

Expected behavior

copilot --resume without an ID should keep the session list focused until I choose a session or cancel. It should not auto-switch to the newly created placeholder session, and the folder-trust prompt should not take focus or Enter from the picker. Alternatively, it should reopen the most recent session for the current repository, as the 1.0.64 changelog describes for --continue/--resume.

Additional context

• macOS 26.7.1 (25G241), x86_64; Terminal.app 470.2; zsh; installed via Homebrew cask, auto-updated to 1.0.102.
• Timeline from a 120x40 pty capture: ~0.7s "Resuming session…"; ~1.1s Sessions tab with list; ~3.0s switch to "[Current]" plus the trust dialog. I could not test a remembered-trusted folder, so I don't know whether the auto-switch is caused by the trust prompt.
• Each launch also creates an empty session directory (only workspace.yaml, no events.jsonl). Related: copilot --resume creates an extra empty session-state directory with a new session ID #3908, when doing --resume, it no longers opens last session #5204.
• Changelog 1.0.100: "Use the unified Sessions browser by default for /sessions, /session, and /resume." I did not bisect other versions.
• Workarounds: copilot --continue, copilot --resume <name|id>.