anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE]: Allow custom tool description #8215

New Issue
Open
opened 2026-02-16 18:09:26 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:09:26 -05:00
Owner
Copy Link
Copy Source

Originally created by @podliy16 on GitHub (Feb 1, 2026).

Originally assigned to: @thdxr on GitHub.

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

Problem

Tool descriptions are hardcoded and can't be modified by users. This creates issues when:

  • Default tool instructions don't match the user's actual tools
  • Users are forced to override instructions in system/user prompts, leading to conflicting guidance
  • Token budget is wasted on irrelevant tool descriptions

Example
The bash tool description states:

Use the gh command via the Bash tool for ALL GitHub-related tasks including working with issues, pull requests, checks, and releases. If given a Github URL use the gh command to get the information needed.

If I use GitLab instead, I need to tell the model about glab CLI. This creates contradictory instructions ("use gh" or "use glab") that the model may not resolve correctly.

Solution
Add a way to customize tool descriptions, possibly via a plugin system or configuration file. Synchronization issues would be the user's reponsibility.

Originally created by @podliy16 on GitHub (Feb 1, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request **Problem** Tool descriptions are hardcoded and can't be modified by users. This creates issues when: - Default tool instructions don't match the user's actual tools - Users are forced to override instructions in system/user prompts, leading to conflicting guidance - Token budget is wasted on irrelevant tool descriptions **Example** The bash tool description states: ``` Use the gh command via the Bash tool for ALL GitHub-related tasks including working with issues, pull requests, checks, and releases. If given a Github URL use the gh command to get the information needed. ``` If I use GitLab instead, I need to tell the model about glab CLI. This creates contradictory instructions ("use gh" or "use glab") that the model may not resolve correctly. **Solution** Add a way to customize tool descriptions, possibly via a plugin system or configuration file. Synchronization issues would be the user's reponsibility.
yindo added the discussion label 2026-02-16 18:09:26 -05:00
yindo commented 2026-02-16 18:09:27 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 1, 2026):

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

  • #7362: Tool call descriptions as skills - proposes moving tool descriptions to skills to reduce token cost
  • #11428: Add description field to MCP server configuration - related to customizing descriptions for specific tools
  • #9570: Support Gemini API by trimming/adapting tool descriptions - addresses tool description customization needs
  • #5715: The problem of overly long bash description - highlights issues with hardcoded tool descriptions

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

@github-actions[bot] commented on GitHub (Feb 1, 2026): This issue might be a duplicate of existing issues. Please check: - #7362: Tool call descriptions as skills - proposes moving tool descriptions to skills to reduce token cost - #11428: Add `description` field to MCP server configuration - related to customizing descriptions for specific tools - #9570: Support Gemini API by trimming/adapting tool descriptions - addresses tool description customization needs - #5715: The problem of overly long bash description - highlights issues with hardcoded tool descriptions Feel free to ignore if none of these address your specific case.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8215
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?