Multi-surface AI agent workflow platform — a product of HodeTech.
With Relavium you can start as a conversational agent, graduate to workflows, or
author workflows directly — a chat session and a git-committable multi-agent,
multi-model .relavium.yaml workflow are two entry points to the same engine.
Run them across a Tauri desktop app, a VS Code extension, and a CLI —
local-first in Phase 1, with cloud execution and a control-plane portal in
Phase 2. The engine is a pure-TypeScript package shared by every surface,
and multi-provider LLM access goes through Relavium's own @relavium/llm
abstraction over the official provider SDKs (no Vercel, no LangChain).
The canonical documentation lives in docs/ — start at
docs/README.md, which is organized by the kind of question each
section answers.
| Start here | |
|---|---|
| Vision · Product constraints · UVP | What and why |
| Tech stack · Project structure | What it's built with |
| Architecture · Decisions (ADRs) · Reference | How it works |
| Roadmap · Standards | Where it's going, and the rules |
Phase 1 — engine and LLM in progress; milestone M1 (LLM seam proven) reached (PR #9,
2026-06-07). Phase 0 — Foundations (milestone M0, 2026-06-04) landed the Turborepo + pnpm
monorepo, the strict toolchain + GitHub Actions CI, @relavium/shared (the full Zod contract
set), the no-vendor-type seam fence, and @relavium/db. Phase 1 then landed
@relavium/llm: the provider-agnostic
LLMProvider seam and all three adapters (Anthropic; the OpenAI-compatible adapter serving
OpenAI + DeepSeek; Gemini), passing one shared conformance suite behind the frozen seam with no
vendor type crossing it (PR #7–#9), followed by the ADR-0031 multimodal seam-shape amendment
(1.AD) — the media content/stream union members, the per-modality capability matrix, and the
reserved generator methods, landed shape-only before the seam's exhaustive consumers exist
(PR #11, 2026-06-10). The seam's last policy layer — the FallbackChain runner (1.K) — then landed
(PR #13, 2026-06-11), completing the LLM lane. The @relavium/core engine lane has since landed the
WorkflowYAMLParser (1.L, PR #14), the {{ … }} interpolation engine + parse-time
secret-taint gate (1.L2, PR #15), and the DAG builder + RunPlan (1.M) together with the
QuickJS-wasm expression sandbox (1.AB) (PR #16, 2026-06-13) — all with zero platform imports.
The run loop (1.N — WorkflowEngine + RunEventBus) landed (PR #17, 2026-06-13), completing
milestone 1.m3 (parse → DAG → run loop emits the canonical event stream); the built-in
ToolRegistry (1.T, a 1.m4 component) landed alongside it; the AgentRunner (1.O —
per-node LLM execution behind the seam) landed (PR #18, 2026-06-14); and the node-type handlers
(1.P — the six non-agent handlers behind a dispatching executor) landed (PR #20, 2026-06-14), followed by
the human gate (1.Q) + checkpoint/resume (1.R, PR #22), node retry (1.S, PR #24), and the
pre-egress budget governor (1.AC) together with the agent-first AgentSession entry point (1.V) —
both landed in PR #26 (2026-06-16). With the budget governor in, milestone 1.m4 is complete; then the
end-to-end Node harness (1.U) landed (PR #27, 2026-06-16) — 🎯 reaching milestone M2: the engine runs
end-to-end (live streaming + checkpoint + cross-process resume + retry + provider failover), completing the
Phase-1 engine critical path. The remaining Phase-1 work is additive (the agent-first sub-spine — session
events 1.W ✅ (PR #28) + persistence 1.X ✅ (PR #29) + session checkpoint/resume 1.Y & export-to-workflow 1.Z ✅ (PR #30, 2026-06-17) + the 1.AA chat-regression harness ✅ (2026-06-17), completing 1.m5 — and the
multimodal sub-spine, whose first step — media-input adapters + the shared SSRF policy primitive 1.AE ✅ (PR #32, 2026-06-18) — landed); Phase 2 (the CLI) is unblocked. See
docs/roadmap/current.md for live status.