TabBeacon v0.9.0

TabBeacon v0.9.0 — bounded public source and Windows x64 artifact release.

Frozen source: 62e1cefac25ffcb71d00a9ea910de803eebb4b58. This release absorbs the previously unreleased v0.8.2 candidate; v0.8.1 is the prior official release. The original package and ZIP documents retain prepublication “Unreleased” / candidate wording. That known documentation limitation was accepted for v0.9.0; these external notes do not alter the shipped bytes.

Source/material/existing-CI review uses the Owner-accepted, one-release R1-AB-090-v1 A+B alternative. Independent native review remains BLOCKED. Train D records two Owner PASS and eighteen SKIP. Optical P95/100 ms, DEC modes, current real Provider, actual terminal/Shell restoration, strict arbitrary OS-stall exit, installed migration and production rollback remain UNPROVEN. Strong arbitrary foreign-writer CAS and cross-file crash atomicity are unsupported. The historical 700 ms failure with unresolved cause and older 24-byte EXE reproducibility failure remain preserved.

这是限定范围的源码和发行资产发布。包内旧的“Unreleased”/候选文案保持原样；不宣称已完成上述真人、终端、Provider、安装或回滚资格。实际安装、Hook 协调和原生手工 trust 需要另行授权。

Verify tabbeacon-0.9.0-windows-x64.zip with SHA256SUMS.txt and RELEASE-PROVENANCE.json. The ZIP contains the unchanged raw Windows EXE; the three TUC dependencies are already public and are not republished.

TabBeacon v0.8.1 — Codex Windows Hook console compatibility

TabBeacon v0.8.1

Candidate: 436ea8d643a880c7b537353e85176108c17c060a.
The Owner authorized publication of this exact candidate on 2026-10-10.
Merged source: a76ed15e758debf6b1635406bd03001695b58bdd; the merged tree exactly matches the authorized candidate. Tag: v0.8.1.

Fix Windows Hook presentation when the native Codex background command launcher
loses its originating console association. TabBeacon recovers only the proven
installed native Codex ancestor's console, retaining redirected Hook stdio,
bounded process ownership, worker cleanup and fail-open suppression. Daily agent
launch remains literally codex.

Windows command Hooks declare a two-second timeout, based on measured startup
tails after console recovery. Unix commands and historical MCP retain one second.
Configuration writes require a complete known generated owned declaration set;
third-party content is preserved and new Hook hashes require manual native /hooks
review. Installation or reconciliation must not automatically grant trust.

The release CI now requires an actually executed, qualified release-only Hook SLA
test. The final exact-head Windows CI ran one test and measured 153 ms against the
generated two-second declaration. This anchored COMSPEC measurement is separate
from real provider delivery and the historical sub-one-second performance target.

On 2026-10-10 the Owner completed one isolated attended native Codex 0.162.0 test
in Windows Terminal: manual Hook review, working green, tool activity green,
completion blue, no Hook timeout and normal exit/reset all passed. Native exit was
0; candidate binary, native entry/launcher/executable and Hook declarations matched
their admitted identities. All 11 isolated review hashes match the declarations.
The isolated config changed only through manual Hook trust and the native TUI
screen-reader-detection flag; its remaining bytes match the pre-review baseline.

This qualifies the current native 0.162.0 Windows Terminal path on the attended
host. It does not claim attended 0.159.2 delivery, repair arbitrary missing-worker
cold overhead, or guarantee latency on every host. The historical original
one-second timeout's precise causal phase remains UNPROVEN. Earlier synthetic
launcher evidence retains its synthetic scope.

Product source, dependencies, console ownership and configuration mutation logic
are unchanged from accepted head 20641846d098f9d908ef6858b9a24e5ca5c116da.
The 91 unaffected Hook cases, 440 synthetic launcher calls and independent source /
configuration safety review are reused. The executable is reused with its original
identity; the source crate was freshly verified at the final candidate. No L4,
launcher stress or full CI was repeated for this closeout.

Release artifacts and SHA256:

