Skip to content

Releases: ashlrai/phantom

Phantom 3.29.15

Choose a tag to compare

@masonwyatt23 masonwyatt23 released this 14 Oct 00:10

Phantom 3.29.15

Resource views

  • Group resources by provider, with separate counts for configured references, current readings and stale or unconfirmed resources. Unknown account identities, coverage and balances remain unknown; quotas and currencies stay separate.
  • Preserve original quota and credit expiry across cards, provider groups and usage views. Connection checks cannot renew retained readings.
  • Keep resource rows and controls available when optional grouping fails.

Local collaboration and safeguards

  • Add local team claims, handoffs and scoped shared context, plus task context ranked by evidence. Preserve human ownership and approval boundaries after agent activity.
  • Keep context replacements within the same owner, project and person scope.
  • Add steward disk and session-retention planning, with dry run by default. Explicit changes stay within documented roots and actions, refuse symlink paths and observed replacements, and preserve existing archives.
  • Prepare self-improvement draft PRs in unique owned worktrees. Private or unverified GitHub evidence stays withheld, public titles are scrubbed, drafts go through the existing protected approval process, and automatic merging remains held.

Test efficiency

Remove seven redundant Git processes from qualified hosted test fixture setup. Three alternating local macOS comparisons measured a median of 208.3→169.7 ms, about 19% faster fixture setup, with all verification commands retained. Whole CI speedup remains unmeasured.

Team approval, standing authority, provider qualification and full-time runtime acceptance retain their separate gates.

Phantom 3.29.14

Choose a tag to compare

@masonwyatt23 masonwyatt23 released this 13 Oct 17:14

Phantom 3.29.14

Workbench

  • Reduce file-finder scoring overhead while preserving match scores, result order and existing performance limits.

  • Keep shared tasks, scoped handoffs, reports and independent review in the existing agent workbench.

  • Find completed and archived agents in Done history, and start onboarding with a bounded change, inspected diff and real tests.

  • See stale fleet data and individual launch results clearly, with retries limited to attempts known not to have started.

  • See failed, partial and blocked run outcomes clearly, with output replay across reconnects and explicit gaps when replay is unavailable.

  • Discover paginated MCP tool inventories and refuse ambiguous tool routes.

Resources and resident operation

  • Handle normal atomic resource-ledger replacement during reads with a bounded fresh read, while retaining strict custody and validation checks.

  • Read supported Devin organization dashboard usage, balance and auto-reload status in an isolated desktop account window. Observations expire after two minutes; individual account identity remains unverified. External sign-in flows are unsupported in this window, and no observation authorizes spending.

  • Opt into resident sleep prevention on Mac. Settings shows saved preference, installed preference and running service separately; saving alone does not start or restart the service.

  • Enjoy Ash's finite coffee animation after the resident is confirmed running with awake enabled. It respects reduced motion; decorative replay is not proof of resident work.

  • Review and apply offline native pool enrollment with an explicit plan digest, or resume an existing journaled transaction. History, policy, receipts and operator holds are preserved; enrollment does not establish provider identity or authorize dispatch.

  • Distinguish available credits from spending authorization and retain the signed metered budget on Devin API launches.

  • Honor native usage's original expiry across account cards, meters and seat selection, including failed refreshes and cached data; retain expired readings as unconfirmed history.

  • Report native quota failures accurately, preserving recovery evidence when a launch's termination is uncertain.

Mac update

Use the signed Mac archive and paired package from this release. The update requires a drained, closed application; a changed authority surface may require Touch ID reapproval. Resident sleep prevention requests idle sleep prevention, plus system sleep prevention on AC power; it does not override closing the lid or explicit Sleep.

Embedded Devin authentication, current provider readings and successful resident work must be verified on the installed Mac. Subscription eligibility, API credits and cash billing are separate resource boundaries.

Phantom 3.29.13

Choose a tag to compare

@masonwyatt23 masonwyatt23 released this 12 Oct 19:51

