Skip to content

The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu

Note that --around-event ignores the event-type filter

Lawrence Jones4e020ff4acd3
diff --git a/agent-skills/skills/beacon-memory-distill/SKILL.md b/agent-skills/skills/beacon-memory-distill/SKILL.md
index c2c1fa63..60d2fbae 100644
--- a/agent-skills/skills/beacon-memory-distill/SKILL.md
+++ b/agent-skills/skills/beacon-memory-distill/SKILL.md
@@ -141,6 +141,9 @@ How to read what comes back:
failed command followed by a different command that succeeded.
- A `user_message` with `content.included` false, or only a hash, means Beacon kept
metadata only. You cannot draft from a hash; say the trace was unreadable.
+- `--around-event` centres on the unfiltered event number. Combined with `--event-type`
+ it can return no events at all, so read a small unfiltered window around the number
+ and skip the `token_usage` and `session` rows yourself.
Work out, from the events themselves: