TPS report falls back to Claude Code when no API key is present - stop paying per run for work a subscription already covers

October 1, 2026 at 3:40 PMtechnicallow

Situation

Ryan TPS GTM summaries failed because the report referenced a hardcoded anthropic-gtm keychain key. Peter found the report was set to API billing rather than an installed Claude Code, kept the existing behavior when the token exists, added a Claude Code fallback when it does not, noted that the current setup pays for every TPS run even when Claude would have done it for free, and pushed the change upstream within about 15 minutes.

Reasoning

Confirmed by Peter. A backwards-compatible fix: do not break the API path, stop requiring it; the hardcoded key was the bug. Cost hygiene consistent with the AI-spend ownership stance. Fixing shared tooling directly and contributing upstream rather than filing it back.

Additional Context

Commit fe6360a in this repo.

Observed Evidence

Root-cause message, fallback decision, pushed upstream.

Matching Patterns

30%

Time Over Cost(partial)

Confidence Breakdown

33/35

Evidence

10/30

Pattern

19/20

Source

12/15

Corroboration

Reasoning Depth Analysis

Org Signal:Shared tooling should not create unaware spend

Who Affected:Anyone running the TPS report

Precedent:Prefer subscription-backed Claude Code over API billing for internal tooling

Consequences:Lower per-run cost; no key required

Timing:Ryan report failure

People Involved

Ryan Smith

Source

reflection

AI Confidence

74%

Related Context

💬

DM with Ryan Smith

slack

I will have it continue working as it does today, but fall back to claude code if that token is not present... we pay for every run of a tps report.

Outcome

No outcome recorded yet.

Decision ID: eed17dce-7ae9-4ba4-8640-507e5fd3997b