---
site: steel.dev
collection: blog
canonical_url: https://steel.dev/blog/agent-logs
markdown_url: https://steel.dev/blog/agent-logs.md
content_signal: ai-input=yes, ai-train=yes, search=yes
related:
  - https://steel.dev/blog/why-we-built-agent-traces.md
  - https://steel.dev/blog/agent-traces.md
  - https://steel.dev/blog/launch-week-v2-recap.md
title: "Agent Logs: Action Traces for Agent Actions"
description: Debug, trace and observe the actions your agents take with Agent Logs.
date: 2025-10-15
authors:
  - Hussien Hussien
category: Product
launch_week: v2
minutes: 2
tldr: "Steel added agent logs to its dashboard: a timeline of every action an agent takes in a session (clicks, navigation, typing, scrolling), shown next to the session viewer. Each event has a type, timestamp and target element, clicking an event seeks the viewer to that point, and events can be filtered by type."
topics:
  - Agent debugging
  - Action logs
  - Session replay
  - Browser automation observability
entities:
  - Steel
  - Agent Logs
answers_questions:
  - How do I see what actions my browser agent took in a Steel session?
  - How do I debug where a browser agent failed?
  - What information does each agent log event show?
  - Where do I find agent logs in the Steel dashboard?
---

# Agent Logs: Action Traces for Agent Actions

Today we're adding agent logs to the Steel dashboard. View every action your agent takes in a session (clicks, navigation, typing, scrolling) on a timeline next to the session viewer.

When your agent fails at a task, you can trace exactly where things went wrong. When it succeeds, you understand why and can reproduce those results later.

[Video on YouTube](https://www.youtube.com/watch?v=Vhx2u0Tynj0)

## How it works

Agent logs appear alongside the session viewer in the Steel dashboard. Each action shows:

- **Event type**: Click, navigation, scroll, keyboard input
- **Timestamp**: When the action occurred
- **Target element**: What the agent interacted with

Click any event in the timeline and the session viewer jumps to that point. You can see what the agent saw, what it did, and what happened next.

## Why this matters

Most agent failures happen silently. Your agent clicks the wrong button, types in the wrong field, or navigates to an unexpected page. Without logs, you're replaying entire sessions trying to spot the moment things broke and matching those to a sea of console logs.

Agent logs give you the exact sequence of events. When a checkout fails, you see that the agent clicked "Express Checkout" instead of "Standard Checkout" at timestamp 00:47. When authentication breaks, you see it typed the password in the username field at 00:12.

For successful runs, logs show you the path your agent took. You can verify it followed the expected flow, identify optimization opportunities, or use the sequence to build more reliable automations.

## Debugging in practice

Before agent logs, debugging meant watching entire session replays and guessing where things went wrong. Now you scan the timeline for anomalies: unexpected navigation events, repeated clicks, or missing form inputs.

You can also filter events by type. Show only navigation events to trace the agent's path through a site. Show only click events to verify it's interacting with the right elements. Show only keyboard events to check what data it entered.

## Get started

Keep an eye on your sessions as this will be rolling out to Steel dashboards over the day. View them at app.steel.dev under any session's detail page.

- [Dashboard](https://app.steel.dev/)

Questions? [Discord](https://discord.gg/steel-dev) or [@steeldotdev](https://twitter.com/steeldotdev).

*Part of Steel's launch week. More at* [*steel.dev/launch-week*](https://steel.dev/blog/launch-week-v2-recap)*.*