Skip to content

v0.5.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 14 Sep 13:20
v0.5.1
This tag was signed with the committer’s verified signature.
antst Anton Starikov
SSH Key Fingerprint: lgAnkhJdgKV1odY8EpHWrEpCwDRVj0NWAJijtWvpeXU
Verified
Learn about vigilant mode.
87270e4
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Sessionbus peers v0.5.1

This release adds parent-tracing tool controls, fixes Codex result collection,
and corrects OMP startup and shutdown ordering. Pi and OMP remain preview
integrations.

Included source changes

  • Codex now collects every final_answer item from the exact persisted native
    turn in native item order. It joins multiple items with one blank line while
    preserving the bytes inside each item. Commentary, tool messages, and other
    turns remain excluded. This fixes the confirmed multi-item collection loss in
    #66; it does not rewrite text
    generated by Codex itself.
  • OMP normal shutdown drains the owned native RPC stream and report work before
    completing owner cleanup. Startup bridge requests now wait until the registry
    owns the bridge, so an immediate native owner.ready cannot race its
    assignment. The wait remains cancellable and shutdown joins it.
  • Every peer tool declaration exposes trace with mode off, events, or
    content, and spawn accepts the same initial trace setting. The default is
    off. A trace-aware daemon sends at most one ordinary message copy to the
    eligible direct parent for a settled Sessionbus send. content includes the
    body; events carries message and delivery metadata.

Trace compatibility and limits

Parent tracing requires the corresponding Sessionbus daemon and all involved
hubs, available in Sessionbus v0.5.4. Updating peers alone does not enable it.
The initial scope excludes Run/lane lifecycle events and native prompt or result
content.

Older daemons reject trace as an unknown method and reject an explicit spawn
trace field under their closed schema. Updated daemons report
unsupported_trace for tracing controls across unsupported federation links.
The live tracing relationship ends when the parent ends, including for
persistent children; a same-ID reconnect does not recover it.

Tracing creates no durable policy, trace history, journal, replay, catch-up, or
separate event transport. Copies use ordinary Sessionbus message delivery and
remain live, bounded, and best-effort. An upgrade error must not be interpreted
as tracing being enabled.

Preview scope

Pi and OMP remain preview integrations under the existing
acceptance record. This
release does not promote them or replace their remaining installed acceptance
work.

Assets 36
Loading