Skip to content

PiClaw v3.3.4 — “Galaxy Quest”

Latest

Choose a tag to compare

@piclaw-bot piclaw-bot released this 15 Oct 23:31
· 1428 commits to main since this release

PiClaw v3.3.4 — “Galaxy Quest”

The ship’s computer has received several clarifications. A status report must describe the turn currently on the bridge, a message must reach the conversation that actually exists, and an instruction to finish without tools must not include directions to the armoury. The crew may still improvise; the routing system should not.

Credential handling receives similar attention. A locked storage compartment is distinguishable from an invalid access code, reducing the occasions on which the captain is invited to log in again because someone misplaced the cupboard.

Highlights

  • Manual compaction keeps reliable status. Older turn updates cannot overwrite current compaction state, and compaction claims ownership before asynchronous work begins.
  • Credential failures are diagnosed more accurately. Storage, locking and configuration faults are distinguished from rejected authentication; recovery handles transient refresh and synchronisation failures.
  • Pi moves to 1.2.0. The published upstream release is qualified with the existing Piclaw integration.
  • Branches and windows keep their identities. Exact branch targeting, remote-session lifetime checks and UI lifecycle fixes reduce misdirected messages and stale state.
  • Recovery finishes without contradicting itself. Tools-disabled finalisation receives a matching prompt while retaining enforcement against tool reactivation.

The current bridge watch

Manual compaction status is fenced to its owning turn. Late updates from an older turn still deliver their responses, but cannot replace newer compaction state. Early ownership claims close a second race before asynchronous compaction and rotation begin.

Compaction output budgets follow the available reserve, model output limit and remaining context instead of a fixed 8,192-token ceiling. The computer consults the available space before promising to fit another shuttle in it.

Credentials with the correct access codes

Credential diagnostics distinguish storage, lock and configuration faults from authentication rejection. Transient OAuth failures receive bounded retries, and offline synchronisation recovery uses fences to avoid overwriting newer credential state.

These changes do not replay inference requests after a 401 or force-refresh credentials indiscriminately. Diagnostic messages remain sanitised.

Messages to the right ship

Exact local add-on targeting considers live sibling branches even when their advertised alias is deduplicated.

Remote delivery checks the target branch’s lifetime during admission, preventing a stale reference from silently attaching to a replacement conversation. Supporting incarnation, cancellation and transactional admission checks preserve that boundary. A familiar call sign does not make it the same vessel.

Stand down means stand down

Recovery and finalisation paths that disable tools use a dedicated text-only prompt. Tool fences remain enforced, attempted reactivation stays blocked, and the normal tool loadout is restored afterwards.

Tool-enabled continuation retains its existing behaviour. The instruction sheet and the locked armoury now agree.

Windows and widgets

Widget isolation and status, editor and pop-out lifecycle fixes address stale state and ownership handoffs across the interface.

These changes reuse the existing conversation, queue and activity surfaces. They do not add a second bridge from which to command the first.

Upstream compatibility

The Pi package family advances to 1.2.0 following qualification of the published release.

The existing Piclaw integration remains in place. This release does not implement the planned pi-durable migration.

Known limits

  • Native MCP remains experimental; Adapter selection is unchanged.
  • Local-lite remains opt-in and defaults to off.
  • Credential recovery does not guarantee that an upstream provider will accept a request.
  • Native desktop applications remain discontinued.
  • The monthly release cadence and planned pi-durable transition remain unchanged.

Upgrade

Follow the repository installation instructions for v3.3.4. Preserve workspace data and configuration, then restart through the service manager appropriate to the installation.

The bridge should now receive the right reports, the right messages and fewer invitations to authenticate the furniture. Further improvisation is left to the crew.

Complete PR list

  • #1642 — Exact local add-on targets across sibling branches.
  • #1643 — Remote delivery fenced to branch lifetimes.
  • #1644 — Credential diagnostics and recovery reliability.
  • #1645 — Context-aware compaction output budgets.
  • #1646 — Published Pi 1.2.0 qualification.
  • #1647 — Tools-disabled recovery prompt.
  • #1648 — Text-only finalisation and tool-fence coverage.
  • #1649 — Widget, status, editor and pop-out fixes.
  • #1651 — Manual compaction status and ownership races.

Release qualification

The filesystem-backed retention test retains its 101-record ordering coverage with a thirty-second allowance for slower test hosts. No runtime behaviour changes with this test-only adjustment.