Phantom 3.29.13

  • Repair native quota launch handoff and hold installation while collector ownership is unresolved.
  • Bound Qwen3.8 Leader streaming and preserve its structured memo output budget.
  • Deduplicate Leader work by goal milestone; decode qualified local outcomes.
  • Support an explicitly selected, measured loopback llama-server for Fleet.
  • Select a verified Devin organization member and verify session attribution; this does not establish an included allowance or cash boundary.
  • Label historical quota honestly and expose sanitized native/Claude diagnostic stages.
  • Hold autonomous native Codex calls without current exact-account subscription-only billing proof. The current quota feed cannot supply that proof; manual Verse chats remain a separate path.

Built from the exact candidate below after full hosted CI, Merge Gate, dependency audit and protected-master attestation. Paired app/CLI artifacts and manifest are signed. Existing unresolved collector ownership requires supported recovery before installation. Authority code changes may require operator reapproval.

Source: b0e0047ef3bc5e15f9a9431213c40b9c99f42c1d.

Phantom 3.29.12

Choose a tag to compare

@masonwyatt23 masonwyatt23 released this 12 Oct 07:48

Phantom 3.29.12 is a paired CLI and macOS app release from candidate 0982f4b.

  • Explain why a connected Claude account has no current quota reading without treating unknown usage as zero or exposing native provider output.
  • Clarify that the resident USD ceiling is secondary to signed metered authority. A zero daemon ceiling stops all resident work, including subscription and local work.
  • Make the macOS broker tamper fixture perform an in-place authenticated-byte mutation while preserving strict fail-closed and rollback assertions.

The original CI build and npm archive passed full hosted Merge Gate, independent Dependency Audit, protected-master attestation, and canonical npm provenance and clean consumer checks. The macOS app archive and update manifest were built and signed locally from that verified source. The app is signed and not notarized.

Installation, resident grant approval, and provider quota readings are separate from these published assets. Claude quota remains unverified until the native collector returns a current reading.

Phantom 3.29.11

Choose a tag to compare

@masonwyatt23 masonwyatt23 released this 12 Oct 01:58

Phantom 3.29.11 makes new macOS native resource profiles resilient to device-number changes after reboot. The launcher verifies a witnessed APFS volume, directory identity, and boot before using a profile. An explicit phm resources profile upgrade-identity command upgrades an unchanged older profile while it is still on the same boot. Profiles that already drifted remain fail closed and require a new profile and native sign-in.

  • Accept current GitHub ruleset transport fields during protected-branch attestation without weakening its policy checks.
  • Allow only the fixed system identity probes needed by witnessed profiles inside Claude's native sandbox.
  • Pass the exact-source platform Merge Gate and independent dependency audit.

The npm package is the original attested CI archive, published through the canonical OIDC workflow with provenance and an isolated consumer check. The Apple silicon app and CLI assets are paired and locally signed with the included manifest. The Mac app is not notarized.

Install the CLI with npm install -g @ashlr/phantom@3.29.11. Publication does not restart the resident fleet or reauthorize standing grants; those are separate Mac operations.

Phantom 3.29.10

Choose a tag to compare

@masonwyatt23 masonwyatt23 released this 10 Oct 22:56

Phantom 3.29.10 improves local fleet readiness and judge accountability while keeping standing authority fail closed.

  • Check the exact configured model on a local engine's loopback /models endpoint before reporting it ready. The bounded probe works in the installed single-file sidecar. A model listing establishes availability, not a successful completion.
  • Record judge launch refusal separately from an invalid judge verdict. If a standing Codex seat lacks a reviewed pin, keep it ineligible and use another admitted independent judge family when available.
  • Bind the public release facts reader to the candidate's complete CI job inventory while retaining all 15 release authority gates.
  • Remove stale fixed 3.26 labels from the Verse landing-page story and footer. The installation link resolves the promoted npm release.

The npm package uses the original attested hosted archive. The Apple silicon app and CLI assets are paired, signed locally, and published with a matching manifest. Existing accounts and settings remain compatible.

Install the CLI with npm install -g @ashlr/phantom@3.29.10. New Mac users can preview phm desktop install, then apply it where no app is present. Existing desktop installations should use the signed update path.

Publication does not resume the resident fleet. A current standing grant, Mac authentication, provider availability, and separate spending permissions are required before unattended execution.

Phantom 3.29.9

Choose a tag to compare

@masonwyatt23 masonwyatt23 released this 10 Oct 21:11

