Skip to content

v0.6.1 — agent can read/search its own session

Choose a tag to compare

View all tags
@michalekz michalekz released this 19 Jun 22:40
· 103 commits to main since this release
v0.6.1
65e37b2

Patch release allowing an agent to read and search its own session. Two paternalistic blocks were removed because they actively hurt the most useful recovery scenarios.

Changed

`peer_chat_read` no longer rejects own session

Previously `peer_chat_read { to: }` returned `self_read` error with message "Cannot read own chat — your own context is already loaded". That assumption is wrong in three common scenarios where it matters most:

  • Autocompact — context window is compressed, original detail is gone from in-memory but lives on disk.
  • `/clear` during a long session — agent intentionally cleared its context, JSONL stays intact on disk.
  • Resume after crash / restart — only partial context is reloaded, full history is on disk.

In all these, querying own JSONL via `peer_chat_read` is the legitimate (and sometimes only) recovery path.

`peer_chat_search` no longer silently filters out caller's own session

Same reasoning. Post-autocompact / long-session use needs to search full on-disk history, including own session. The silent filter made searches look incomplete without explanation.

`peer_ask` self-send block stays intact

`peer_ask { to: }` still returns `self_send` error. Sending a message to your own inbox is genuinely a weird loop with no useful semantic.

Why this isn't a breaking change

No tool signature changes. Both tools accept the same args. Behavior change only: previously-erroring calls now succeed. No existing correct code can break.

Tests

  • Existing self-rejection tests flipped to verify happy-path: `peer_chat_read { to: self }` returns own messages; `peer_chat_search` includes self session in scope.
  • 230/230 tests pass.

See CHANGELOG.md for the full record.

Assets 2
Loading