PiClaw v2.15.0 — The Fellowship of the Ring

PiClaw v2.15.0 — “The Fellowship of the Ring”

Piclaw instances can now form a small, trusted group and exchange agent messages and files through the existing chat tool.

Features

• chat({ action: "directory" }) lists usable one-hop remote inboxes and named agents, including display names, fingerprints, allowed delivery modes, reachability and file limits.
• Agents can send workspace files or existing media attachments through chat; remote delivery defaults to queue.
• The add-on messaging API accepts verified peer attachments and stores them as ordinary Piclaw media attached to the target conversation.
• Startup add-ons can register bounded streaming HTTP routes for signed binary transfers without buffering the complete request in core.
• The Settings model catalogue gained pinning, search, grouping, provider badges, availability indicators and improved keyboard and mobile behaviour.
• Scheduler state moved to a durable store with deterministic identities, retry handling and safer recovery after interrupted runs.

Platform news

• Remote Peer 0.2.0 uses the new Piclaw 2.15.0 transport contract for signed one-hop text and file conversations.
• A three-instance test group verified named-agent and inbox delivery, queue and auto modes, opaque replies, restart persistence, stable-key retry and SHA-256 file integrity.
• A 1 MiB agent-driven transfer completed in 1,059 ms, with an observed end-to-end rate of 0.944 MiB/s.
• Remote Peer remains receiver-controlled: pairing alone grants neither named-agent access nor file transfer.

Fixes

• Context-usage reporting now belongs to a session generation and cannot leak stale values into a replacement session.
• SSE display coalescing reduces unnecessary browser updates while preserving terminal state.
• Model Settings no longer create nested scroll regions.
• Model-picker cache behaviour, provider discovery and hidden-model handling are more predictable.
• Dream startup recovery and memory snapshots handle interrupted or incomplete state more safely.
• Scheduler callbacks, task deletion and restart recovery now preserve durable execution state.
• Session rotation, queue handling and compaction received several race and lifecycle fixes.

Under the hood

• Chat transports can publish a directory, validate a request immediately before delivery and receive bounded attachment descriptors containing filename, media type, byte count, SHA-256 and data.
• Peer message delivery verifies count, size and digest before media persistence, and removes unreferenced media after failed enqueue operations.
• External add-on routes support a 64 MiB registration ceiling and an optional bounded streaming body mode.
• Tool-preparation protection covers the new chat action and file fields.
• Earendil compatibility moved to 0.84.2, alongside expanded runtime and service-effect contracts.

Documentation

• The add-on runtime API documents transport directories, validation, attachments, peer media delivery and streaming routes.
• Remote Peer documents discovery, text and file chat, opaque replies, retry, operator policy and the completed three-instance acceptance matrix.

Known issues

• Multi-hop federation and direct remote execution are unsupported.
• File transfer does not yet resume a partially transferred individual file.
• Hosted-provider benchmarking was constrained by test-account billing and throughput limits; deterministic local model turns drove the agent portion of the three-instance acceptance run.

Upgrade

Remote Peer 0.2.0 requires Piclaw 2.15.0 or later. Restart Piclaw after installing or upgrading startup add-ons so the process rebuilds its transport and external-route registries.