feat: add /session-id command to copy session ID to clipboard

[huynguyen03dev]

Problem

There's no easy way to copy the current session ID in the TUI. Users need session IDs for:

• Referencing specific sessions in conversation ("continue from session X")
• Handoff workflows between sessions
• Manual session lookups with session_read/session_search tools
  Currently requires mouse-selecting from status bar or running session_list and scanning output.

Proposed Solution

Add a /session-id slash command that copies the current session ID to clipboard with a toast confirmation.
~10 lines, similar pattern to existing commands. I have a working implementation ready.

Alternatives Considered

• /copy-session-id — too verbose compared to other slash commands (/editor, /skills)
• Keybind only — less discoverable than slash command

[taoalpha]

Manual session lookups with session_read/session_search tools Currently requires mouse-selecting from status bar or running session_list and scanning output.

Not exactly sure about your use case here, but I recently had a use case to retrieve current session id within a skill run, my workaround currently is creating a custom tool (current-session-lookup):

import { tool } from "@opencode-ai/plugin"

export default tool({
  description: "Retrieve current session information.",
  async execute(args, context: { sessionID?: string; messageID?: string; directory?: string; worktree?: string }) {
    return JSON.stringify(
      {
        sessionID: context.sessionID,
        messageID: context.messageID,
        directory: context.directory,
        worktree: context.worktree,
      },
      null,
      2,
    )
  },
})

test run:

opencode run --model opencode/big-pickle "invoke current-session-lookup tool and print the output"

> Sisyphus (Ultraworker) · big-pickle

⚙ current-session-lookup Unknown

Session ID:    ses_3539926bdffe4zzzZ6tyV0OE60
Message ID:    msg_cac66d9af001q6RD6DPqmN7Fcn
Directory:     xxxx
Worktree:      xxxx

[github-actions]

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