A replayable record of everything the agent did.
When an agent breaks something, teams should not have to reconstruct the failure from scattered logs. Flight Recorder keeps one ordered history per dock.
- One timeline
- Runs, prompts, commands, SSH sessions, file changes, and snapshots line up in the order they happened.
- Network decisions included
- Each outbound connection shows whether policy permitted or blocked it.
- Cost in context
- See what a run cost next to what it did, not in a separate billing export.
- Captured outside the guest
- Usage comes from host counters, not guest self-reports, so an agent cannot quietly edit its own record.
Questions
Who can see Flight Recorder data?
Access follows workspace roles. Retention follows your plan and workspace policy.
Use cases that fit
Coding agents
Run coding agents like Claude Code, Codex, and OpenCode in isolated, repository-aware Linux machines with Docker, previews, and cheap branches.
Learn moreBrowser and computer use agents
Keep Chrome profiles, logins, and session state on a persistent dock, with a live desktop for human takeover when the workflow needs judgment.
Learn moreQA and preview environments
Build branches, run services, expose private preview URLs, and keep screenshots, logs, and artifacts on a persistent dock per change.
Learn moreInternal agent platforms
Connect agents to internal tools and private systems with deny-by-default egress, brokered credentials, approvals, and a full audit trail.
Learn moreAgent evaluations
Branch one snapshot into many identical docks to run agents, prompts, or models side by side and compare results fairly.
Learn more
Tell us what your agents need to run.
Private beta is open. Describe your workload and we will reply about access.