You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: web: move sessions that require attention to the top #53757
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
Thanks for the suggestion! So we can route this to the right place, could you tell us:
Which OpenCode version you're using (output of opencode --version, or opencode2 --version if you're on v2)
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.
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:
Started session A and sent a prompt.
Started session B and sent a prompt whose reply streamed for about 12 seconds.
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.
Activity
[-][FEATURE]: move sessions that require attention to the top[/-][+][FEATURE]: web: move sessions that require attention to the top[/+]opencode-agent commentedon Oct 7, 2026
Thanks for the suggestion! So we can route this to the right place, could you tell us:
opencode --version, oropencode2 --versionif you're on v2)/sessionspicker, 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.
github-actions commentedon Oct 7, 2026
This issue might be a duplicate of existing issues. Please check:
opencode-agent commentedon Oct 7, 2026
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:
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.