Engineering Trace

The Engineering Trace panel turns a coding session into a map of what the agent actually did — every file it read, every change it made, every decision it took, every skill it ran and every error it hit, drawn along a timeline you can click through.

What you see

• Trace Map — the session as a directed flow of events: reads, edits, decisions, corrections, tests and validations, laid out so you can follow the agent's reasoning from first message to last.
• Changes — every file the agent touched, grouped so you can review what actually changed before you trust it.
• Skills — the skills the agent invoked during the session, and when.
• Decisions — the choices the agent made and the reasoning it recorded around them.
• Validation — the checks and tests the agent ran, and their outcomes.

Metrics at a glance

The header of the panel keeps a live scoreboard over the whole session: total events, files changed, skills used, decisions made, corrections applied, and the duration. Cost and token figures are shown per session too, and clicking them expands a chart of spend by event type so you can see where the budget went.

Why it matters

A coding agent that explains itself after the fact is easier to trust than one that just delivers a diff. Engineering Trace is that explanation: it is the audit trail of a session, built from the same conversation you can already see, and it stays attached to the task so you can return to it later.

Next steps

• Repository Intelligence — the map of your codebase itself.
• What is AETHER Coder — the panel these views live in.