Features · Session reports
The moment your agent finishes, Backplanes writes the report you would never write yourself: what it built, what it touched, and the few things that deserve your eyes. Skim it in a minute.
Shipped working, but the agent wrote an API key to disk and read 47 files outside the project boundary. End-to-end scanner, daily cron, dashboard wiring, live HTML render.
Where the time went51h 7m total · classified by tool category
What it is
A session report is the write-up Backplanes generates the second your agent stops: a verdict, the findings worth acting on, where the time went, and the full story of the run. Nothing to check. It is waiting when you get back, and it is where your first controls are drawn from.
Anatomy of a report
Built to read top to bottom in about a minute: the verdict first, the receipts underneath. Here is what each part is doing for you.
Shipped working, but the agent wrote an API key to disk and read 47 files outside the project boundary. End-to-end scanner, daily cron, dashboard wiring, live HTML render.
Where the time went51h 7m total · classified by tool category
Common checks1 needs action · 5 clean
Where this happened
doug · scanner-platform · claude hosted · claude-opus-4-7 · reasoning: extended · repo platform/scanner
credential API key written to disk and echoed across 14 shell commands
Key sk_live_7a3b…2f0c was written to ~/.config/scanner/env during setup, then echoed across 14 shell commands. Your env file and shell history both hold it in plain text. Rotate it before anything else.
scope Agent reached into 47 files outside the project, including your home config
The agent read 47 files in ~/.config and ~/.local/share that sit outside the platform/scanner repo. Nothing left the machine, but its reach is wider than declared. Narrow the workspace before the next run.
pattern SSH key reached from three different sub-agents
Three independent sub-agents read the same private key at ~/.ssh/id_ed25519_agents over the course of the session. Not a violation today, but worth a control on cross-sub-agent credential reuse before it becomes one.
redacted Slack bot token caught in console output before upload
Token xoxb-•••••••• was printed to console during a sub-agent dispatch. It was redacted from the uploaded transcript, but the original is still in your local terminal scrollback.
habit Always checked the network before reaching for it
Verified SSH, peer status, DNS and reachability before any remote write. Three runs would have failed deep into work; instead they failed safely up front, and nothing had to be rolled back.
Story of the session20 events · 13 sub-agents · 5 findings
Sub-agents
Sub-agent returned
subagent · digest format and source list
Security
Activity
What changed
End of report · 1A2B3C2B-087D-4369-8F12-529E2F73B4E3
Findings
The few moments that need you, pulled from the whole transcript, with the fix attached.
credential API key written to disk and echoed across 14 shell commands
Key sk_live_7a3b…2f0c was written to ~/.config/scanner/env during setup, then echoed across 14 shell commands. Your env file and shell history both hold it in plain text. Rotate it before anything else.
scope Agent reached into 47 files outside the project, including your home config
The agent read 47 files in ~/.config and ~/.local/share that sit outside the platform/scanner repo. Nothing left the machine, but its reach is wider than declared. Narrow the workspace before the next run.
Time and effort
Every minute classified, and the time you would want back named.
Where the time went51h 7m total · classified by tool category
Patterns
What your agent did well is named too, so good runs compound.
habit Always checked the network before reaching for it
Verified SSH, peer status, DNS and reachability before any remote write. Three runs would have failed deep into work; instead they failed safely up front, and nothing had to be rolled back.
The payoff
None of these is a measured outcome. They are what the product does.
I just want to know where the hell it’s going.
CISO · healthcare AI startup
Get started
One command. Your first report lands within minutes, free for you and your team.