Skip to content

[Bug]: Extreme token/cost spike after upgrade — $20 used in one hour #3098

@GEMTechnologies

Description

@GEMTechnologies
  1. Open Reasonix and start a coding/debugging task on an existing production project.

  2. Ask Reasonix to diagnose and fix a production coding issue.

  3. Let Reasonix inspect multiple project files and continue debugging across the codebase.

  4. During the same session, Reasonix repeatedly searched/read files, inspected configuration, checked application logic, reviewed API-related code, and continued diagnosing the issue.

  5. Keep the coding/debugging session running for about one hour.

  6. Check DeepSeek billing/token usage after the session.

Actual result:
Reasonix consumed approximately USD 20 in about one hour. This is far above my normal DeepSeek mass-coding usage, which is usually around USD 10 per month.

Expected result:
Reasonix should not consume such a large amount in one hour under normal coding/debugging usage. It should keep DeepSeek cache usage stable, avoid repeatedly resending huge context, show cost/context/cache-hit information clearly, warn before high-cost actions, and allow a hard cost limit per session.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingv2Go rewrite (1.x) — main-v2 branch, active development

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions