What is running, what it costs, and what to change.
GitDoctor reads the runtime — scheduled loops, function calls, queues, keys, and the model bill — not your code. Connect a provider and in thirty seconds you get one sentence like the one below, a list of what needs a look, and a reversible fix for each. Nothing is installed, nothing is stored, nothing is changed until you say so.
Why try it
Because nobody looks after the loops. Sweepers, drains, nightly jobs, and cron workflows get written once and run forever. On the first real account we read, three of them had been firing 360 times a day into empty queues since July, and a nightly pipeline had failed every one of its 179 runs since March. Nobody knew. That's not carelessness; it's that no dashboard shows it.
Because the model bill is a black box. A usage export nobody downloads, on a key nobody can attribute to a project. GitDoctor pulls it, shows where the money goes, and names what's on the table — with the assumptions stated, and the provider's own cost report as the cross-check.
Because every fix is one reversible line. Pause, never delete. Plan before apply. An undo for everything. The engine is a command-line tool you can run yourself, and a downloaded snapshot reproduces every number on this site.
From a real account, read once
One loop in storefront-clone runs 360 times a day into an empty queue. daily-news-pipeline in news-digest has failed every run since 2026-03-09 (179 of 179).
- storefront-clone / intake-sweeper — IDLE: runs ~360×/day; intake_items has 0 pending and no rows touched in 7 days (0 total) — spinning fix
- news-digest / daily-news-pipeline — FAILING: has failed every run since 2026-03-09 (179 of 179); last error: ERROR: schema "net" does not exist; function logged 1 errors in 24h fix
- One model key (ANTHROPIC_API_KEY) is shared by 3 projects: crm, storefront, storefront-clone. Their usage lands on a single line in the provider console, so a bill can't be traced back to a project. One key per project fixes that.
- 1 other credentials are shared across storefront, storefront-clone — EBAY_CLIENT_SECRET. Usually intentional between clones (the same marketplace or supplier account); worth knowing because rotating one means rotating it everywhere at once.
