Clausona Account Manager

The README describes config directories, credentials, session history, shared files, quota lookups, and update checks. It also explains API-key input through a prompt, stdin, Keychain/local storage, or environment/command sources, supporting full marks for data-flow transparency. Switching is explicit, updates ask by default, removal preserves profile data, and session separation and repair are documented, supporting moderate scores for privilege, confirmation, and recovery. The dependency list gives versions but the supplied material shows no vulnerability review or mitigation. Publisher identity is unknown, and the repository gives a contribution path without establishing maintainer identity or update responsibility, so those scores remain limited.

The README gives broadly consistent descriptions of account separation, shared configuration, platform differences, and network behavior. The CI file lists linting, type checking, tests, builds, and bundle smoke checks; the Superset plugin test also covers errors, token redaction, and deletion safeguards. These are repository artifacts, not checks run for this review. Some reliability claims remain primarily documented assertions, and the supplied files omit core implementation, so consistency and dependency availability do not receive full marks. Error cases are illustrated, but the evidence does not establish clear messages for every path.

The README addresses people using multiple Claude Code or Codex accounts on one machine and covers personal, work, organization, API endpoint, parallel-session, Superset, and quota scenarios. It clearly limits API profiles to Claude Code and describes Windows link behavior and session-sharing differences, earning strong boundary coverage. Invocation is mostly explicit through commands and a shell hook, though first-session API-key confirmation and environment variables that cause the hook to step aside show some trigger complexity. Platform and runtime requirements are detailed, but the core implementation is not supplied for compatibility verification.

The README is organized into installation, quick start, features, operation, commands, FAQ, and limitations, with practical examples and platform-specific instructions. The MIT license text is complete. The package version is 0.5.1-beta and CI lists cross-platform checks, but no changelog is supplied, leaving version history thin. A contribution path is present, but maintainer responsibility and verified publisher identity are not established, so maintenance responsibility is only partly clear.

The CLI, JSON listing, interactive dashboard, and usage view help users select accounts and inspect quota. Per-account sign-in separation with shared settings and optional history addresses concrete repeated setup work. The README also explains the Node.js requirement, shell hook setup, key handling, and Windows link limitations, making user costs visible. Initial setup and platform constraints still add effort, and the supplied material lacks core implementation or runtime evidence to confirm every claimed benefit.

The README gives traceable descriptions of commands, data locations, credential sources, limitations, and network calls. CI and plugin tests provide a second kind of repository evidence for some error handling and safeguards. The supplied files omit the core product implementation, and the README's comparisons are described as based on other projects' documentation rather than independent verification. CI describes intended checks but does not establish that they were run or passed, so scores are moderate.