Activity

1. code-yeongyu commented on Feb 17, 2026

   

   code-yeongyu

   on Feb 17, 2026

   Owner

   More actions

   Thanks for filing this! You're correct that this is an upstream OpenCode core issue with the /sessions picker.

   Current state in oh-my-opencode:

   We already have session management tools that can help work around this:

   • session_list - Lists sessions with filters:

     • from_date / to_date - ISO 8601 date range filtering
     • project_path - Filter by project directory
     • limit - Limit results

   • session_read - Read messages from a specific session by ID

   • session_search - Search across session content

   • session_info - Get metadata for a session

   The gap:
   While you can list and read older sessions, there's currently no session_select tool to actually continue a session from the agent. Users have to manually type /continue <session_id> in the TUI after finding the ID.

   Next steps:

   1. I'll look into adding a session_select tool that returns the proper /continue command
   2. We should document the date filtering capabilities better in the features guide

   Keeping this open as a valid feature request to bridge the upstream limitation.
2. code-yeongyu commented on Mar 2, 2026

   

   code-yeongyu

   on Mar 2, 2026

   Owner

   More actions

   [sisyphus-bot]

   Analysis

   This is a valid feature request to bridge the upstream OpenCode TUI limitation where /sessions picker only shows recent sessions.

   Current Session Tools Assessment

   I analyzed the codebase and found 4 existing session management tools in src/tools/session-manager/tools.ts:

   Tool	Purpose	Status
   session_list	List sessions with date/project filters	✅ Available
   session_read	Read messages from a session by ID	✅ Available
   session_search	Search across session content	✅ Available
   session_info	Get session metadata	✅ Available

   Gap Confirmed

   The session_select tool mentioned by @code-yeongyu does not exist in the codebase. Verified via search - no matches for session_select.

   The Challenge

   A session_select tool faces an architectural constraint: OpenCode plugins/tools cannot directly invoke TUI commands like /continue. The plugin operates within the agent context, not the TUI shell.

   Potential approaches:

   1. Documentation approach (low effort): Add clear examples showing how to use session_list with date filters to find older sessions, then manually /continue <session_id>

   2. Helper output approach (medium effort): Create session_select that returns a formatted message with the /continue <session_id> command ready for the user to copy-paste

   3. Navigation bridge (high effort / may not be possible): Investigate if OpenCode exposes any API for session switching from within a plugin context

   Recommended Next Steps

   For maintainers:

   • Document the date filtering capabilities (from_date, to_date on session_list) with examples for finding older sessions
   • Evaluate feasibility of a session_select helper that outputs the proper /continue command
   • Link to upstream OpenCode issue when available

   For users (workaround):

   # List sessions before a specific date
   session_list(from_date: "2026-01-01", to_date: "2026-02-11")
   
   # Then manually continue: /continue <session_id>
   

   Classification

   • Type: Feature Request / Enhancement
   • Priority: Low-Medium (has workaround)
   • Effort: Small (documentation) to Medium (new tool)
   • Blocked on: None, but upstream fix would eliminate need
3. code-yeongyu

   added

   triage:needs-investigationNeeds deeper analysisNeeds deeper analysis

   on Mar 24, 2026
4. code-yeongyu commented on May 16, 2026

   

   code-yeongyu

   on May 16, 2026

   Owner

   More actions

   [sisyphus-bot]

   Read-only triage on dev.

   Current state

   • Boulder state (src/features/boulder-state/) tracks active plans but does not expose a "done" or "archive" state for completed plans.
   • Plans remain in the active list indefinitely unless manually removed.
   • Adding a done/complete state would require:
     1. A new state enum value (done).
     2. A transition hook from active to done.
     3. UI filtering to hide done plans from the active list.

   Action

   • Labels: triage:feature-request (already set). No label change.
   • Keep open. Assigning code-yeongyu for scope decision: whether to add plan lifecycle states or to keep the current flat list.
5. code-yeongyu

   self-assigned this

   on May 16, 2026
6. code-yeongyu

   closed this as completedin #5265on Jun 14, 2026