Jido Conductor

jido-conductor

Desktop application for managing JIDO autonomous agents. Tauri shell (Rust) with a React frontend and an Elixir agent service backend.

Status

Early development. The Tauri + React shell renders and the Elixir agent service starts, but the two halves communicate over a loopback HTTP API that is partially wired. No packaged releases exist.

Component	State
Desktop shell (Tauri 2 + React 18)	UI scaffolded with shadcn/ui; template gallery, run management pages
Agent service (Elixir + JIDO)	Phoenix API on port 8745; template registry, run worker, SSE log streaming
Conductor.json support	Parser and executor implemented
Tests	1 test config file (test.exs); no test modules
CI	3 workflow files (CI, build-release, semantic-release)
Releases	None published

What it does

1. Users browse and import agent templates (.jido.zip archives with a conductor.json manifest)
2. Configure runs with schema-validated parameters
3. The agent service executes runs in isolated workspaces via setup/run/archive shell scripts
4. Live logs stream back to the desktop UI over SSE
5. Budget tracking and cost management per run

conductor.json format

{
  "name": "my-template",
  "version": "1.0.0",
  "setup": "scripts/setup.sh",
  "run": "scripts/run.sh",
  "archive": "scripts/archive.sh",
  "env": { "API_KEY": "value" },
  "timeout": 3600,
  "budget": { "max_usd": 10.0 }
}

Stack

Layer	Technology	Version
Desktop shell	Tauri (Rust)	2.0
Frontend	React 18, TypeScript, Vite, Tailwind, shadcn/ui	See app/package.json
State management	Zustand	5.x
Agent runtime	Elixir, JIDO framework	1.16+ / jido ~> 1.2.0
Web framework	Phoenix + Bandit	~> 1.7.14
Database	SQLite (dev), PostgreSQL (prod)	ecto_sqlite3 ~> 0.17
Forms	react-hook-form + zod	--

Repository layout

app/                    Tauri + React desktop app
  src-tauri/