Docs Try Workflows Get started
RIGLANE

A workflow control plane for AI agents.

Declared steps. Hard gates between them. Runs you can prove — who did what, what was checked, who signed off. The engine runs on the agent host you already use; no LLM API key, no cloud.

$ npm install -g riglane
Anatomy of a run: the engine owns the control flow — steps pass gates, the trace records everything, a human gate delivers its question to the Inbox and the answer resumes the run.
Identical behavior on Claude CodeCursorCodexOpenCodeGitHub CopilotGemini CLI

Gates, not vibes

A step cannot be stamped complete unless its gate actually passed — schema checks on every handoff, script verdicts, human sign-off. The rules live in the engine, not in the prompt.

Runs you can prove

Every step, tool call, gate verdict and retry lands in a trace you can open and audit. State is on disk: runs survive crashes, restarts and closed terminals.

Humans in the loop, durably

A decision waits in the Inbox for hours or days without losing state — the agent proposes, the engine holds, the person disposes. All three leave evidence.

Workflows worth sharing

The catalog shares workflows as pointers with byte-locked capability inventories — you see every command a workflow can run before you install it.

See it working, right now

The Workflow Studio, loaded with a real twelve-role research workflow — frozen mid-run, waiting on a human signature. Click through the graph, the live trace and the Inbox.

Open the demo →