Guide

How do you get value from Studio in under five minutes?

runtime:iversen node:all

What this page is for: choose a guided workflow, follow in-product coachmarks, and complete setup, interaction, and triage paths without leaving Studio.

Why Discovered Counts Can Be High

Studio separates discovered modules from running instances, so module counts are often higher than currently active runtime processes.

  • Discovered modules: compiled agent modules.
  • Running instances: started processes right now.
  • Active instances: running instances in your filters.
  • Scope: `runtime` + `node` change all counts.

Starter Agent

Jido Studio Beginner

Why this starter: Built-in Studio beginner agent (deterministic, no API keys required).

This opens the module with `start=1`; you still confirm Start Instance manually.

First 5 Minutes

5 min

Get oriented quickly: health, attention items, fleet state, diagnostics path, and setup status.

5 steps

  1. 1. Start With Fleet Health
  2. 2. Check Attention Needed
  3. 3. Open Active Instances
  4. 4. Use Timeline For Root Cause
  5. 5. Confirm Setup Re-entry

Not started

Setup + First Interaction

6 min

Walk through setup checks and the first safe interaction path for new operators.

6 steps

  1. 1. Validate Setup On Home
  2. 2. Re-test Setup In Settings
  3. 3. Set Live Ops Scope
  4. 4. Pick An Active Instance
  5. 5. Understand Discovered vs Running
  6. 6. Launch The Starter Module

Not started

Incident Triage

4 min

Follow the warning-to-root-cause path used in on-call workflows.

4 steps

  1. 1. Start From Attention
  2. 2. Open Timeline Mode
  3. 3. Choose Trace Scope
  4. 4. Inspect Waterfall And Span Details

Not started