Add Virtual Folder/Group Management to the Project Session List

Feature Requests
1

Problem

When working on a large project, hundreds of chat sessions accumulate over time. Currently, all sessions within a single project are displayed in a flat list, making it extremely difficult to find, review, or manage specific sessions. As a heavy user, I often have 600+ sessions per project, and scrolling through an unorganized list to find a past conversation is impractical. There’s no way to logically group related sessions together within the same project.

What problem does this solve?

  • Session discoverability: When you need to revisit a previous conversation (e.g., a bug fix from last week, a design discussion from last month), there’s no way to quickly locate it among hundreds of flat-listed sessions.
  • Workflow continuity: Tasks that span multiple sessions get lost. You can’t group “EDS Phase 1 Refactoring” sessions together to review progress.
  • Daily work management: For users who rely on Qoder for daily development, the inability to organize sessions by topic, feature, or time period makes it nearly impossible to generate daily/weekly reports or review past decisions.

Solution

Add virtual folder/group support within a project’s session list. This is a UI-level organizational feature — no physical file system changes needed. Suggested capabilities:

  1. Create virtual folders within a project’s sidebar (e.g., “Bug Fixes”, “Feature A”, “Sprint 23”)
  2. Drag-and-drop or assign sessions into these folders
  3. Auto-tagging by keywords or date ranges (optional, nice to have)
  4. Collapsible folder tree in the session panel, similar to VSCode’s file explorer
  5. Filter/search within a folder to narrow down sessions

The key point: these folders are purely a management layer on top of the existing session storage. No changes to the underlying conversation-history file structure are required.

How should it work?

  • Right-click in the session panel → “New Folder” to create a group
  • Drag sessions into folders, or use a context menu “Move to Folder → …”
  • Sessions remain in their original location on disk; only the display grouping changes
  • Folder assignments are stored locally (e.g., in the existing SQLite database as a folder_id on chat_session)
  • Folders can be nested (one level deep) or flat — either works
  • A session can belong to one folder (or optionally multiple via tags)

Use Case

  • A developer working on a long-running project accumulates 50+ sessions per week. They create folders like “Auth Module”, “Performance Tuning”, “Code Review Sessions” to stay organized.
  • When preparing a weekly report, they browse by folder to quickly recall what was discussed and decided in each area.
  • When a bug resurfaces, they navigate to the “Bug Fixes” folder to find the original debugging session instead of searching through hundreds of flat-listed sessions.

Priority

:yellow_circle: Medium - Important improvement

Additional Info

Current workaround: We’re building an external knowledge base tool that parses Qoder’s JSONL session files and SQLite metadata to provide tagged, searchable session management outside of Qoder. But native support within Qoder would be far superior.