Phantom 3.29.9 improves CLI responsiveness and release feedback, and refreshes local-model speed after successful turns.

  • Load doctor, init and setup only when selected. Local compiled Node help/version/resource-help startup measured 32–33 ms, down from 117–118 ms. These are compiled Node measurements; native app startup is measured separately.
  • Run npm run check:release:fast after a normal local build for the existing packaging/workflow contracts and release checks. The local run passed 380 Node and 220 Vitest cases in about 20 seconds, with one existing intentional skip. Full platform qualification remains separate.
  • Reduce test-worker setup work and load only the selected package smoke command. The complete local 38-case package comparison ran about 6% faster; hosted gains are not attributed to this measurement.
  • Start short Mac checks after isolated tests finish so they can overlap general partitions. All 15 platform release gates remain required.
  • Remove a duplicate walk over the captured release archive while preserving fresh signature, source and original-byte checks.
  • Refresh observed local-model speed when a successful local turn completes, including when an older context read is pending. Streaming chunks and duplicate events do not add reads.
  • Keep cached sign-in expiry warnings from incorrectly claiming the native CLI has signed out.

The release uses the original hosted npm tarball, trusted npm publication, and matching signed Apple silicon app and CLI artifacts. Existing accounts and settings remain compatible.

Install the CLI with npm install -g @ashlr/phantom@3.29.9. New Mac users can preview phm desktop install, then use phm desktop install --apply when the app location is absent. Existing desktop installations use the signed update path.

Runtime recovery is separate from publication: a held legacy collector record still requires a normal Mac restart, followed by physical authentication of the unchanged grant. Unknown provider balances and purchased-credit exclusions stay in effect.

Phantom 3.29.8

Choose a tag to compare

@masonwyatt23 masonwyatt23 released this 10 Oct 19:43
6a73145

Phantom 3.29.8 improves resource accuracy, chat refreshes and installation.

  • Install the signed Apple silicon desktop app with phm desktop install, without a local compiler or publisher key.
  • Keep newer chat activity when an older snapshot arrives; load resize controls separately while preserving saved widths.
  • Preserve unknown provider usage, and display resource metrics to two significant figures.
  • Honor the original metadata-process deadline when a timer wakes early.
  • Keep uncertain release-article writes held while allowing retries after a confirmed refusal without persistence.
  • Refresh current Leader, installation and ecosystem documentation.

Canonical package: @ashlr/phantom. Workbench: https://phm.dev. Secrets: https://phm.dev/secrets.

For installations already holding an incomplete legacy collector record, a normal Mac restart is still needed to recover live usage collection. Installation and standing-grant renewal are separate steps.

Phantom 3.29.7

Choose a tag to compare

@masonwyatt23 masonwyatt23 released this 10 Oct 05:08

Phantom 3.29.7 improves resource history, release downloads and optional repository qualification.

  • Record Claude promotional API credits separately from subscription usage. Unbound history remains held for spending.
  • Keep historical resource readings tied to their reported origins.
  • Provide canonical signed Mac app archive links when a DMG is unavailable.
  • Restore recovery of signed historical remote handoffs without weakening PR-only merge rules.
  • Add default-off test timing calibration and a Mac scheduling pilot for measuring future CI improvements.

The package and desktop assets use the original qualified CI build. Installation preserves accounts and existing data. Live collector recovery on affected Macs still requires a normal restart; fleet authorization remains a separate runtime step.

Phantom 3.29.6

Choose a tag to compare

@masonwyatt23 masonwyatt23 released this 10 Oct 01:28

Phantom 3.29.6 improves resource visibility and runtime recovery.

  • Collapse the resource sidebar while retaining account usage, credit balances and hover details. Grok Build and Grok Bot remain separate usage pools.
  • Keep the Fleet page stable when refreshes overlap.
  • Record collector identity before execution and add a signed desktop launcher and installed-pair self-check.
  • Dispatch Outcome Manager tasks into the admitted workspace.
  • Distinguish reported tokens, estimates, reservations and unknown usage in measurements.
  • Bind website staging to its qualified source and verify the exact Vercel deployment before promotion.
  • Consolidate release guidance and collect CI phase timings.

These changes preserve existing accounts and spending settings. An older incomplete collector record can still hold quota refresh until its process lifecycle is proved settled; this release does not manufacture missing readings. Website publisher activation and protected-remote fleet merge qualification remain separate operational steps.