Bug: /new can return to previous session after blanking screen

[shiny-code-bot]

Summary

Using /new appeared to start a fresh session, but after the screen blanked the previous session content came back. The command should establish a clear context boundary; resurfacing the old chat makes it unclear whether the model has been reset and can cause follow-up work to inherit stale assumptions.

Observed Behavior

• User ran /new in the Every Code TUI.
• The screen blanked, suggesting a fresh session was being created.
• Instead of an empty/new chat, the previous session content reappeared.
• The user then asked whether this was actually a new session, because the prior transcript was still visible.

Expected Behavior

• /new should open a visibly fresh conversation/session.
• Previous chat history should not reappear as the active chat after the transition.
• If any state is intentionally retained, the UI should make that boundary explicit rather than showing the prior session as if /new failed.

Environment

• Repo: cbusillo/code
• Observed command/version: code 0.6.109
• Local branch at report time: fix/concurrent-session-model-context
• Current commit at report time: 6d5de47dbd

Notes

• This may overlap with deeper harness/session mechanics work tracked in Triage rollout/session friction audit findings #90, but the /new behavior is concrete enough to track as its own bug.
• The local branch had unrelated uncommitted concurrent-session changes at the time of reporting, so reproduction should verify against current main or a clean build as well.