| Activity | What the agent did, counted by kind, the commands it ran with their exit codes, and each rule finding linked to its evidence. It is also the spec’s example lens. |
| Files Changed | Every file the agent created, edited or deleted, as a tree with line counts. Selecting a file shows each of its edits in order, with the diff, or the diff’s hash and size when it was not retained. Files only read are counted, not listed. |
| Token Usage | An itemized bill: counted usage and runtime-reported cost, split by model and by turn, then every event that reported usage. When the events’ own numbers add up to more than Beacon counts (usage reported on two channels, or as a cumulative counter), the lens says so. It also says when a runtime that should report usage did not, and when a runtime never exposes usage at all. |
| Security Review | Threat-rule findings grouped as untrusted input (prompt injection), sensitive access (credentials, metadata endpoints) and consequential action (exfiltration, destructive commands, sensitive edits). It calls out a trace that has all three, which is how an injected instruction turns into stolen data, and shows each finding’s evidence events. |
| Approvals & Policy | Every approval decision in order: allowed or denied, whether the operator or a policy provider (the optional BEACON_POLICY_PROVIDER seam) decided, what it was about, and whether the runtime reported it or Beacon inferred it. |
| Skills | Every skill the agent loaded, where each entered the run (the event, and the prompt it came under) and how (a skill tool call, a read of a SKILL.md, or a shell command that printed one), and the exact instructions the agent received, when the runtime reported them and the log retained them. A load whose text was not retained shows its hash and size instead. |
| MCP Calls | Every MCP tool call, grouped by server and then by tool, with how many calls each tool took and how many failed. Each call shows when it ran, its method and resource URI where the runtime reported them, and the arguments the agent sent and the result that came back. A call whose result reports isError or an error is marked failed. |
| Failures | Everything that went wrong, in order: commands that exited non-zero, tool and MCP calls the runtime reported as failed, and error events, each with the output or result that explains it, or the output’s hash and size when it was not retained. A call reported twice (by a hook and by OpenTelemetry) is listed once. For each failed call it says what the next identical call did (the same command line, the same tool on the same path, or the same MCP tool with the same arguments): succeeded, failed again, or never came. |