ShipUntilDead
The idea
A record of what really happened.
A finished output rarely explains the whole run. Model calls, tool use, file changes, and shell commands can be scattered across systems. When something goes wrong, reconstructing the sequence becomes its own project. Agnys brings those events into one reviewable history.
What it does
The moving parts.
Capture the activity
A forwarder collects model calls, tool actions, file edits, and shell commands into an action feed. Supported capture paths include Claude, LangChain, LangGraph, VS Code, AutoGen Studio, LM Studio, Ollama, and Antigravity.
Reconstruct the session
Session replay follows a run from its trigger through the recorded actions to the outcome. AQL Search Lab adds queries, sequence searches, saved searches, and alerts across the history.
Look for behavioral changes
The product’s Behavioral DNA feature establishes normal patterns and flags deviations such as scope creep or suspicious activity for review.
Take the evidence with you
Hash-chained events make the audit history tamper-evident. PDF, CSV, and JSON exports support human review and machine verification. Governance checks map recorded evidence to supported frameworks.
How it works
From idea to action.
Connect the capture path
Start on the Agnys website and follow the setup for the tools you use. Supported automatic integrations can capture activity without changing application code.
Run and review
Let the agent work, then inspect the action feed, search the recorded events, or replay a session to understand its sequence.
Export a reviewable record
Package the relevant history for debugging, investigation, or governance review in the format your team needs.
In practice
Before you dive in.
Agnys is a separate hosted product. Visit its website for current onboarding, integration requirements, and product availability.
The site describes mappings to the EU AI Act, GDPR, ISO 42001, and NIST AI RMF. These organize evidence for review; they do not make every deployment automatically compliant. Recording must be in place when the activity happens—missing historical events cannot be reconstructed as an original audit trail.
Go deeper
Straight from the source.
Explore the original documentation for setup instructions and the latest changes.