Session Overview
Semantic rollup of a high-velocity agent session to prevent execution amnesia and cognitive load.
Install
npx ax-depute@latest add session-overviewpnpm dlx ax-depute@latest add session-overviewyarn dlx ax-depute@latest add session-overviewbunx ax-depute@latest add session-overviewBasic usage
Use <SessionOverview /> at the conclusion of a complex, multi-step agent run where the agent touches across dozens of files, APIs, or databases.
import { SessionOverview } from "@/components/SessionOverview";
export function PostRunReport() {
return (
<SessionOverview
sessionSummary="Refactored the authentication strategy and updated corresponding unit tests."
duration="14m 23s"
surfacesTouched={[
{ type: "file", label: "src/auth/index.ts", action: "write" },
{ type: "system", label: "jest-test-runner", action: "execute" }
]}
keyDecisions={[
{ description: "Bypassed standard hashing due to legacy auth constraints." }
]}
/>
);
}Props
| Prop | Type | Default | Description |
|---|---|---|---|
sessionSummary | string | — | High-level semantic summary of what the agent achieved |
duration | string | — | Total elapsed time of the agent session |
surfacesTouched | Array<{ type, label, action }> | [] | Which digital surfaces the agent interacted with |
keyDecisions | Array<{ description: string }> | [] | Significant decisions or deviations made autonomously |
Solution Patterns
Combating Execution Amnesia
When working with AI IDEs or multi-agent swarms, humans "fire and forget". After 10 prompts, humans suffer from Execution Amnesia—they no longer know what files were created, what systems were mutated, or what environment variables were exposed.
By rendering a SessionOverview dynamically updating on the side of the screen (or upon session completion), humans can quickly parse the total blast radius of the agentic action.
The Impact Matrix
Display SessionOverview next to the SharedContextLedger. The Ledger shows the memory the agent holds, while the Overview displays the tangible mutations the agent authored.
Design rationale
Why categorize impacts by Read vs Write vs Execute? When scanning a massive wall of text generated by an agent ("I did XYZ and then ABC"), users tune out. By categorizing surfaces touched strictly by their read/write vectors using standard UI badges, a security auditor or reviewing engineer can immediately identify exactly where side-effects happened in thousands of lines of code.
Visual layout scales better than walls of text for tracking agentic blast radiuses.