Documentation for source version 1.6.0. A local build does not confirm that this version is published in the Chrome Web Store.
Your day, at a glance
GPTandME counts prompts you send on supported browser chat sites. Open the popup to see today's total, your week and month, and your all-time history. A seven-day chart makes your recent activity easy to read, and a service breakdown shows where your prompts went.
- Today's count in the toolbar badge and an optional in-page counter.
- Today, calendar week, calendar month, and all-time prompt totals.
- A seven-day chart and today/all-time counts by service.
- Settings, diagnostics, and data controls tucked into expandable sections.
- Complete JSON backup/restore and dated-count CSV export/import.
A more focused counter
Version 1.6.0 removes API cost estimates, thinking-time displays, and the session, streak, last-24-hours, and model-breakdown panels. The updated page script no longer captures thinking time. Existing counts and legacy timing, model, hourly, and session data remain in JSON backups. Reload already-open chat tabs after updating.
Supported services
Count prompts on ChatGPT, Claude, Gemini, Perplexity, and optionally Grok. Turn on Grok access in settings and reload existing Grok tabs to start counting there. Chrome/Chromium 111 or newer is required.
Only new sends are counted; historical conversations are not backfilled. GPTandME does not count Claude Code, native desktop apps, command-line tools, direct provider API clients, or Chrome Incognito activity.
ChatGPT, Claude, Perplexity, and Grok counts come from recognized outgoing user-send requests; Gemini uses send activity in its primary page composer. Counts record submissions, not successful responses. Detection can miss sends when a provider changes its request endpoint or composer, and an extension update may be needed.
Your history stays with you
GPTandME needs no account and sends no usage data to a server. Counts, settings, and diagnostics stay in your browser. It does not store prompt text, response text, raw thinking labels, raw timing samples, or full conversation URL paths.
A JSON backup preserves the complete local dataset and replaces current data when restored. CSV contains prompt counts only; imports add counts, so importing a file twice duplicates them. Use JSON when moving your complete history.