Skip to content

[FEATURE]: Token Consumption Analysis and Requirement for a Plugin Disable Feature for Agents #9858

Closed

Description

@alpgul

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.

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Jan 21, 2026
  2. github-actions commented on Jan 21, 2026

    @github-actions
    Contributor

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

    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.

  3. github-actions commented on Mar 28, 2026

    @github-actions
    Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

discussionUsed for feature requests, proposals, ideas, etc. Open discussionzenRelates to Zen

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions