RESOURCES · DOCS · AGENT STUDIO · LAUNCH

Launch assets

Published launch narrative, share-ready channel summaries, press-kit asset inventory, and demo scripts for Agent Studio Open.

Open browser IDE All docs

LAUNCH

Agent Studio Open

LOCAL-FIRST

ConnectComposeTracesReplayObserveShip

COMPOSE · TOOL CALL

{
  "tool": "refund_order",
  "order_id": "ORD-1042",
  "dry_run": true
}

TOOLS

TRACE

.ast

P95

812ms

TRACE READOUT

SECTION

Launch

Where this entry sits in the docs index.

READ TIME

12 min

Pace it for a coffee or a coffee break.

SECTIONS

Each one stands alone and is copy-paste safe.

INSTRUMENT READOUT · LAUNCH

THE WALKTHROUGH

What you will actually do.

STEP 01

↳ LAUNCH

Announcement

Agent Studio Open is a local-first IDE for MCP and A2A agents. It turns a failing tool call into a traceable regression by connecting a server, inspecting its manifest, recording the session, replaying the failure, comparing model behavior, importing OTEL spans, and exporting CI evidence from one project folder.

The launch page positions Open as the local-first desktop and browser authoring surface. Hosted collaboration, enterprise governance, and managed review programs are described as separate roadmap tracks, not required dependencies. License and release labels stay evidence-gated.

Canonical page: /open/agent-studio-open.

↳ CHECK

Docs entry: /resources/docs/agent-studio-open.

↳ CHECK

Quickstart: /resources/docs/agent-studio-open/quickstart.

↳ CHECK

Cookbook: /resources/docs/agent-studio-open/mcp-cookbook.

↳ CHECK

Primary CTA: download the local-first app and run the sample MCP replay.

↳ CHECK

STEP 02

↳ LAUNCH

Channel summaries

Developer channels lead with commands, sample servers, replay artifacts, and GitHub Action export. Narrative channels explain why local debugging and production observability need a shared trace record. Every channel points back to the canonical AuraOne page and the repository.

Developer summary: connect a sample MCP server, record a tool call, replay it, compare model behavior, and export CI evidence.

↳ CHECK

Market summary: local debug sessions become durable agent evidence before production rollout.

↳ CHECK

Community title: Agent Studio Open - local-first IDE for debugging MCP and A2A agents.

↳ CHECK

Security note: no account is required, telemetry is off by default, and projects stay on disk unless explicitly exported.

↳ CHECK

STEP 03

↳ LAUNCH

Press kit

The press kit includes AuraOne Open logo guidance, transparent app icons, the 1200x630 Open Graph image, the one-page overview copy, demo captions, and screenshots for the six primary product surfaces.

Connection panel with stdio server.

↳ CHECK

Manifest Inspector with capability and risk findings.

↳ CHECK

Compose surface with JSON and form views.

↳ CHECK

Replay diff across two model versions.

↳ CHECK

Observe span timeline from OTEL import.

↳ CHECK

Ship export surface for GitHub Actions and JUnit.

↳ CHECK

STEP 04

↳ LAUNCH

Demo scripts

The 90-second hero demo shows the whole loop once. The 5-minute walkthrough explains each surface. The 15-minute deep dive adds A2A, OTEL, sandbox, provider keys, and CI export.

90 seconds: connect sample server, inspect manifest, record, replay, export trace card.

↳ CHECK

5 minutes: add risk scan, model compare, GitHub Action export, and browser edition boundary.

↳ CHECK

15 minutes: add A2A contract test, Phoenix import, OTLP receiver, sandbox rejection, provider key smoke check, and PR comment export.

↳ CHECK

← PREVIOUS

Troubleshooting

LAUNCH

Next time, it's already a replay.

The path you just read becomes the path you can repeat. One trace, one artifact, one gate the next release has to clear.

Open browser IDE GitHub repo