timharris707/modeldeck

Selection

Select when

• You use Claude Code or Codex CLI on macOS 14 or newer.
• You maintain multiple provider accounts or subscriptions.
• You need live remaining-capacity and reset-time visibility.
• You want low-capacity notifications without repeated nagging.
• You want one-click profile activation for new terminal sessions.
• You prefer a local application with no hosted backend.
• You need Claude and Codex usage shown in one interface.
• You want provider credentials to remain in provider-managed profiles and Keychain storage.

Boundaries

Avoid when

• You need Windows or Linux support.
• You need a native Claude Code plugin, hook, command, or skill.
• You need cloud synchronization or remote team dashboards.
• You require commercial usage rights under a permissive open-source license.
• You need switching to alter already-running CLI sessions.
• You use only API-key billing without the documented CLI account workflows.
• You cannot permit a bundled localhost background service.
• You need independently audited security or privacy guarantees.

Strengths

Capabilities

Risk profile

Risks and limitations

• Uncertainty: only selected first-party files were supplied, so daemon implementation, database schema, account-switching code, update verifier, managed proxy, and release workflows were not directly inspected.
• Uncertainty: repository metadata and documentation dates are in 2026 relative to this analysis context, so current release status, activity, and adoption cannot be independently reconciled.
• Uncertainty: a repository binding document describes this repository as a public release mirror of a separate private development repository, so source and issue-history completeness are unclear.
• Security, privacy, credential-isolation, update-signature, and no-telemetry claims are repository-authored and were not independently audited.
• The supported desktop platform is macOS 14 or newer; no Windows or Linux application is documented.
• Claude Code and Codex CLIs must already be installed for the provider workflows a user wants to track.
• Account activation affects only new terminal sessions and intentionally leaves running sessions unchanged.
• Removing ModelDeck may leave its locally generated Keychain items unless the user deletes them separately.
• Deleting ModelDeck's application-support directory also removes the managed isolated sign-ins stored under that directory.
• The PolyForm Noncommercial license reserves commercial rights and is not a standard permissive open-source license.
• Optional update checks and approved downloads contact GitHub, while usage reads contact the configured providers.
• Provider endpoints, CLI protocols, authentication storage, limit schemas, and plan behavior can change independently of ModelDeck.

The documented daemon binds only to 127.0.0.1, rejects unexpected Host and Origin headers, and requires a per-server token plus SameSite=Strict cookie for mutations. State is described as owner-only SQLite. Updates are described as EdDSA- and Apple-signature-verified. These controls were not independently inspected or audited.