Session persistence: decide whether session_manager or codewhale-state owns session truth
- Dominant language
- Rust
- Stars
- 41k
- Forks
- 3.6k
- Avg merge
- 13h 59m
- Merged PRs (30d)
- 299
Description
From the 0.9.14 refactor backlog.
`tui/src/session_manager.rs` (~7.1k, late-usage ledger, append-time journal stamps) vs `crates/state` `StateStore` (~2.9k). app-server reads `StateStore` while the TUI writes `session_manager` formats. Reconcile which one owns session truth and make the other a view of it. Related symptoms: #6136 (silent transcript eviction at MAX_S…), #6137 (empty auto-sessions occupying the cap), #6138 (resume when the session or provider is gone).
Size: M.
Contributor guide
Research direction
Start by comparing tui/src/session_manager.rs with crates/state StateStore, then trace how the app-server reads StateStore and how the TUI writes session_manager formats. Use related issues #6136, #6137, and #6138 to understand the persistence symptoms. Done means one component owns session truth and the other is a view of it, with the listed session behaviors reconciled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, cli
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100