AppsSecurity & Compliance

Audit and evidence

Execution history

Autessa keeps the history of every tool execution, closed agent and manager conversation, table trigger firing, scheduled job run and inbound webhook call, with decrypted inputs and outputs. Every surface is viewable in the web app and readable from the CLI, and each run records its source, such as API, TRIGGER, AGENT, SCHEDULED, WEBHOOK or SCRIPT.

Start free
Execution historydecrypted inputs and outputsSample
Tool historyLook up ordersource: API
Agent historySupport Assistant · closedsource: AGENT
Trigger historyinvoices · on insertsource: TRIGGER
Scheduled jobNightly syncsource: SCHEDULED
Webhook handlerStripe eventssource: WEBHOOK
ScriptMonthly closesource: SCRIPT

Visible to the person a run acted as, the resource’s Admins and company Admins.

The problem

What problem does it solve?

AI agents and automations act on your behalf around the clock. Without a complete record of what each one did, with what inputs, you cannot debug it, let alone audit it.

How it works

  1. 1

    Find the run

    Open the tool, agent, trigger, job or webhook handler history, or list it from the CLI.

  2. 2

    Read it in full

    Lists cap payloads and say so (requestTruncated, resultTruncated); detail returns the full value.

  3. 3

    Know where it came from

    The source field tells a terminal-driven run from a trigger or an agent.

  4. 4

    Respect who may see it

    History holds reads made as a specific person, so it is as private as those reads.

Every option

Execution history: settings and options

SettingWhat it does
Tool historyautessa tools history list / history detail
Agent historyautessa agents conversations history / conversation
Manager historyautessa managers conversations
Trigger historyautessa trigger-history list / detail
Scheduled job runsautessa scheduled-events history
Inbound webhook callsautessa custom-webhooks get-execution-history

Permissions

Who can do what?

WhoWhat they can do
The person a run acted asSee that run.
The resource’s Admins and company AdminsSee all of its runs.
AutessaDB permission holdersUse trigger execution history.

FOR DEVELOPERS

autessa trigger-historybash
autessa trigger-history list --tableId <tableId> --page 0 --size 25
autessa trigger-history detail   # full, uncapped event and response

What to know

  • An agent conversation is logged after it is closed, so history may lag a moment behind the end of a conversation.
  • Tools with Sensitive output on are never written to history.

Read the docs: CLI: the audit surfaces →

Connections

How Execution history connects to the rest of Autessa

Who a run acts as →

Why history is private to the person behind each run.

Tenant isolation and encryption →

Payloads are encrypted with your company key.

AI-native runtime →

Conversation history for agents.

Reports, policies and security questionnaires are on the Autessa Trust Center.

FAQ

Execution history: questions

Can I see exactly what an agent sent to a tool?

Yes. Agent history includes full message and tool logs, and tool history includes decrypted inputs and outputs.

Can I tell if a change came from the CLI?

Yes. Each run’s source distinguishes API, TRIGGER, WORK_ITEM, AGENT, SCHEDULED, WEBHOOK and SCRIPT.

Get started with Execution history

Every tool execution, agent and manager conversation, trigger firing, scheduled job run and inbound webhook call is recorded with its inputs and outputs, and each run says where it came from.

Start free

Reports, policies and questionnaires live on the Autessa Trust Center.

100% customizable, code and all

Make Autessa Security & Compliance fully your own.

Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.

Start free and make it yours