---
title: Log of AI agent steps
summary: Every run leaves a record of its steps. The person who started a run sees what was done in the chat. Talemo's staff tools read only technical facts of runs, not the words.
tools: []
related: [run, stopping-and-retry, run-spend, built-in-agents]
search: [audit log, steps of AI]
---

# Run journal

## What is recorded

For each run Talemo keeps the steps in order: every call to the model, every call
to a tool with its result, the approvals that were asked and decided, how the run
ended and what it spent. A step is written down when it begins and again when it
ends, which is what lets an interrupted run continue (see
[Stopping, cut-offs and retries](stopping-and-retry.md)).

## What the person sees

Under each answer of the assistant:

- **What I did** with the time the run took, as a list of steps in plain words:
  "Looked at the visits", "Changed a contact", "Looked in the knowledge". A step
  can be marked "Didn't work" or "It isn't known whether this was done".
- **Where it comes from**, the sources of the answer: Visits, Contacts, Knowledge,
  Balance and so on.

The time does not include the time spent waiting for a decision. The list names
what was looked at or changed. The arguments and results of the steps are not in
the chat.

## Who can see a run

Only the person who started it. A run of someone else is not visible to anyone,
the owner included. A role can be given the rights **Give the assistant work** and
**See what the assistant did**, and the second one covers the person's own runs.

The online admin's runs belong to no person. The business sees their result in the
chat: the messages, the drafts, and the cards that pass a chat to the team.

## What the assistant changed

What the assistant changed in the data shows in the history of the record itself,
for example in [Contact history](../clients/contact-history.md) as "the
assistant" at a person's request.

## What Talemo's staff tools read

The tools Talemo's staff use to look after the service read the structure of a run
and technical facts: status, codes, counts, time. The columns that hold what people
and clients wrote, the agent's replies and the arguments and results of calls are
closed to those tools.

The team also reads the requests the assistant passes on when it cannot do
something (see [Request to the Talemo team](../assistant/feedback-to-team.md)).
Those arrive in the person's own words.

## Ignored chats

When a chat is ignored, the words of that chat are erased from the run records as
well. Arguments, sent data and results of the calls that carried them are replaced
with a mark. That a call took place and when remain. A run with erased calls
cannot be replayed word for word. The assistant's conversation with the person and
the knowledge already approved stay.