Skip to content

Sessionbus peers v0.5.2

Choose a tag to compare

View all tags
@github-actions github-actions released this 21 Sep 00:10
v0.5.2
This tag was signed with the committer’s verified signature.
antst Anton Starikov
SSH Key Fingerprint: lgAnkhJdgKV1odY8EpHWrEpCwDRVj0NWAJijtWvpeXU
Verified
Learn about vigilant mode.
a1af0c1
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.2

Managed peer and lane launches keep the Sessionbus communication tool available under ordinary native policy, while preserving caller-selected permissions for other tools.

Changes

  • Add exact Sessionbus tool grants for Codex and Qwen; protect managed communication from conflicting launch arguments in Claude and Pi. OMP exposes the tool through its native approval and essential-tool mechanisms.
  • Grok ensures the exact MCPTool(sessionbus__sessionbus) allow rule in its global user config before managed startup. Existing compact or structured permission rules and unrelated settings are preserved; subsequent launches do not rewrite an already-present rule. This persistent config rule works around native leader-mode CLI rules being ignored. The wrapper verifies rule presence, while native policy remains authoritative: existing deny and ask rules are preserved, and effective permission still depends on native policy and caller-selected mode.
  • Restore explicit Kilo lane bypassPermissions through native session policy, leaving ordinary launches on inherited policy.
  • Update the public Sessionbus Go SDK and JavaScript kit to 0.5.5, including compatibility with effective trace-policy responses.
  • Report peer release/build identity from --version; use --native-version for the underlying product version outside lane mode.
  • Fix Codex local-plugin catalog discovery and improve installation documentation.

Qwen limitation

This release ships the Qwen wrapper permission fix, not a native memory fix. One official Qwen 0.24.1 run delivered its Sessionbus message and then failed with a V8 heap OOM; its cause remains unresolved. Subsequent instrumented rebuilds did not reproduce it, including one ten-minute session with ten turns and twenty confirmed message deliveries. Used heap returned from a 615.7 MB peak to 141.3 MB and RSS from 756.1 MB to 250.8 MB. Those rebuilt binaries are not byte-identical controls for the original official artifact.

No diagnostic counters, SDK instrumentation, PTY test drivers or heap-limit workaround are included in the wrapper release. The original failure and bounded diagnostic results remain documented in PR50.

Scope and compatibility

Pi and OMP remain preview integrations. Explicit bypass remains a separate caller choice; the managed Sessionbus grant does not enable global bypass. Use matching current peers/helpers and Sessionbus 0.5.5 for the current tracing response contract, and restart managed sessions after updating their helpers.

Assets 36
Loading