Usage overviewClaude + Codex

One quiet usage surface for Claude and Codex.

If Claude and Codex are both part of your day, the status should not live in two separate mental tabs. CodexIsland keeps limits, reset context, and cost estimates in one small place on the Mac.

InstallView on GitHub
Useful when

You use more than one AI coding tool on a Mac and want one small usage surface instead of several provider-specific checks.

Claude CodeCodex CLIReset windowsDaily and month-to-date token cost
CodexIsland cost panel showing daily and monthly token usage.

One surface for multi-provider coding.

The common developer workflow is no longer one AI tool. You might ask Claude to reason through a repo, run Codex for another pass, then decide where the next step belongs.

  • Claude and Codex shown side by side.
  • Limits screen for usage windows.
  • Cost screen for local token-cost estimates.
  • Small notch UI instead of another browser dashboard.

Local by default.

Seeing usage should not require giving another service a copy of your coding history. CodexIsland is designed around local reads from existing provider auth and session logs.

  • No CodexIsland account.
  • No hosted analytics dashboard for your app usage.
  • No upload of Claude or Codex session logs.
  • Open-source implementation for inspection.
In practice

Less checking. More context.

Need
Manual path
With CodexIsland
Tool coverage
Check Claude and Codex separately.
Show both in one Mac notch panel.
Workflow fit
Open a browser dashboard or run a command.
Keep the signal visible across the desktop.
Cost context
Wait for billing or parse logs manually.
Estimate daily and monthly local token cost.
Provider notes

Limits change. The app follows what your tools expose.

CodexIsland does not promise fixed provider quotas. It reads the available local usage context and keeps that signal close while you work.

Claude Code error referenceOpenAI Codex with ChatGPT plan
FAQ

Common questions.

What is the best way to track AI coding usage on Mac?

For Claude Code and Codex CLI workflows, the most useful tracker is one that stays visible while you code and reads local session context instead of making you open another dashboard.

Can one Mac app track Claude Code and Codex CLI together?

Yes. CodexIsland shows Claude and Codex side by side for usage windows and local token-cost estimates, so mixed AI coding workflows are visible in one place.

Does CodexIsland track API billing dashboards too?

No. It focuses on local Claude Code and Codex CLI-style usage. It is not a replacement for provider billing dashboards or API-console spend reports.

More workflows

Other ways to use CodexIsland.

Claude CodeKeep Claude Code usage in sight.

Keep Claude Code session pressure, reset timing, and local token-cost estimates visible from the MacBook notch.

Codex CLISee Codex CLI usage without leaving your flow.

Show Codex CLI usage context and local token spend from a small MacBook notch surface.

Claude Code resetsPlan around Claude Code resets before they stop you.

Keep Claude Code reset context nearby before a long task runs into a limit.

OverviewChoose the view that matches how you code.

Choose the CodexIsland view for Claude Code, Codex, reset windows, and local token-cost estimates on Mac.

Install

Start tracking from the notch.

Free, open-source, local-first, and built for macOS.

$brew install --cask ericjypark/tap/codexisland

Download CodexIsland-0.1.6.dmg — or browse all releases. Then run this once to clear the quarantine bit:

$xattr -d com.apple.quarantine /Applications/CodexIsland.app