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]: Token Consumption Analysis and Requirement for a Plugin Disable Feature for Agents #7093

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

Originally created by @alpgul on GitHub (Jan 21, 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

Description

This analysis documents the static token costs introduced by various permissions and the @tarquinen/opencode-dcp@1.2.3 plugin. Tests indicate that even a tool designed for token optimization creates a significant overhead on its own.

Test Methodology & Findings

  • Agent State: Empty / Clean installation.
  • Input Prompt: "hi"
  • Observation: It has been observed that the @tarquinen/opencode-dcp@1.2.3 plugin does not provide the expected optimization on the default system configuration; on the contrary, it causes high token consumption (790 tokens).

Token Usage Table

Plugin / Permission Token Cost
todowrite 2148
task 1146
@tarquinen/opencode-dcp@1.2.3 790
read 482
websearch 468
codesearch 366
webfetch 336
grep 322
glob 276
skill 119
todoread 73
edit 0
list 0
lsp 0
external_directory 0
doom_loop 0
bash -3

Analysis Results

  • Contradictory Situation: The fact that a "token reduction tool" itself consumes 790 tokens leads to inefficient token usage.
  • Ineffectiveness: It has been confirmed that the tool fails to deliver the promised performance or savings on the default system.

Proposed Action (Feature Request)

A plugin disable feature for agents should be implemented to allow the plugin to be completely deactivated. This will provide users with the ability to manually intervene in scenarios where the optimization is ineffective or where the plugin's own cost outweighs its savings.

Originally created by @alpgul on GitHub (Jan 21, 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 ### Description This analysis documents the static token costs introduced by various permissions and the `@tarquinen/opencode-dcp@1.2.3` plugin. Tests indicate that even a tool designed for token optimization creates a significant overhead on its own. ### Test Methodology & Findings * **Agent State:** Empty / Clean installation. * **Input Prompt:** "hi" * **Observation:** It has been observed that the `@tarquinen/opencode-dcp@1.2.3` plugin does not provide the expected optimization on the default system configuration; on the contrary, it causes high token consumption (790 tokens). ### Token Usage Table | Plugin / Permission | Token Cost | | --- | --- | | `todowrite` | 2148 | | `task` | 1146 | | **@tarquinen/opencode-dcp@1.2.3** | **790** | | `read` | 482 | | `websearch` | 468 | | `codesearch` | 366 | | `webfetch` | 336 | | `grep` | 322 | | `glob` | 276 | | `skill` | 119 | | `todoread` | 73 | | `edit` | 0 | | `list` | 0 | | `lsp` | 0 | | `external_directory` | 0 | | `doom_loop` | 0 | | `bash` | -3 | ### Analysis Results * **Contradictory Situation:** The fact that a "token reduction tool" itself consumes 790 tokens leads to **inefficient token usage.** * **Ineffectiveness:** It has been confirmed that the tool fails to deliver the promised performance or savings on the default system. ### Proposed Action (Feature Request) A **plugin disable feature for agents** should be implemented to allow the plugin to be completely deactivated. This will provide users with the ability to manually intervene in scenarios where the optimization is ineffective or where the plugin's own cost outweighs its savings.
yindo added the discussionzen labels 2026-02-16 18:06:10 -05:00
yindo commented 2026-02-16 18:06:10 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 21, 2026):

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

  • #7687: [FEATURE]: Disable plugins via cli - requests ability to disable plugins without manual config file editing
  • #8320: [FEATURE]: Manage plugins like providers in configuration - proposes project-level plugin configuration with disabled_plugins/enabled_plugins support
  • #8342: [FEATURE]: Optimization of skill context control and user manual control entry - discusses unloading context from skills and similar manual controls for token optimization

These issues all relate to giving users control over which plugins and tools are loaded to manage token consumption and overhead. Your analysis provides valuable data about static token costs that supports the need for these features.

Feel free to ignore if your specific use case differs from these.

@github-actions[bot] commented on GitHub (Jan 21, 2026): This issue might be a duplicate of existing issues. Please check: - #7687: [FEATURE]: Disable plugins via cli - requests ability to disable plugins without manual config file editing - #8320: [FEATURE]: Manage plugins like providers in configuration - proposes project-level plugin configuration with disabled_plugins/enabled_plugins support - #8342: [FEATURE]: Optimization of skill context control and user manual control entry - discusses unloading context from skills and similar manual controls for token optimization These issues all relate to giving users control over which plugins and tools are loaded to manage token consumption and overhead. Your analysis provides valuable data about static token costs that supports the need for these features. Feel free to ignore if your specific use case differs from these.
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 zen
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#7093
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?