Skip to content

[FEATURE] Disclose per-turn token cost of reactions + opt-out during setup #76

Description

@Nipeno

What would you like?

Two small things around reactions transparency:

  1. A note in the README (near the install steps) that reactions add tokens to every response — the MCP server instructs Claude via system prompt to append <!-- buddy: ... --> at the end of every turn, which means every session has ongoing token overhead even when the user isn't interacting with the buddy directly.
  2. A prompt during install asking whether to enable reactions, or make them opt-in by default. There's already a /buddy off command, but it requires the user to discover it after the fact.

Why?

Users coming from the original /buddy may not expect the MCP version to affect token usage — the original was purely a display feature. Right now nothing in the README or install flow warns about this, so users on paid plans or with tight budgets may accumulate unexpected cost before they notice.

Ideas for implementation

  • Add one line to the README under install: something like "Reactions are enabled by default and add a small number of tokens per turn. Run /buddy off to disable."
  • Optionally, add a y/N prompt to the setup wizard: Enable reactions? Buddy will comment on your code each turn (adds ~20–50 tokens per response)

Not asking to change the default necessarily — just surfacing it so users can make an informed choice before their first session.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions