Connect
Start with a local stdio server, a remote SSE or HTTP MCP endpoint, an A2A card, or an imported OTEL trace.
→A local-first IDE for MCP and A2A agents. Connect, inspect, record, replay, compare model behavior, ingest OTEL spans, and export regression suites to CI.
stdio, SSE, HTTP, WebSocket. Cards, manifests, tools, risk findings.
Record the path. Mock the tool outputs. Compare across models.
GitHub Action, JUnit, PR comment, trace card, intake packet.
Connect the server. Replay the path. Ship the regression. The trace stays on disk.
Start with a local stdio server, a remote SSE or HTTP MCP endpoint, an A2A card, or an imported OTEL trace.
→Record the agent path. Replay it with mocked tool outputs. Compare per-turn and per-tool across model versions.
→Generate a GitHub Action, JUnit report, PR comment, trace card, or AuraOne intake packet for the next reviewer.
Repo-ready files. No hosted account. The next reviewer can pick the run back up from disk.
Portable Markdown and JSON for one agent run: tools, retries, data touched, outcome, failure mode.
Every failed tool call becomes a deterministic replay the next release must clear.
A drop-in workflow file that runs the replay set on every push and posts findings to the PR.
Standard XML for the CI dashboard your team already runs. No new viewer required.
Signed .auraonepkg with a privacy preview before handoff to AuraOne reviewers.
Local, file-based, git-friendly criterion-level authoring.
See the page →Scrub synchronized sensor streams. Cluster failures. Export reviewed subsets.
See the page →Twelve installable packages. mcp-risk-linter, a2a-contract-test, tool-call-replay, more.
See the page →The debug loop, your tool calls, your replay artifacts — all on disk. No telemetry by default.