Skip to content

[Question]: why not support symbol/function @mentions in prompt ? #11878

Closed

Description

@jensenojs

Hi all — maybe I missed something, but I can’t find a quick way to @mention a function/method/class symbol directly in OpenCode.

In Cursor/Windsurf I can just @ a symbol and it’s immediately part of the context. In OpenCode, I always end up going back to Neovim to search the symbol and manually copy/paste it, which is pretty inconvenient.

This is a large open-source project, so I doubt I’m the first person asking for this. I’m not asking for implementation here — just raising the need: symbol-level @mentions, not just file/agent.

I also had GPT investigate this requirement, and it seems that current custom tools/plugins don't yet support custom mention sources. However, I haven't looked into this issue in depth yet; if it does, I'll probably implement one for myself.

If this isn’t supported for a reason (limitations or tradeoffs), I’d love to know.

Activity

  1. github-actions commented on Feb 3, 2026

    @github-actions
    Contributor

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

    Feel free to ignore if none of these address your specific case.

  2. jensenojs commented on Feb 3, 2026

    @jensenojs
    ContributorAuthor

    When dealing with behemoths like MySQL, 99% of your effort goes into tracing complex call chains and understanding module interactions. Conversations with the agent become an iterative cycle of exploration and reference. To maintain the agent's reasoning foundation and prevent it from veering off course, you must frequently provide it with specific symbols and code snippets.

    The bottleneck here is context-switching overhead. Every time I have to pause my train of thought and manually jump between buffers, copy and paste symbols into the prompt, it creates friction.


    update :

    Image
  3. imadNaseer commented on Feb 18, 2026

    @imadNaseer

    got here searching for the exact same feature +1

  4. github-actions commented on Apr 20, 2026

    @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.

  5. jensenojs commented on May 16, 2026

    @jensenojs
    ContributorAuthor

    reopen it

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