Skip to content

PiClaw v2.7.0 — The Right Stuff

Choose a tag to compare

View all tags
@piclaw-bot piclaw-bot released this 23 Jun 20:19
v2.7.0
ec3135d

PiClaw v2.7.0 — "The Right Stuff"

A runtime migration release for Earendil 0.80.1: Piclaw now uses the new Models/runtime API surfaces instead of leaning on deep imports and compatibility scaffolding like a ladder made of old release notes.

Platform news

  • Piclaw now targets the Earendil 0.80.1 runtime APIs, aligning model/session/agent integration with the upstream package boundary rather than spelunking through internals and hoping the cave keeps its shape.
  • Public add-on compatibility was validated against the new runtime surface, so the migration is not just “it compiles here”; it also avoids detonating the obvious extension ecosystem on contact.

Fixes

  • Removed obsolete Pi AI deep-import typings and updated import-boundary checks so accidental private API usage has fewer places to hide.
  • Azure OpenAI, context mode, context pruning, smart compaction, side prompts, session rotation, agent info, and session management paths now use the migrated runtime contracts.
  • Test coverage was refreshed around model/runtime integration, reasoning metadata, context pruning, Azure OpenAI API handling, import-boundary enforcement, and live tool activation.

Under the hood

  • Earendil packages were bumped to 0.80.1, carrying the Models-runtime/API migration through package.json and bun.lock.
  • Agent pool contracts, session manager, session creation, and side-prompt runner code were updated for the new upstream shapes.
  • Deterministic audit scripts and skeleton agent guidance were updated to match the new API expectations.
  • The old deep-import compatibility file was deleted, because keeping a fossil in the type tree does not make it architecture.

Known issues

  • This is a runtime/API migration release; it should be boring at runtime, which is the only acceptable kind of exciting for this layer.
  • Third-party extensions that depended on private Earendil internals may need updates; depending on internals remains a hobby best practised with a helmet.

Upgrade

  • Upgrade normally; no database migration is required.
  • Extension authors should retest against the public runtime APIs and stop borrowing furniture from upstream’s private rooms.
Assets 13
Loading