Word setAgent Ops
Featured termA fresh pick each visit

Agent Ops / Standard term

An audit log is a running record of every action an agent took, each entry stamped with the time and the inputs that produced it, so you can reconstruct what happened after a run finishes.

An audit log is a running record of every action an agent took, each entry stamped with the time and the inputs that produced it, so you can reconstruct what happened after a run finishes. Each line answers what the agent did, when, and with which inputs. Say you let an agent triage your inbox overnight and label messages by topic. In the morning the log shows it read forty messages, applied a label to thirty-eight, and skipped two it could not classify, with a timestamp and the message it acted on for every step. Reading that trail, you catch the two silent skips, confirm the labels were sensible, and decide whether to let it archive on its own next time.

Builder example

When an agent runs without you watching, the log is how you find out what it touched. Picture a scheduled agent that drafts replies to support tickets each hour. If a customer reports a reply that quoted the wrong order, you open the log, find the entry with that ticket's timestamp and inputs, and see whether the agent pulled the wrong record or wrote from a bad prompt. Tell the agent to record every action it takes, so a quiet mistake leaves a trace you can follow back to its cause.

Common confusion: An audit log records what already happened so you can review it afterward. An approval gate stops an action before it runs and waits for a person to say yes. The log explains a finished run; the gate controls a pending one, so most setups use both.