Skip to content

Feature Request: Support for Extra Usage on Base Plans #174

@alex365nl

Description

@alex365nl

## Feature Request: Support for Extra Usage / Additional Budget on Base Plans

Problem Statement

Currently, claude-monitor supports fixed plan types (Pro, Max5, Max20, Custom), but Anthropic allows users to
purchase extra usage on top of their base subscription plans. The tool doesn't support this hybrid billing
model, making it difficult to accurately track usage and costs for users who purchase additional tokens.

Current Behavior

When a user has:

  • Base Plan: Pro (€21.78/month with ~44k tokens included)
  • Extra Usage: €5 additional purchase (~156k extra tokens)
  • Total Available: 200k tokens

They must use --plan custom --custom-limit-tokens 200000, which:

  • ❌ Doesn't distinguish between base plan and extra usage
  • ❌ Shows incorrect cost limits (defaults to $50 instead of actual ~$23-26)
  • ❌ Doesn't help track if you're consuming base allowance vs paid extras
  • ❌ Loses context of what plan you actually have

Proposed Solution

Add support for extra usage through new CLI options:

claude-monitor --plan pro --extra-tokens 156000 --extra-cost 5.40

Alternative syntax:
claude-monitor --plan pro --extra-usage-tokens 156000 --extra-usage-cost 5.40

Expected Behavior

Display Output:
┌─────────────────────────────────────────┐
│ Plan: Pro + Extra Usage                 │
│ Base:   44k tokens  ($18.00)            │
│ Extra: 156k tokens  ($5.40)             │
│ Total: 200k tokens  ($23.40)            │
│                                         │
│ Used:   41k / 200k  (20.5%)             │
│ Cost:   $8.45 / $23.40  (36.1%)         │
└─────────────────────────────────────────┘

Benefits:
1. ✅ Accurate cost tracking matching actual billing
2. ✅ Clear visibility into base vs extra usage consumption
3. ✅ Helps users understand if they're exceeding their base allowance
4. ✅ Better reflects Anthropic's actual billing model
5. ✅ Could show warnings like "You've consumed your base allowance, now using extra tokens"

Implementation Suggestions

Config/Settings:
Update last_used.json to support:
{
  "plan": "pro",
  "extra_usage_tokens": 156000,
  "extra_usage_cost": 5.40,
  "theme": "dark",
  ...
}

Code Changes:
1. Add CLI arguments: --extra-tokens, --extra-cost
2. Update Plans class to support composite limits (base + extra)
3. Modify display logic to show breakdown when extra usage is configured
4. Optionally: Add progress bars showing base vs extra consumption

Backward Compatibility:
- If no extra usage specified, behavior remains unchanged
- Custom plan still works as fallback
- Existing configs remain valid

Use Cases

1. Pro + Extra Usage (common with European pricing)
  - Base: Pro plan €21.78 → ~44k tokens
  - Extra: €5 → ~156k tokens
  - Total: 200k tokens
2. Max5 + Extra Usage
  - Base: Max5 plan → 88k tokens
  - Extra: Variable amount purchased
  - Total: 88k + extra
3. Tracking Budget Separately
  - Users want to know: "Am I still on my base plan or am I paying extra?"
  - Warning when base allowance depleted

Alternative Workarounds (Current State)

Users currently must:
1. Calculate total tokens manually (base + extra)
2. Use --plan custom --custom-limit-tokens <total>
3. Manually track which portion is base vs extra
4. Accept incorrect cost limits

This feature would eliminate these manual workarounds.

Additional Context

Example Anthropic Billing:
- Pro plan: €21.78/month (Europe) or $20/month (US)
- Extra usage: Purchased in increments (€5, €10, etc.)
- Tokens are additive: base allowance + purchased extras

Screenshot/Example:
User dashboard in Anthropic console might show:
Plan: Pro
Extra Usage: €5.00 purchased
Total tokens available: 200,000

The monitor should reflect this same breakdown.

---
This feature would make the tool more accurate and useful for users who purchase extra usage on top of their base plans.
---

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