The briefingAgentic AI
Loading Ashlr Brief
On October 12, Phantom merged its 3.29.12 and 3.29.13 releases, and Phantom Secrets closed a race in device approval expiry.
On October 12, 2026 (UTC), Ashlr merged pull requests for two Phantom releases. These are Ashlr's own descriptions of its own work.
The first was 3.29.12. Its main change explains why a Claude quota reading is missing. The pull request says the app now carries a reviewed, non-sensitive failure code only when the current quota meter is absent, and explains it in the Apps and Accounts screen and the Resources drawer. It keeps sign-in state and quota state separate. It says the release does not claim a verified Claude quota reading.
The second was 3.29.13. The description says Phantom could leave usage collection stuck when a signed helper process exited before reporting its identity. The fix records the identity earlier and refuses to install the app over unresolved collection work. It also covers the Leader, the part that plans work: its memo step now finishes its thinking before it answers and has a fixed size limit on streamed data. It lets an allowed local model server run Fleet work alongside subscriptions. The description says no live configuration is changed by the pull request.
Earlier that day a pull request made new Mac profiles survive macOS renumbering a disk. It adds a stable volume identity check. The description is clear about the limit: it detects replacement and one-file edits, and it is not protection against a malicious process running as the same user.
Separately, Phantom Secrets fixed a timing gap in device approval. A sign-in code could expire while an approval was waiting for a database lock. The fix checks the deadline at the moment the database changes the row. The description says an already-issued CLI token stays valid when its short device code expires. No hosted database or live site was changed by that pull request.
When a check can go stale while it waits, run it at the moment of the change. The device approval fix does that inside the database, so no application clock can be out of date.
A missing number is better explained than hidden. The quota change shows a reason for the missing reading and says plainly that it does not repair it.
Open the 3.29.12 pull request and read the Boundaries section. It lists what the release does not do, which is the part most product pages leave out.
Ashlr tools connected to this story. Review their source and setup requirements.
Work with eligible coding-agent accounts and local models in one workbench; review fleet proposals under signed authority.
Source material behind this briefing. Our practical implications are Ashlr’s interpretation.
This briefing was prepared with AI assistance from the linked sources. The analysis may include interpretation; consult the original sources for complete context. Cover artwork is illustrative.
A plain-English guide to Phantom: what it is, what Work with me and Work for me mean, what Leader and Manager do, and a safe first 15 minutes.
"Deep autonomy" is our label for agents working unattended under a signed grant. Phantom's README calls it autonomy with custody. Here is what it covers.
On October 16 and 17, Phantom merged first-run fixes, renamed Verse to Phantom in user-facing text, sped up the app, and added a one-gateway guide.
Delegate supported API work through scoped placeholders and a local proxy, keeping real keys out of agent context.
