Skip to content

[FEATURE]: web: move sessions that require attention to the top #53757

Open

Description

@bilogic

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

Make it like a chat, sort so that most recently updated is at the top for opencode version 2.0.25

Image

Activity

  1. changed the title [-][FEATURE]: move sessions that require attention to the top[/-] [+][FEATURE]: web: move sessions that require attention to the top[/+] on Oct 7, 2026
  2. opencode-agent commented on Oct 7, 2026

    @opencode-agent
    Contributor

    Thanks for the suggestion! So we can route this to the right place, could you tell us:

    1. Which OpenCode version you're using (output of opencode --version, or opencode2 --version if you're on v2)
    2. Which interface the screenshot shows: the terminal UI (TUI), the desktop app or the web app, and which list (for example the /sessions picker, the home session list, or the session tabs)

    You can reply here with the details, or edit the issue and then leave a comment saying you've updated it.

  3. github-actions commented on Oct 7, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    • #13569: requests ordering session lists by most recently updated first.
    • #13030: proposes a Web/Desktop inbox for triaging sessions that need user attention.
  4. opencode-agent commented on Oct 7, 2026

    @opencode-agent
    Contributor

    Thanks for the details! I tested this on v2.0.24 (2.0.25 isn't on npm yet) and found what's behind it. A session's "last updated" time only changes when you send a prompt. It doesn't change while the reply streams in, or when the reply finishes. The web session list sorts by that time, so a session that just finished, or is waiting on you, doesn't move to the top.

    What I did:

    1. Started session A and sent a prompt.
    2. Started session B and sent a prompt whose reply streamed for about 12 seconds.
    3. Checked session B's updated time during and after the reply. It stayed at the moment the prompt was sent.

    The stale timestamp is tracked in #36893. Putting sessions that need attention (permissions or questions) first would be an extra feature on top of that, since nothing currently orders sessions that way.

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