`hiveloom compaction-log`

Reads the compaction event log — a record of every time an agent’s context was summarised to fit the model’s token budget. Use this when an agent’s replies get vague or short and you suspect aggressive compaction.

Synopsis


hiveloom compaction-log [OPTIONS]

Options

Flag	Default	Description
`--agent <AGENT>`	—	Filter by agent (ID or name).
`--tenant <TENANT>`	`default`	Tenant slug.
`--since <DURATION>`	`24h`	Show events from the last N. Examples: `1h`, `6h`, `24h`, `7d`, `30d`.
`--limit <N>`	`50`	Maximum events.
`--json`	—	JSON output.
`--endpoint <URL>`	—	API endpoint.
`--token <TOKEN>`	—	Bearer token.

Examples

Last 24 hours, default tenant, all agents:


hiveloom compaction-log

Last week for one agent, JSON, fed to jq:


hiveloom compaction-log \
  --agent pirate \
  --since 7d \
  --limit 500 \
  --json \
  | jq 'select(.trigger=="token-budget")'

What’s logged

Each event records: when it fired, which agent, what triggered it (token-budget, manual, tool-result-truncation), how many tokens were retained, and how many were summarised. Per-agent compaction behaviour is configured via hiveloom agent compaction.

When to use it

An agent’s replies suddenly look vague → check if compaction is firing too aggressively.
An agent stops referencing earlier turns → compaction may be dropping the relevant context. Tune the agent’s compaction config or raise the budget.
After a release that changed compaction defaults → confirm the new behaviour matches expectations on a representative agent.