What happened
After archiving a conversation from the Desktop session list, there is no visible way to unarchive / restore it in the Desktop UI. The conversation appears to be gone from the normal list, and I could not find any "archived" section, filter, or restore action in the sidebar or the session list. The only workaround I found was editing runtime.sqlite directly (session_metadata.is_archived = 0 + status back to active), which is not something a normal user can or should do.
How to reproduce
- Open the Desktop app, open the session list (sidebar).
- Right-click / open the "⋯" menu on any conversation → choose Archive.
- Try to find the conversation again: search it, scroll the list, check for any "Archived" group/filter/section, and look for an Unarchive/Archive-Restore action.
- Expected: an obvious way to restore archived conversations (e.g. an "Archived" section in the list, a filter toggle, or an "Unarchive" action), and that the conversation is still discoverable.
- Actual: the archived conversation is not discoverable in the Desktop UI and there is no restore entry point.
Environment
- Maka version: 0.1.6 (macOS arm64 dmg)
- OS: macOS
- Surface: Desktop
- (CLI
maka --resume <session-id> can reopen the session, but the Desktop UI offers no equivalent.)
Logs, screenshots, or additional context
Data is not lost — confirmed the archived sessions still exist in runtime.sqlite (session_metadata with is_archived = 1, status = 'archived'), including all messages and artifacts. So this is purely a missing UX entry point for unarchiving. A restore action in the row menu (like the existing Archive action) or an "Archived" section/filter would resolve it.
What happened
After archiving a conversation from the Desktop session list, there is no visible way to unarchive / restore it in the Desktop UI. The conversation appears to be gone from the normal list, and I could not find any "archived" section, filter, or restore action in the sidebar or the session list. The only workaround I found was editing
runtime.sqlitedirectly (session_metadata.is_archived = 0+ status back toactive), which is not something a normal user can or should do.How to reproduce
Environment
maka --resume <session-id>can reopen the session, but the Desktop UI offers no equivalent.)Logs, screenshots, or additional context
Data is not lost — confirmed the archived sessions still exist in
runtime.sqlite(session_metadatawithis_archived = 1,status = 'archived'), including all messages and artifacts. So this is purely a missing UX entry point for unarchiving. A restore action in the row menu (like the existing Archive action) or an "Archived" section/filter would resolve it.