Your Quotas. Your Data Flow.

CodeCaps can read quota information on your Mac, send those readings to a server you choose, and display readings fetched from a server.  These are separate choices.

No collector server is required for local Mac monitoring.  CodeCaps does not create a shared server or a public feed for you.

Choose a Setup

Push uploads the local readings; it does not forward downloaded readings back to the server.  Turning off local collection leaves nothing new to upload.

“Local only” means no collector sync.  Some local readers contact their provider to retrieve current quotas using an existing signed-in session, and app update checks are separate.  Turning off push and pull is not an app-wide network firewall.

Set Up CodeCaps on Mac

1. Choose Local Sources

Open CodeCaps Settings → Sources.  Turn Read Quotas From This Mac on to use supported local sign-ins.  Sign in through the provider’s own app or CLI first; CodeCaps does not need you to paste a provider API key.

If a source asks for access, use its explicit authorization action in CodeCaps.  An unavailable or signed-out source is not evidence of zero remaining quota.

2. Optionally Upload Readings

1. Obtain an ingest endpoint and ingest token from your server administrator.
2. Enable Push Quotas to a Server.
3. Enter the Ingest Endpoint and Ingest Token, and select the matching Payload Format.
4. Choose Save & Push Now and confirm a successful result and updated push time.

A compatible Usage Monitor ingest URL commonly ends in /api/ingest/usage.  Generic webhook mode requires a receiver that understands the CodeCaps JSON payload; an arbitrary website URL will not work.

3. Optionally Download Readings

1. Obtain a quota read endpoint and a read token from your server administrator.
2. Enable Show Other Machines’ Quotas.
3. Enter the Quota Endpoint and Read Token.
4. Choose Save & Fetch Now and confirm a successful fetch.

A compatible Usage Monitor read URL commonly ends in /api/quota-windows.  A read URL is different from an ingest URL.  Uploading data does not automatically enable downloading it.

Change Your Mind at Any Time

Turn each switch off independently to stop that activity.  Use Forget Ingest Token or Forget Read Token when you also want the saved credential removed.  Disabling sync does not erase readings already stored on your server; manage retention there.

iPhone, iPad, and Native Widgets

An iPhone cannot read the signed-in CLI sessions on your Mac.  To display those readings on iOS, keep a Mac or another collector publishing to a compatible server, then enter the server’s quota read URL under Mac Sync Endpoint and its read credential as the Sync Bearer Token in the companion’s Settings.

Leave the companion endpoint empty if you do not want it fetching data.  Previously cached readings may still be visible; their timestamps determine whether they are current.

Native widgets display dated quota snapshots from their containing app.  On Mac, keep CodeCaps running and confirm a successful refresh before adding its widget from the system widget gallery.  The Mac app writes a dedicated widget cache after local reads or server pulls; turning local readers off does not prevent a configured server pull from reaching the widget.

On iOS, add CodeCaps from the Home Screen widget gallery.  The companion caches pulled readings, and its widget may make an HTTPS pull when a sync endpoint is configured.  With no endpoint, the widget makes no network request.  A failed pull leaves the previous reading and its timestamp in place.

Widgets do not log in to providers or configure a server for you.  The operating system schedules widget timelines, so a widget may update later than its app.  An empty widget means no usable reading is available to it; it does not mean your quota is exhausted.

What Is Shared?

Quota payloads contain supported provider and window identifiers, quota percentages, reset and observation timestamps, and optional machine labels or identifiers.  They are not conversation transcripts.  Provider login credentials are not included in quota uploads.

Connection tokens are credentials for your server.  Keep them out of public pages, screenshots, browser-side embed code, and shared links.  Use HTTPS and separate read and ingest credentials where your server supports them.

“Push quotas” means an HTTP data upload.  Reset alerts, notification sounds, and cross-device push notifications are separate features; enabling uploads does not automatically deliver alerts to another device.

Troubleshooting