
Phantom 3.29.13: when a quota is unknown, say so
Phantom 3.29.11 to 3.29.13 stop treating unknown usage as zero and hold some unattended runs without billing proof. These are Ashlr releases.
This briefing covers a release from Ashlr’s own developer-tool projects. Product claims come from the linked sources; this is not an independent review.
What changed
Phantom is our workbench for coding agents. Three releases landed on October 12, 2026: 3.29.11, 3.29.12 and 3.29.13. Their notes share a theme. When Phantom does not know something, it should say so and not guess.
Release 3.29.12 explains why a connected Claude account has no current quota reading. It does not treat unknown usage as zero, and it does not expose raw output from the provider. It also clarifies that the resident dollar ceiling is secondary to the signed metered authority. A zero ceiling stops all resident work, including subscription and local work.


