Skip to content

PiClaw v2.6.11 — Pressure Point

Choose a tag to compare

View all tags
@piclaw-bot piclaw-bot released this 19 Jun 19:35
v2.6.11
0e70b93

PiClaw v2.6.11 — "Pressure Point"

A patch about making pressure visible before it turns into a mess: image annotation gestures behave better, malformed LLM context gets fuzzed, aborted turns and tool-call caps report properly, and compaction context usage stops hiding in the plumbing like it owes rent.

Features

  • Image annotation gestures in the web UI are smoother and less likely to feel like negotiating with a tiny hostile map of your own screenshot.
  • Tool-call cap usage is now reported, because hitting a limit silently is not “minimal UI”, it is just a progress bar wearing camouflage.
  • Compaction context usage is surfaced more clearly, so operators can see why context got squeezed instead of assuming the model developed a sudden interest in interpretive pruning.

Fixes

  • Aborted turn failures are surfaced more explicitly, because a failed turn should not vanish into the logs like it joined witness protection.
  • Malformed LLM context inputs now have fuzz coverage, which is the polite engineering phrase for “we threw weird shapes at it until it stopped flinching”.
  • Pre-prompt compaction resume tests now capture and run the queued resume task directly, making the test deterministic instead of asking the scheduler, the queue, and the moon phase to agree within half a second.

Under the hood

  • Earendil packages were bumped to 0.79.8, keeping the shared runtime stack current and ensuring any upstream surprises at least arrive with fresh stationery.
  • Context pressure, compaction usage, tool-cap reporting, aborted-turn failure paths, malformed-context fuzzing, and image annotation tests were expanded around the new behaviours.
  • Image annotator fixture tests now resolve paths from the checkout instead of assuming /workspace/piclaw, because CI runners also enjoy not being gaslit by absolute paths.
  • Classic web bundles were rebuilt for the patch, because apparently every UI change must leave behind a sedimentary layer of JavaScript.

Known issues

  • Context pressure remains arithmetic with consequences; this release makes more of it visible, it does not repeal token limits.
  • Fuzzing malformed context inputs proves we handled the weird things we tried, not that the universe has run out of weird things.
  • Image annotation gestures are better, but humans can still draw arrows with the emotional precision of a raccoon holding a stylus.

Upgrade

  • Upgrade normally; no migration step is required.
  • If pressure, caps, and aborted turns are easier to diagnose, that is intentional; if they are still annoying, that is distributed systems keeping its brand consistent.
Assets 13
Loading