Skip to content

[FEATURE]: pass sessionID into tool.definition hooks #17334

Closed as not planned
Closed as not planned
[FEATURE]: pass sessionID into tool.definition hooks#17334
Assignees
rekram1-node

Description

@ian-pascoe
ian-pascoe
opened on Mar 13, 2026

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

tool.definition hooks should always receive the active sessionID when tool definitions are built.

Right now that session context is not available consistently across tool listing paths, which makes it hard for plugins to customize tool descriptions or schemas per session. The need is the same across prompt resolution, batch execution, debug tool listing, and /experimental/tool, so those entry points should use one session-aware contract instead of each path behaving differently.

This would also keep the plugin hook contract and generated SDK types aligned with the API behavior.

Activity

  1. github-actions
    assigned
    rekram1-node
    on Mar 13, 2026
  2. github-actions
    added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    needs:complianceThis means the issue will auto-close after 2 hours.
    on Mar 13, 2026
  3. ian-pascoe
    changed the title [-]tool.definition hooks should receive the active session ID[/-] [+][FEATURE]: pass sessionID into tool.definition hooks[/+] on Mar 13, 2026
  4. github-actions
    removed
    needs:complianceThis means the issue will auto-close after 2 hours.
    on Mar 13, 2026

  5. github-actions commented on Mar 13, 2026

    @github-actions
    github-actionsBot
    on Mar 13, 2026 – with GitHub Actions
    Contributor

    Thanks for updating the issue! It now follows our contributing guidelines and has been marked as compliant.

  6. thdxr
    removed
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on May 3, 2026

  7. github-actions commented on Jul 3, 2026

    @github-actions
    github-actionsBot
    on Jul 3, 2026 – with GitHub Actions
    Contributor

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

  8. github-actions
    closed this as not plannedon Jul 3, 2026
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