Problem
Running /new creates a fresh session, but the previous session disappears from the default resume picker.
This makes the old session appear lost and prevents users from returning to it through the normal corbits resume --pick flow.
Reproduction
Verified with Corbits Code v0.2.97:
- Start Corbits in a repository.
- Rename the current session:
- Create a new session:
- Rename the new session:
- Exit Corbits.
- Run:
Only second-session is shown. first-session is absent.
Findings
This does not appear to be session-data loss. /new successfully creates a new session, and the previous session remains on disk.
During session rotation, src/tui/runner.ts records the outgoing session with the done status. The default filtering in src/tui/pick-session.ts only includes sessions with the running or cancelled status.
As a result, the previous session is preserved but hidden from the default resume picker.
Running the focused session and slash-command tests produced 53 passes and no failures. The tests currently encode the completed-session filtering as intended behavior.
No existing GitHub issue matching this problem was found.
Current workaround
Completed sessions become visible when the picker is opened with:
corbits resume --pick --force
The previous session can then be selected and resumed successfully.
Problem
Running
/newcreates a fresh session, but the previous session disappears from the default resume picker.This makes the old session appear lost and prevents users from returning to it through the normal
corbits resume --pickflow.Reproduction
Verified with Corbits Code v0.2.97:
Only
second-sessionis shown.first-sessionis absent.Findings
This does not appear to be session-data loss.
/newsuccessfully creates a new session, and the previous session remains on disk.During session rotation,
src/tui/runner.tsrecords the outgoing session with thedonestatus. The default filtering insrc/tui/pick-session.tsonly includes sessions with therunningorcancelledstatus.As a result, the previous session is preserved but hidden from the default resume picker.
Running the focused session and slash-command tests produced 53 passes and no failures. The tests currently encode the completed-session filtering as intended behavior.
No existing GitHub issue matching this problem was found.
Current workaround
Completed sessions become visible when the picker is opened with:
The previous session can then be selected and resumed successfully.