Skip to content

Feature request: show usage per profile #1

@Hobeom

Description

@Hobeom

Summary

It would be useful if aimux could show usage per profile/subscription, for example token usage, estimated cost, session count, or rate-limit-related state for main, work, personal, etc.

Current behavior

aimux status currently shows profile/auth/model/shared-link health, but it does not expose usage information:

aimux status

Example fields shown today:

  • profile name
  • auth status
  • default model
  • shared symlink health

There does not appear to be a usage, stats, or cost command in the CLI.

Why this would help

When using aimux to manage multiple Claude Code subscriptions or accounts, it is hard to tell which profile is consuming usage. A quick overview would make it easier to decide which profile to run and to diagnose account-specific limits.

Possible implementation ideas

  • Add a command such as:
aimux usage
aimux usage --profile work
aimux usage --since 7d
  • Aggregate per-profile data from profile-local files such as metrics/costs.jsonl, stats-cache.json, policy-limits.json, transcripts, or other Claude CLI usage metadata when available.
  • Consider treating usage-related paths as private/profile-local instead of shared, if required for accurate future accounting.
  • If historical logs are already shared via symlinks, document that past usage may not be separable and only future usage can be tracked accurately after profile-local logging is enabled.

Notes

In my local setup, metrics, projects, and transcripts under non-source profiles were symlinked back to the shared source directory, so the current layout may make exact historical per-profile attribution difficult. Even a best-effort or forward-looking implementation would be helpful.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions