Skip to main content

History

History lists the chat sessions that your gateways routed. Each row is one session, made of one or more entries. An entry is one model request and its result.

Before you start​

  • You need history:read to see sessions. To read retained prompts and responses, you also need ai_usage_stream:read. To edit tags, you need history:write.
  • The gateway must capture history. History capture is set in the history.capture block of the policy config. See Runtime configuration.
  • An empty History does not mean that the gateway received no requests. Capture can be off, or the retention period can be over.

Find a session​

  1. Open History.
  2. Type in the search field. You can use free text, or field:value filters, for example:
    • type:chat
    • status:blocked or blocked:true
    • agent:support-app
    • entries:>5
    • started:today or updated:>2026-01-01
  3. Optionally select a time range. To start again, select Clear filters.

History with a list of saved sessions, each with its agent, model, number of entries, and start and update times.

The table shows Session, Agent, Model, Entries, Started, and Last updated. You can show more columns, such as Gateway, User, Team, Allowed, Blocked, and Tags.

Read a session​

  1. Select a session. Session details shows the agent, actor, team, entries, tokens, and gateway.
  2. In Entry timeline, select an entry to see its request, response, and Audit facts, such as Decision, Provider, Model, and Token usage.
  3. To read the retained conversation, select Show conversation. If nothing was retained, the Console shows No conversation was retained for this session.

History has no export button. To export sessions, use verdictan history export.

Next steps​