I wanted seat quota and cooldown timers on an iPhone home screen. The meter already collects everything needed, so I ended up decoding Application Support/AgenticUsageMeter/state.json with a bridge script (Apple-reference-date timestamps, the [UUID: UsageSnapshot] dict flattened to an alternating key/value array), publishing a small JSON document to a token-gated Cloudflare Worker every 5 minutes, and rendering it with a Scriptable widget. It works well.
It would be simpler — and less coupled to Swift JSONEncoder internals — if the meter offered a supported export. Either shape would do:
- a CLI/scriptable dump: print the current snapshots as plain JSON (Unix epochs, named fields), or
- a setting: "also write snapshot JSON to this folder on every poll".
One hook like that lets people build phone widgets, dashboards, and cross-machine views without touching the app, and it would insulate downstream readers if the Tauri rewrite changes the internal state format.
Happy to PR the file-export option if you'd take it — any preference on shape?
I wanted seat quota and cooldown timers on an iPhone home screen. The meter already collects everything needed, so I ended up decoding
Application Support/AgenticUsageMeter/state.jsonwith a bridge script (Apple-reference-date timestamps, the[UUID: UsageSnapshot]dict flattened to an alternating key/value array), publishing a small JSON document to a token-gated Cloudflare Worker every 5 minutes, and rendering it with a Scriptable widget. It works well.It would be simpler — and less coupled to Swift JSONEncoder internals — if the meter offered a supported export. Either shape would do:
One hook like that lets people build phone widgets, dashboards, and cross-machine views without touching the app, and it would insulate downstream readers if the Tauri rewrite changes the internal state format.
Happy to PR the file-export option if you'd take it — any preference on shape?