Skip to content

Feature request: mark/pin/favorite sessions to distinguish important ones #41231

Closed as not planned

Description

@xingluo-wink

Feature Description

Add the ability to mark/pin/favorite specific sessions in the TUI so important sessions (e.g. ongoing work on a main project) stand out from casual one-off sessions.

Currently sessions can only be listed and switched via /sessions, ordered by recency. With many projects and many sessions, it's hard to quickly find the sessions that are actively being worked on, especially after a few days.

Proposed Behavior

  • In the /sessions list, allow marking a session as pinned/favorite (e.g. a keybind like p, or a marker icon like a star/pin).
  • Pinned sessions could be sorted to the top or shown in a separate group.
  • Persist the pinned state (stored alongside session metadata in the session storage).
  • Optionally support pinning via CLI, e.g. opencode session pin .

Alternatives Considered

  • Relying on descriptive session titles (sessions are auto-titled by the first message) - works but is fragile.
  • Exporting important sessions with /export or opencode export - useful for archiving, but doesn't help with quick resume.

Use Case

User works on several projects at once: one main project (long-running, resumed daily) and many casual tasks. A pin/star feature would make resuming the important session one keypress away instead of hunting through a long session list.

Thanks for considering this!

Activity

  1. github-actions commented on Aug 8, 2026

    @github-actions
    Contributor

    This issue doesn't fully meet our contributing guidelines.

    What needs to be fixed:

    • Feature requests must use the [FEATURE]: prefix in the title (e.g. [FEATURE]: mark/pin/favorite sessions...)
    • The feature request template requires checking the verification box confirming the feature hasn't been suggested before

    Please edit this issue to address the above within 2 hours, or it will be automatically closed.


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

    If you believe this was flagged incorrectly, please let a maintainer know.

  2. github-actions commented on Aug 8, 2026

    @github-actions
    Contributor

    This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

    Feel free to open a new issue that follows our issue templates.

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