Relavium

Start as an agent. Ship the workflow. Own every run.

A local-first AI agent platform that turns productive conversations into
version-controlled, multi-agent workflows — on one pure-TypeScript engine.
A product of HodeTech.

Get started · Why Relavium · Architecture · Status · Documentation

Relavium begins where agent work naturally begins: in conversation. Explore a task in a persistent session, keep the flow that proves useful, and graduate it into a reviewable .relavium.yaml workflow. The conversation and the workflow are not separate products — they are two entry points into the same engine, tool registry, model seam, and event stream.

Most agent tools make you choose between a flexible chat and an operable workflow. Relavium treats them as a continuum:

1. Explore in an agent session. Work conversationally with streaming output, tools, model controls, persistent history, and human approval.
2. Promote what works. Export the proven flow into git-native YAML that can be reviewed, changed in a PR, and shared without embedding provider keys.
3. Run it deliberately. Execute locally or in CI with typed events, durable history, human gates, checkpoints, and cost controls.

You can also author the workflow directly; conversation is an on-ramp, not a requirement.

The published CLI is the fastest way to use Relavium. It requires Node.js 22 or newer.

npm install -g relavium

1. Connect a provider. The key is read from stdin and stored in the OS keychain — never passed through argv.

relavium provider add anthropic
printf '%s\n' "$ANTHROPIC_API_KEY" | relavium provider set-key anthropic

2. Start as an agent.

relavium chat

3. Run /export inside the session to create a git-committable workflow. Execute it interactively, or stream NDJSON for CI with --json.

relavium run ./my-workflow.relavium.yaml --json

Prefer to author first? relavium create scaffolds an agent or a minimal workflow; relavium import and relavium export move validated artifacts between projects. See the CLI command reference for the complete surface and the local development runbook to build from source.

The center of Relavium is @relavium/core, a strict TypeScript engine with zero platform-specific imports. It exposes two co-equal entry points:

• AgentSession for conversational, multi-turn work.
• WorkflowEngine for declarative .relavium.yaml execution.

Both reuse the same ToolRegistry, typed event substrate, and Relavium-owned @relavium/llm abstraction. Official provider SDKs are confined to thin adapters; no vendor SDK type crosses the seam. Host packages supply persistence, MCP connections, keychain access, files, processes, and network I/O without making the engine platform-specific. Read the architecture overview or the decision records for the reasoning behind those boundaries.

The CLI is the currently published product surface. Desktop and VS Code integrations, plus managed inference and cloud execution, are under development or planned. The diagram shows the shared-engine topology, not equal release availability.

For exact command behavior and contracts, use the reference documentation rather than this overview.

• No account is required for local BYOK. The CLI runs the engine and stores history on your machine.
• Provider keys do not belong in workflows or committed configuration. Interactive setup stores them in the OS keychain; a documented environment fallback exists for automation.
• Workflows remain ordinary files. They can be reviewed, branched, reverted, and moved without exporting from a proprietary database.
• Network use is explicit. LLM requests go to the provider you configure; optional catalog refreshes and future managed/cloud modes are not hidden prerequisites for local execution.

The binding guarantees live in the product constraints and security standard.

Relavium is under active development. The CLI is published as v0.1.1; the pure engine, agent-session entry point, workflow runtime, inbound MCP client, and CLI management surface are implemented. The current engineering focus is Phase 2.6.5 — Core Reliability Remediation, which hardens the execution core before the next product wave opens.

Status changes quickly, so this README intentionally stays high-level. The canonical source for the exact active wave, completed work, and open reliability obligations is docs/roadmap/current.md.

The full dependency graph and ownership rules live in docs/project-structure.md.

Relavium is a pnpm + Turborepo monorepo. For a first local verification:

corepack enable
pnpm install --frozen-lockfile
pnpm run ci

Use pnpm only — never npm or yarn for workspace development. Start with the local development setup, then read CLAUDE.md or AGENTS.md before making changes.

The canonical documentation is organized by the question you are trying to answer:

Relavium is proprietary software — © 2026 HodeTech, all rights reserved. It is not open source and grants no rights except as expressly stated. See LICENSE for the full terms. For licensing inquiries or commercial-use agreements, contact HodeTech.