RESOURCES · DOCS · AGENT STUDIO · MENTAL MODEL

Concepts

Connections, sessions, replays, regression banks, trace cards, and intake packets.

Talk to AI Labs All docs

SECTION

Mental model

Where this entry sits in the docs index.

READ TIME

7 min

Pace it for a coffee or a coffee break.

SECTIONS

Each one stands alone and is copy-paste safe.

INSTRUMENT READOUT · MENTAL MODEL

THE WALKTHROUGH

What you will actually do.

STEP 01

↳ MENTAL MODEL

Core objects

A connection is a configured MCP server, A2A card, OTEL file import, or provider key profile. A session is a recorded interaction with ordered turns, tool calls, outputs, costs, timings, and attachments.

A replay re-runs a saved session against deterministic tool outputs. A regression bank is a curated set of replays that should run in CI before a server or model upgrade ships.

Manifest Inspector shows the raw protocol surface before an agent touches it.

↳ CHECK

Compose is the controlled workbench for schema-backed tool calls and agent loops.

↳ CHECK

Trace Browser is the local memory of sessions, imports, spans, and failed cases.

↳ CHECK

Ship exports GitHub Actions, JUnit XML, PR comments, trace cards, and AuraOne intake packets.

↳ CHECK

STEP 02

↳ MENTAL MODEL

Local-first boundary

Trace contents stay on the machine unless the user explicitly exports a file, posts a PR comment, or packages an AuraOne intake packet. Telemetry is off by default and excludes trace payloads.

← PREVIOUS

60-second quickstart

MCP cookbook

MENTAL MODEL

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.

Talk to AI Labs All docs