Skip to content

Pet Halo 0.1.0 Beta 3 — Unsigned Developer Preview

Choose a tag to compare

@github-actions github-actions released this 25 Jul 15:03
e8480a0

Pet Halo 0.1.0 Beta 3

Pet Halo is an independent, unofficial macOS companion for Codex. Beta 3
improves compatibility with the current Codex Desktop Pet surfaces, restores
centered placement across Hide/Wake, and makes the Pet Ring fail closed when no
truthful live inner-ring metric is available.

Highlights

  • Pet discovery handles the current multi-surface Codex Desktop topology with a
    deterministic largest-SystemDialog policy and still rejects tied largest
    candidates.
  • Hide/Wake restores the saved visual-center placement immediately, without
    waiting for a new task activity event.
  • The Pet Ring presents Weekly remaining and an optional exact 300-minute 5h
    window. The former Today ring is removed.
  • Wide Accessibility geometry may choose only the shared arc opening. It is not
    exposed as Live Activity because the same surfaces persist while Codex is idle.
  • The inner slot remains hidden and reserved for a future exact Context
    Remaining source. Expanded fallback cards retain their capability-gated
    Account Usage details.
  • Public README previews now show the current Weekly-only presentation.

Requirements

  • macOS 14.0 or later on Apple silicon or Intel.
  • Supported Codex CLI and Desktop versions listed in docs/COMPATIBILITY.md.
  • Accessibility permission only when following is enabled.

Distribution boundary

This is Beta software distributed as an Unsigned Developer Preview. The
manually gated GitHub workflow publishes it only from reviewed main, with the
new v0.1.0-beta.3 tag and bundle build 3, after the unsigned artifact,
manifest, release notes, checksums, and source commit pass validation.

Pet-Halo-0.1.0-beta.3-unsigned-universal.zip is not signed with a Developer ID
certificate and is not notarized by Apple. macOS may block its first launch.
Verify SHA256SUMS, the GitHub source, and repository provenance before deciding
whether to override Gatekeeper. A future signed/notarized artifact must use a
new tag and build number; it must not replace this release.