Artifact	SHA256
tabbeacon-0.8.1.crate	67AC37B1F95EC1A2EF1AB94B7FE5843B9A64BD1B96F083BB922852094C942E4C
tabbeacon-0.8.1-windows-x64.zip	6FAEB187A392494B1DF402F82067F2A3C0516F167276FD572FB74663524DC869
tabbeacon.exe	8BD5C5D884CF026C2B4F0CB19437E29EAE906E56E70A005BF3CE4B4D49368C88

The ZIP includes the executable, LICENSE, README and hotfix scope document. Existing
package bytes and checksums are unchanged; this attended-acceptance addendum is
carried in PR #121 and the closeout receipt without a status-only source commit.

Install from the official channel with cargo install tabbeacon --version 0.8.1 --locked.
Run tabbeacon setup codex for ownership-safe reconciliation, preserving existing presentation preferences and third-party declarations. Review changed Hook declarations manually in native /hooks; installation does not grant trust.

TabBeacon v0.8.0

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.

TabBeacon v0.7.3

TabBeacon v0.7.3 discoverability and distribution polish

v0.7.3 is a public-surface maintenance release. It improves how people find,
understand, preview, and install TabBeacon without changing runtime or provider
behavior.

Codex-led discovery with exact support truth

• The repository description, topics, social-preview assets, and README hero
  lead with Codex and more.
• The adjacent support table remains exact: Codex is production-supported from
  positively established local capabilities, and Agy is production-supported
  only for the admitted 1.1.19 profile.
• Claude Code and OpenCode remain deferred; the positioning phrase does not
  claim otherwise.

Deterministic real-Windows-Terminal demo

The README now shows a privacy-safe 10-second demo rendered by TabBeacon's
production presentation path in one stock Windows Terminal window. The demo
uses only the synthetic aliases API, WEB, and DOCS; it contains no real
model session, desktop capture, Owner identity, private path, private
repository, or unrelated window.

The qualification lifecycle creates an immutable exact-ownership record before
capture and revalidates the unique anchor TabItem, ancestor window, HWND, and
creator process instance before exact close. Ambiguous windows remain untouched,
and broad Windows Terminal termination remains forbidden.

Simpler installation and cleaner package

The normal user path is now:

cargo install tabbeacon
tabbeacon setup
codex

English and Simplified Chinese landing pages retain parity, important media and
links render from the crates.io context, and the crate excludes promo media,
social-preview assets, build evidence, frames, palettes, and FFmpeg binaries.

Unchanged product boundaries

Daily commands remain literal codex and agy. v0.7.3 adds no provider,
wrapper, fake executable, PATH shadow, PTY host, global daemon, Hook-trust
bypass, automatic Owner configuration mutation, or native tab-icon support.

Release status

v0.7.3 was published from release SHA
1485b4dc0fe634a21634adc9ec539deb76beaad2 to crates.io, the immutable
v0.7.3 tag, and the public GitHub Release. The Windows x64 ZIP and sidecar,
the exact locked crates.io install, the default crates.io install, and a fresh
GitHub-asset download were all verified. This public release does not itself
authorize or perform an Owner production-binary or configuration upgrade.

TabBeacon v0.7.2

TabBeacon v0.7.2 Codex subagent Hook stability hotfix

v0.7.2 fixes a Codex Hook stability failure in which child/subagent activity
could interfere with the root tab's presentation and visible Hook failures or
one-second timeouts could appear during a real parent-plus-subagent turn.

Root and subagent isolation

• Child and subagent lifecycle/tool events are identified and ignored before
  they can mutate root presentation state.
• Stop continues to normalize to WaitingUser plus ResultReady. ResultReady now
  remains visible through a bounded static activity-worker lease after the
  one-shot Stop Hook exits.
• Generation, session, workspace, terminal, predecessor, and cleanup ownership
  stay explicit. Worker launch failures remain fail-open.

Exact legacy transport convergence

An installation with the exact TabBeacon-owned historical Codex MCP Hybrid
declarations can converge transactionally to the current command-v1 Hook
transport. Similar, partial, modified, or otherwise ambiguous declarations are
refused rather than guessed.

The migration preserves unrelated third-party Hooks, MCP servers, Codex
configuration, title ownership, and backup/recovery state. When TabBeacon's
managed Hook definitions change, Codex requires a fresh manual /hooks trust
review. v0.7.2 does not bypass or pre-approve that review.

Qualification terminal safety

