Logs and history
Session logs
Every answer, action, and move — with the source behind it and who did it.
Logs is the record. It is the surface to open when you need to know not just what was said but why — and it is what makes an autonomous agent supervisable rather than merely fast.
What is recorded
| Entry | Carries |
|---|---|
| An answer | The reply, and the source it was drawn from |
| A move | The card moving between columns, and what made it move |
| A takeover | Which member stepped in, and when the agent stopped |
| A policy change | A board's agent being switched on or off, and by whom |
| A channel change | The channel being paused, resumed or reset |
Answers are attributed to the board and the agent profile that produced them, so on a workspace with several boards you can always tell which agent said what.
Reading a conversation's history
Find the conversation and read down. A well-behaved exchange reads as a chain: an answer, its source, a move when the column's condition came to hold, then either a hand-off or a close.
The two things worth checking when something looks wrong:
- Does each answer name a source you recognise? An answer with no source, or a surprising one, points at the board's knowledge rather than at the agent.
- Did a move happen without the condition being met? That points at the column objective being written loosely.
What logs are for
- Auditing a specific complaint — what did we actually tell this customer?
- Tuning an agent — the pattern across many conversations, not one.
- Confirming a change landed — after flipping a board switch, the next inbound message should reflect it.
Related
- Guardrails — the rules whose observance you are checking
- Policy behavior — what the agent's saved policy changes