Skip to content

TabBeacon v0.8.0

Choose a tag to compare

View all tags
@JerrySkywalker JerrySkywalker released this 30 Sep 16:36
· 30 commits to main since this release
v0.8.0
372637b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

TabBeacon v0.8.0 adds independent per-CLI presentation settings, strict color-only Cursor integration, supported structured Codex state and English/Chinese terminology. Daily commands remain native codex, agy and agent.

Published from authorized source 11d5596ff27f7b7422de773dd8767ad5c347dede. Tag v0.8.0 points to protected merge 372637bdbc95e2fd5456f91d7b78a5ae1b3ebcfc, whose content tree is exactly equivalent. Exact-candidate CI, package verification and independent focused release review passed.

Provider and evidence limits

  • Codex admission remains capability-based. Observed 0.159.0 has the 11-event baseline; it does not inherit separately qualified 0.157.1 Interrupt evidence. In the audited 0.157.1 original-command path, Warning/Failed/original HTTP404 lack authoritative signals and may leave stale tab state. Issue #116 remains OPEN_KNOWN_LIMITATION, not detection PASS.
  • Agy preserves exact 1.1.19 and narrowly admits exact 1.2.7 title-callback contract, authenticated real Working/default-color/mixed noninterference, separately scoped isolated setup/reconcile/uninstall/restore/drift safety, and deterministic delivered-idle to Ready mapping. Real visible Ready remains UNPROVEN. Attended preserve-native switching and same-tab handoff remain NOT_EXECUTED_OWNER_STOP, outside this release's qualified public promise. No 1.2.13 admission.
  • Cursor uses exact-owned project Hooks and strict color-only operation with its native title. Owner-accepted mixed lifecycle/noninterference evidence remains scoped to its actual observations; no new daily Cursor deployment is implied.

Install and upgrade

The official crates.io 0.8.0 package is published:

cargo install tabbeacon --version 0.8.0 --locked

Existing managed Codex installations require ownership-aware tabbeacon setup codex, normal manual Hook trust review where requested, Doctor and applicable runtime verification. Preserve preferences, authentication, third-party Hooks and MCP configuration. See attached upgrade and support materials.

The Windows x64 ZIP, checksum sidecars, verified source crate, MIT license, 247-dependency declared-license inventory and source/build provenance are attached. SHA256SUMS.txt covers release material. ZIP BUILD.txt is the frozen qualification preparation receipt; RELEASE-PROVENANCE.txt records public source/tag/package identity. No private runtime state, authentication or local configuration is included.

Assets 14
Loading