From agent session to
engineering outcome
See how coding-agent work happened, connect it to review and delivery, and improve workflows using accepted outcomes instead of activity counts.
Read why this exists: The Agent Observability Gap
Session evidence to engineering outcome
Preserve how the work happened, connect it to review and delivery, and improve the workflows that matter.
Keep the session story
Capture hook-visible and OTel-visible tool calls, file operations, commands, errors, retries, duration, and cost. Collection gaps stay visible.
- Ordered timeline : Replay events and phases without reading a long transcript
- Failure context : See errors, retries, loops, and recovery steps
- Evidence health : Show missing boundaries, late capture, and export failures
- Content controls : Keep content opt-in and redact secrets before export
Follow the work into review and delivery
Link sessions to diffs, commits, pull requests, CI, reviews, deployments, rollbacks, and incidents. Preserve the source and confidence of every link.
- Code outcomes : Diff, commit, pull request, CI, review, and merge
- Delivery outcomes : Deployment, rollback, incident, and recovery
- Honest correlation : Explicit IDs first, confidence-scored heuristics second
- Manual correction : Let teams repair links instead of hiding uncertainty
Compare workflows using accepted outcomes
Understand which task and workflow classes produce reviewable, stable results without turning activity counts into individual rankings.
- Accepted outcomes : Measure what passed review and delivery checks
- Review economics : Track time, comments, rework, and intervention
- Cost per result : Include failed and abandoned sessions in the denominator
- Team-level learning : Compare equivalent workflows, not individual developers
Your traces, your backend
agent-strace exports standard OTLP. Drop it into Grafana, Honeycomb, Datadog, or Prometheus without a custom integration. If your observability stack speaks OpenTelemetry, it works.
See what your agent
forgot mid-session
Claude Code, Cursor, and every other agent framework silently compacts context when the window fills. A constraint mentioned early gets dropped. The agent proceeds without it. Verio is the only tool that shows you exactly what was lost, and whether behavior changed after.
- Token drop detection : Identifies compaction from input token signature. No LLM calls.
- Survived vs dropped : Reconstructs what the agent could see before and after
- High-risk flag : Constraints, requirements, and decisions that didn't survive
- Behavior diff : Did redundant reads or tool loops increase after compaction?
- Pre-compaction checkpoint : Auto-snapshot at 80% fill. Paste back into next session.
OSS core, forever free
The CLI stays open. Paid tiers add shared evidence, outcome correlation, and team workflows.
- Full CLI, all commands
- Self-hosted collector
- VS Code extension
- GitHub Action
- Unlimited local storage
- MIT license
- Everything in OSS
- Shared session replay
- Evidence-health reporting
- GitHub and CI outcome links
- Team workflow analytics
- OpenTelemetry export
- 30-day metadata retention
- Everything in Team
- Custom outcome connectors
- Review and delivery correlation
- Deployment and incident correlation
- Configurable retention
- Aggregated engineering reporting
- SLA and dedicated support
- On-prem or VPC option
The CLI is MIT licensed and will always be free. No feature gates, ever. Read the source.
Up in 30 seconds
One install. Run your agent as normal.
agent-strace captures everything without touching your code.