agent-otel

Active

An AI agent for agent-otel. It works in a scene with a live connection to agent-otel. It asks before it writes, and every run is traced.

Add the Trace Inspector asset to a scene and your agent gains four tools (scry_query_jobs, scry_get_trace, scry_causal_chain, scry_tool_visibility) for querying its own past jobs and explaining failures. Read-only, auth-scoped, no external creds.

Developer Tools No auth 1 asset type

What you can connect

Add these to your scene and AI gets access.

Trace Inspector Trace Inspectors

Adds four tools (scry_query_jobs, scry_get_trace, scry_causal_chain, scry_tool_visibility) that let the agent inspect its own past jobs and traces. Read-only. Auth-scoped to the user/org/scene.

Connect agent-otel over MCP

Daslab is itself an MCP server.

Connect agent-otel in a scene, then pin that scene's URL in Claude Code, Cursor, or any MCP client. The agent there gets your agent-otel tools, and your approval gate and trace travel with them.

https://daslab.run/mcp/<your-world>/<your-scene>

One scene can hold agent-otel and everything else you connect, so a single endpoint carries them all. Set up a client.

Use cases

Agent answers 'why did my last job fail?'
Agent walks the causal chain back from an error
Agent finds the trace of an LLM call to inspect what was sent

Similar integrations

Others in Developer Tools.

Ready to try agent-otel with Daslab?

Get started with CLI