RESOURCES · DOCS · AGENT STUDIO · LAUNCH

Launch assets

Announcement copy, dev.to and Substack cross-post notes, press kit contents, demo scripts, and community-post drafts.

SECTION
Launch

Where this entry sits in the docs index.

READ TIME
12 min

Pace it for a coffee or a coffee break.

SECTIONS
4

Each one stands alone and is copy-paste safe.

INSTRUMENT READOUT · LAUNCH
THE WALKTHROUGH

What you will actually do.

STEP 01
LAUNCH

Announcement

The launch headline is direct: Agent Studio Open is a local-first IDE for MCP and A2A agents. The long-form announcement should lead with a real debug loop, then show replay, model comparison, OTEL ingest, and CI export.

The announcement should avoid commercial upsell language. Agent Studio Cloud, Enterprise, and Programs are future roadmap tracks and must be named as proposed, not shipped.

01

Open with the pain: Inspector confirms a tool exists but does not turn a failure into a regression.

↳ CHECK
02

Show a 60-second path from sample MCP server to trace card.

↳ CHECK
03

Include screenshots of Manifest Inspector, Compose, Trace Browser, Diff, Observe, and Ship.

↳ CHECK
04

Close with MIT license, GitHub link, docs, cookbook, and design-partner ask.

↳ CHECK
STEP 02
LAUNCH

Cross-post copy

dev.to should be technical and command-forward. Substack should be narrative and market-positioned. Both point back to the canonical AuraOne announcement and GitHub repository.

01

dev.to: include install commands, sample MCP server, replay artifact, and GitHub Action export.

↳ CHECK
02

Substack: explain why local debug tooling is different from production observability.

↳ CHECK
03

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

↳ CHECK
04

Reddit: lead with no account, local-first, MIT, and sample servers.

↳ CHECK
STEP 03
LAUNCH

Press kit

The press kit should contain an SVG logo lockup, transparent PNGs, six screenshots, a 1200x630 OG image, one-page PDF, founder quote, 90-second video link, and boilerplate.

01

Screenshot 1: connection panel with stdio server.

↳ CHECK
02

Screenshot 2: manifest inspector with risk findings.

↳ CHECK
03

Screenshot 3: compose surface with JSON and form views.

↳ CHECK
04

Screenshot 4: replay diff across two model versions.

↳ CHECK
05

Screenshot 5: Observe span timeline from OTEL import.

↳ CHECK
06

Screenshot 6: 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.

01

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

↳ CHECK
02

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

↳ CHECK
03

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

↳ CHECK
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.

Launch assets | Agent Studio Open Docs