ai-overflow
v1.0.6
Published
The CLI collects your local agent usage through Codeburn and uploads a sanitized report to https://aioverflow.prathadox.com. Node.js 22.13 or later is required.
Readme
AI Overflow
The CLI collects your local agent usage through Codeburn and uploads a sanitized report to https://aioverflow.prathadox.com. Node.js 22.13 or later is required.
Connect and upload
Run this command from any folder:
npx ai-overflowApprove the device in your browser. Complete the GitHub connection and profile setup in the same wizard.
The CLI saves your login locally. Later runs reuse that login.
Manual uploads request an efficiency analysis, subject to the daily limit.
The npm installation prompt is normal. The --yes flag is optional.
Automatic updates
After your first successful upload, macOS and Linux enable local 15-minute usage sync automatically.
npx ai-overflow --no-auto-syncUse npx ai-overflow --auto-sync to enable it again after opting out.
The local scheduler uploads usage totals every 15 minutes while your computer is awake and your user session is active.
Background updates never open a browser or request AI analysis.
The profile shows the latest usage separately from the last completed analysis.
Check the scheduler:
npx ai-overflow --sync-statusAutomatic updates use launchd on macOS or a systemd user timer on Linux. Windows supports manual uploads only. The scheduler keeps a pinned CLI installation outside the npx cache. Your login remains after you stop automatic updates. The current version stores the latest snapshot from one computer. It does not combine usage from multiple computers.
For a totals-only upload without AI analysis, run:
npx ai-overflow --syncThis command requires a saved login. If the login expires, run npx ai-overflow to reconnect.
Local development
Keep local and production logins in separate config files:
npm run build:cli
node dist/cli/index.js --base-url http://localhost:3001 --config-file /tmp/ai-overflow-local-cli.jsonFor local automatic updates, use the same --base-url and --config-file arguments.
The local server must be running. Automatic installation requires a published CLI version.
Use --dry-run to inspect the sanitized report without an upload.
Use --help to see all commands.
Database upgrade
Before deployment, apply each migration to the intended database in order:
npm run db:migrate
npm run db:migrate-profile
npm run db:migrate-usage
npm run db:migrate-trustExisting installations with migrations 001 and 002 should run db:migrate-usage and then db:migrate-trust.
These migrations add totals, consent, and public GitHub activity cache fields without deleting accounts or analysis history.
