You orchestrate the agents. Who closes the runtime loop? In this demo, an agent shipped a hidden TypeError — watch Dstl8 surface the cause and hand the fix back to your agent.
Demo telemetry, running through the real pipeline — nothing to set up. See the diagnosis below, then connect your own runtime in three steps to get findings on your code.
✓Debug AI code
2Where’s it running?
3Hook up the CLI
4Connect MCP
Click through all four steps to see the full loop — Dstl8 finds it, your agent fixes it.
Möbius is analyzing the runtime…
Ingesting demo OTLP stream
Scanning logs and traces…
Anomaly detected — recurring TypeError in store_event
Correlating across services and deploys…
Root cause identified — assembling incident
Incident · demo data MAJOR
TypeError in store_event — index() missing entity_class
index() is called without its required entity_class argument after the create_or_update refactor, so store_event() raises on every call. Recurring across three services. Introduced by an agent-authored deploy.
Evidence ← what we detected
[2026-06-20 00:02:33][WARNING]app.events.services.store_event():41
action=store_event · type(e)=<class ‘TypeError’>e=TypeError(“index() missing 1 required positional argument: ‘entity_class'”)related:TypeError(‘issubclass() arg 1 must be a class’) · ×97
What Möbius correlated ← why it matters
·97 occurrences in data-service-prod, recurring in report-worker-prod and upload-handler-prod
·Same root cause: sibling issubclass() arg 1 must be a class means a non-class is reaching index()
·Next layer: downstream create_or_update failures & ConflictException — fixing the missing arg likely surfaces these
Handoff ← what your agent needs
Cause found. Context ready for your agent — Dstl8 finds it, your agent writes the fix.
You: is this the same bug across all three services?
Möbius: Yes — same root cause. After the create_or_update refactor, index() is called without entity_class, so store_event() raises TypeError wherever it’s used. The sibling issubclass() arg 1 must be a class is the same problem one level down. Fix the missing arg first, then watch the create_or_update / ConflictException cascade. Hit Copy for AI to hand it off.
Next
Want this on your code?
You just watched Möbius find and explain a bug with zero setup. Point it at your own runtime and it does the same on your code — in about a minute.
Install the CLI, then dstl8 tap wraps your log source, handles auth, and streams it in — token’s already in it. Run it against staging first if you like.
$ brew install control-theory/dstl8/dstl8
$ dstl8 tap –token dstl8_tr1al_x839 — kubectl logs -f deploy/checkout
Add the MCP server and the diagnosis shows up where you work — your editor — instead of here.
> what broke in prod since my last deploy?Möbius (via Dstl8 MCP): 1 regression since deploy 4412 —
TypeError in store_event, index() missing entity_class.
Cause, evidence, blast radius attached. Want me to patch it?
The agent fixes it faster, more accurately, and with less token burn — it skips re-deriving the diagnosis you already handed it.
Copied — now hand it to your agent
Paste it into Claude Code (or Cursor / Codex) and watch the agent write the fix. That’s the core Dstl8 loop: Dstl8 finds the cause, your agent fixes it — with the context already attached, so it skips the investigation.
claude — ~/work/dstl8-demo-dev
No paste needed — the agent pulls this through the Dstl8 MCP server. This is the same incident, fetched automatically.
14-day free trial · No credit card · Setup in 5 minutes
Questions
Before you start.
How long does setup take?
Under 5 minutes. brew install control-theory/dstl8/dstl8 for the terminal, or point your OpenTelemetry collector at Dstl8. No agents to deploy, no dashboards to configure.
Do I need a credit card to start?
No. The 14-day free trial gives you full platform access with no credit card required.
What does it integrate with?
Vercel, Supabase, Railway, AWS, Kubernetes, Cloudflare, OpenTelemetry, GitHub, and 50+ sources — plus Claude Code, Cursor, Codex, and Copilot via MCP.
Is there a free, open-source option?
Yes. Gonzo is our MIT-licensed terminal log analysis tool — brew install gonzo, no account needed. Dstl8 adds continuous analysis and Möbius AI root cause on top.
How is this different from Datadog?
Dstl8 distills signal at the source instead of charging you to ingest everything, and Möbius AI hands you root cause cited to the log line instead of a dashboard to interpret yourself.
Get started
Find what broke in your next five minutes.
Free 14-day trial. No credit card. Full platform access.
