Skip to content

[FEATURE]: Session status management (Todo, Done, Backlog, etc.) for organizing AI sessions #21590

Closed as not planned

Description

@leoncheng57

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Problem

Currently, OpenCode sessions are a flat list with no way to organize or track their status. When working on multiple tasks across sessions, there's no way to mark sessions as "todo", "in progress", "done", "needs review", etc.

Existing issues like #18071 and #18564 address task-level todo lists within sessions, but this is about session-level status management — treating each AI session itself as a trackable work item.

Proposed Feature

Add session statuses and organization. For reference, Craft Agent implements this nicely in their desktop app (screenshot attached below):

  • Statuses: Backlog, Todo, Needs Review, Done, Cancelled, Flagged, Archived
  • Sidebar filtering: Sessions sorted/grouped by status for easy navigation
  • Labels: User-defined tags for categorizing sessions (e.g., by project, priority)
  • Agent self-management: Allow the agent to set its own session status (e.g., mark as "done" when finished)

Use Cases

  1. Multi-task workflows — Keep track of which coding sessions need attention vs. are complete
  2. Review workflow — Mark sessions as "Needs Review" for human follow-up
  3. Automation triggers — Status changes could trigger webhooks or downstream actions
  4. Session hygiene — Archive old sessions, flag important ones

Benefits

  • Sessions become first-class trackable work items, not just chat threads
  • Users can manage AI-assisted work like a lightweight task board
  • Agents gain the ability to signal completion or request review
  • Much better UX for power users managing many concurrent sessions

Screenshot

Craft Agent's session sidebar showing status-based organization:

Image

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Apr 9, 2026
  2. added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on Apr 9, 2026
  3. assigned and unassigned on Apr 26, 2026
  4. removed
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on May 3, 2026
  5. shuppel commented on Jun 4, 2026

    @shuppel

    @leoncheng57 I see your current feature but have a different approach to it -- check out what I had suggested in my issuer request and maybe we can convince opencode to implement some version of it. Are you using the TUI or the GUI interface?
    #30763

  6. github-actions commented on Aug 4, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

  7. shuppel commented on Aug 5, 2026

    @shuppel

    booooo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions