开源AI工作流：Jido工作室

1. Install the dependency

def deps do
  [
    {:jido_studio, "~> 0.1.0"}
  ]
end

Then fetch dependencies:

mix deps.get

Installation

Add jido_studio to your dependencies:

def deps do
  [
    {:jido_studio, "~> 0.1.0"}
  ]
end

Setup

Use this sequence for a clean first-time setup.

Setup Assistant and Profiles

After mount, Studio surfaces a Setup Assistant on Home with a re-entry card in Settings. Checks cover:

• runtime connectivity/reachability
• persistence durability mode
• realtime event-driven vs polling fallback
• optional chat provider key presence
• smoke-path readiness

Profiles are guidance-only presets shown in-app:

• Local Dev Fast Start
• Chat Demo Showcase
• Team Durable Ops

Apply profile snippet means show/copy snippet text with "What changes?" and rollback notes. Studio does not mutate host config files.

Runtime Installation Modes

Quick Start

Mount the studio in your Phoenix router:

```elixir

Non-Chat Example Recipes

Studio Playground seeds non-chat examples under dev/studio_playground/lib/studio_playground/demo_agents/non_chat_agents.ex:

• StudioPlayground.DemoAgents.SignalRunnerAgent — Signal-first route execution example for introspection and guarded dispatch
• StudioPlayground.DemoAgents.DeviceControlAgent — Schema-driven control flows with richer action payloads

These examples are registered in dev/studio_playground/lib/studio_playground/demo_agents.ex so they appear in the active/discovered lists by default.

Optional Extensions

Studio supports optional package-specific admin pages through extensions. Built-in extension routes are only compiled when their backing package is available.

Current built-in extension:

• jido_messaging -> Messaging / Rooms page

Optional extension modules can also be registered from the host app:

config :jido_studio,
  extension_modules: [MyAppWeb.Studio.Extensions.Custom]

For jido_messaging room listing, you can provide an explicit provider if your API differs:

config :jido_studio,
  messaging_room_provider: {MyApp.MessagingAdmin, :list_rooms}

2. Configure Studio

Set your Jido supervisor module so Studio can show running instances (without this, Studio still shows discovered modules only):

```elixir

config/config.exs

config :jido_studio, jido_instance: MyApp.Jido

Optional override for multi-runtime installs:

When `:jido_instances` is present, Studio shows a runtime selector in the sidebar.
When it is absent, Studio derives a single runtime from `:jido_instance` and keeps the UI simplified.

Default observability persistence is ETS and needs no extra setup:

Optional next-wave debug/observability defaults:

Studio now ships a built-in Presence default (`JidoStudio.Presence`) so viewer tracking works out-of-the-box.
If your host app already has its own Presence module, you can override it:

4. (Optional) Use Postgres persistence for traces/spans

Switch the persistence adapter:

config :jido_studio, :persistence,
  adapter: JidoStudio.Persistence.Ecto,
  opts: [repo: MyApp.Repo, prefix: "public"]

Copy the provided migration template into your host app and run:

mix ecto.migrate

Template:

• priv/ecto/migrations/20260215000000_create_jido_studio_persistence_tables.exs

config/config.exs

config :jido_studio, auto_start_runtime: false