Active v0.7.2 qualification and visual paths now register each temporary
Windows Terminal window with a unique run ID, fixed anchor TabItem, and exact
ancestor HWND. Cleanup revalidates that complete identity and refuses ambiguous
or mismatched ownership; broad Windows Terminal process/window termination is
forbidden.

Unchanged product boundaries

v0.7.2 adds no provider and no new presentation feature. Daily agent launch
remains literal codex. The release adds no wrapper, fake executable, PATH
shadow, PTY host, global daemon, Hook-trust bypass, or automatic mutation of an
Owner's production Codex configuration or trust state.

TabBeacon v0.7.1

TabBeacon v0.7.1 maintenance closeout

v0.7.1 is a maintenance and closeout release. It improves public brand and
current-truth quality without changing TabBeacon runtime behavior.

Maintained public identity

• Repaired the horizontal TabBeacon SVG wordmark with a deterministic local
  glyph grid. Glyphs use a shared cap height and baseline, bounded cells,
  explicit advances and gaps, and zero overlap.
• Preserved the existing TabBeacon mark, monochrome mark, and state strip.

Current product truth

• Reconciled current-facing Agy and architecture text with the exact admitted
  Agy 1.1.19 production profile while retaining historical qualification and
  release records as history.
• Corrected the governance roadmap's current public-release pointer.
• Kept Codex CLI and Agy CLI 1.1.19 as the only production-supported coding
  agents. Claude Code and OpenCode remain deferred.

Deliberate dogfood pause

After v0.7.1, active feature development is paused for an Owner dogfood/use
period. The v0.8 option set is non-authoritative; no v0.8 roadmap or feature
implementation is created by this release.

Unchanged boundaries

RUNTIME_BEHAVIOR_CHANGED=false
PROVIDER_BEHAVIOR_CHANGED=false
NATIVE_TAB_ICON_DISPOSITION=NO_GO

The release adds no provider, Codex App Server backend, native-tab-icon route,
XAML Diagnostics work, launcher, PATH shadow, PTY host, daemon, timeout tuning,
worker behavior, HookStat integration, or new presentation semantics.

TabBeacon v0.7.0

TabBeacon v0.7.0 release notes

Open-source experience

v0.7.0 gives TabBeacon a clearer public home without changing the literal
coding-agent commands that users run every day.

• An original TabBeacon SVG identity, including a compact mark, horizontal
  logo, monochrome mark, and semantic state strip.
• An English-canonical README and a full Simplified Chinese counterpart, with
  exactly two project-health badges: Rust/MSRV and Windows CI.
• A separate Supported Coding Agents table and a scalable compatibility guide.
• A privacy-safe real Windows Terminal screenshot rendered by TabBeacon's
  deterministic presentation fixture. It is not presented as a live model
  conversation.
• A documentation portal with getting-started, configuration,
  troubleshooting, FAQ, design, build/test, and release-process guides.
• CONTRIBUTING v2 and an offline documentation contract check in Windows CI.

Supported coding agents

Codex CLI remains production-supported with literal daily command codex and
capability-based compatibility. Agy CLI remains production-supported only for
the exact admitted Agy 1.1.19 profile, with literal daily command agy.

Claude Code and OpenCode remain deferred. v0.7.0 adds no third provider and no
Codex App Server backend.

Native Windows Terminal tab icon research

NATIVE_TAB_ICON_DISPOSITION=NO_GO
PRODUCTION_RUNTIME_NATIVE_ICON=false

Stock Windows Terminal still has no supported public application-controlled
native-tab-icon bridge. The remaining documented XAML Diagnostics route is
process instrumentation, and it could not meet the admitted isolated-target
safety bar on the qualified host. No XAML attachment, visual-tree enumeration,
IconSource mutation, snapshot, or restore was attempted.

TitleMarkBackend remains TabBeacon's production visual path. Native tab
icons do not ship in v0.7.0 and this conclusion does not promise a future
integration.

For the detailed evidence, see the research disposition
and ADR 0018.

TabBeacon 0.6.1

TabBeacon 0.6.1 release notes

TabBeacon 0.6.1 is the current public release.

Codex compatibility

