AI Tool
AI Usage
Claude Code + Codex usage on your Mac, iPhone, and Apple Watch.
- Type
- AI Tool
- Platforms
- macOS, iOS
- Status
- Live
- Role
- Design + engineering
The story
Why it exists
Claude Code and Codex expose usage in separate web surfaces, making it hard to know which limit is approaching while working.
My role
Independent product designer and engineer across macOS, iPhone, Apple Watch, WidgetKit, and CloudKit.
Product move
Use the Mac as the trusted data source, then publish one private CloudKit snapshot to read-only phone, watch, widget, and complication surfaces.
What shipped
A signed and notarized Apple ecosystem app with live plan data, three widget sizes, automatic authentication, and private cross-device state.
See the product
Product judgment
Key decisions
- 01
The Mac is the source of truth
Credentials stay on the computer. Phone and watch clients receive only a private usage snapshot.
- 02
Show real limits, not estimates
The app reads provider plan data and excludes cache rereads so the trend line reflects new-token volume.
- 03
Design one system for four surfaces
Host app, desktop widget, phone widget, and watch complications share the same hierarchy at different densities.
Build notes
An embedded WKWebView captures the Claude session cookie into Keychain. Codex authentication is detected from the local CLI session.
The notarized macOS host publishes a single latest record to private CloudKit. Companion devices are read-only and retain a last-good cache.
Built withSwift, SwiftUI, WidgetKit, macOS, iOS, watchOS, CloudKit, WKWebView, Keychain Services, XcodeGen
