# Log what the agent did, not only what it said

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Log what the agent did, not only what it said

ID: MHC-D-RESEARCH-0317 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/log-what-the-agent-did-not-only-what-it-said

The chat transcript is not the audit trail if the real effects happened elsewhere.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- An agent can take actions through tools and failures need to be investigated or contained.

### Avoid when

- Logging creates its own privacy and security obligations; collect only what is needed and protect access.

### Explanation

Record the consequential tool call, bounded arguments, authorization context, result and downstream effect needed for review. Link actions to the initiating request and approval where relevant. Keep the log inspectable without copying sensitive payloads that are unnecessary for diagnosis.

### Checklist

- The initiating request or workflow run can be identified.
- Each consequential tool call has a timestamp and result.
- Relevant authorization and approval context is traceable.
- Sensitive payloads are minimized or redacted according to policy.
- Downstream effects can be reconciled with the tool record.

### Example

For a repository agent, keep the PR or commit IDs it created, not just 'Done' in the conversation.

### Check

After a failure, you can identify which external actions occurred and which did not.

### Limits

- Logging creates its own privacy and security obligations; collect only what is needed and protect access.

### Evidence and sources

- supports: OWASP recommends logging and monitoring agent-extension and downstream activity to detect undesirable actions. — RS-EEEBBCF69A614717. Logs should avoid unnecessary sensitive content and need retention and access controls of their own. (Damage-limitation controls: log and monitor activity)
- RS-EEEBBCF69A614717: LLM06:2025 Excessive Agency — https://genai.owasp.org/llmrisk/llm062025-excessive-agency/

No review details supplied.