Codex setup now selects its conservative command-Hook profile from explicit
local capability evidence. A reported Codex version is diagnostic only; it is
not mutation authority. When Hooks are explicitly available, a fresh setup
uses codex-hooks-command-v1, whose Hook parsing remains forward-compatible
and fail-open for unknown fields.

The profile retains eleven synchronous command-Hook lifecycle declarations,
the one-second fail-open timeout, and manual /hooks trust review. Daily use
remains literal codex; TabBeacon adds no launcher, PATH shadow, PTY wrapper,
or global daemon.

Persistent title and visual identity

Provider Visual Identity v2 carries provider identity into activity workers.
Provider, runtime, and workspace occupy independent title slots, so a worker
keeps the provider identity while workspace identity remains stable.

Persistent Windows title output uses Unicode-wide VT transport. The normal
path does not call SetConsoleTitleW. A newly published worker leaves the
originating Hook to write its first complete frame, while an already-active
worker renders without replacing that title.

Windows worker reliability

Worker and cleanup-observer standard streams are explicitly NUL-backed, but
that alone does not constrain all inherited Windows handles. v0.6.1 also uses
PROC_THREAD_ATTRIBUTE_HANDLE_LIST to allowlist the exact detached handles
passed to those long-lived descendants. OS-level sentinel-pipe and EOF tests
prove they do not retain ambient Codex redirected pipes after a Hook root exits.

The Hook model remains synchronous and fail-open. It does not promise
sub-second completion when Windows PowerShell startup is saturated, and it does
not make all Hooks asynchronous.

Out of scope

This release does not add a native Windows Terminal tab icon, XAML
integration, or Windows Terminal injection.

TabBeacon 0.6.0

TabBeacon 0.6.0 release notes

TabBeacon 0.6.0 adds the first real second provider while preserving literal
agent commands and the provider-neutral core.

Highlights

• Exact Agy 1.1.19 support through its official user-global structured title
  callback.
• Content-minimal Ready/Working projection, stable Root Workspace Anchoring,
  provider-aware Sessions, Integrations, and Why this title?.
• Compact provider badges with auto, always, and off policy.
• Ownership-safe Agy setup, migration, drift refusal, and uninstall.
• Codex and Agy session/root/config namespaces remain isolated while sharing
  the same workspace alias registry.

Daily workflows

Codex-only:

tabbeacon setup codex
codex

Agy-only:

tabbeacon setup agy
agy

Both providers can run concurrently in stock Windows Terminal. TabBeacon adds
no launcher, agent wrapper, PATH shadow, PTY host, or global daemon.

Capability boundary

Codex retains its admitted Hook-backed lifecycle and Windows Terminal
presentation. Agy contributes only the facts proven from Agy 1.1.19: stable
conversation identity, equal current/project workspace root, Ready from
idle, Working from initializing/working, and plain title output. Agy tab
color, WT progress, animation, approval, result-ready, stop authority, health,
and background-task count are not claimed.

See Agy setup and the upgrade guide.

TabBeacon v0.5.2

[0.5.2] - 2026-08-23

Added

• Added the high-performance Codex 0.149 runtime: a Root Workspace Fast
  Anchor Path keeps normal post-anchor events at zero Git subprocesses, with
  a release-mode one-second regression gate.
• Added the Codex 0.149 hybrid transport: ten normal lifecycle Hooks use the
  session-scoped TabBeacon stdio MCP server, which alone receives
  WT_SESSION; only SessionEnd remains a command Hook.
• Added authoritative SessionEnd cleanup for activity, Windows Terminal
  progress, and owned frame/tab color. EOF cleanup remains fallback-only.

Changed

• Normal events keep real spinner animation and result-ready transitions
  without starting a command shell; the synchronous SessionEnd cleanup Hook
  starts one command process per session.
• The source-audited Codex 0.147 command fallback remains supported. The
  direct Windows declaration and generic hostile-path declaration both retain
  synchronous one-second bounds.
• Strengthened owned-Hook repair and runtime continuity: exact owned groups
  are repaired only when proven absent, while third-party Hooks and MCP
  servers remain preserved. /hooks trust remains manual-only; existing MCP
  trust hashes are preserved and the new SessionEnd definition requires
  Owner review.
• Agy has no admitted production provider in this release.