Docs · v1.4

Routix in 15 minutes.

This is the practical guide we hand new design partners. By the end you'll have observed your team, mined three patterns, and shipped your first agent behind a review queue.

1. Install the observer

The observer is a browser extension plus a thin desktop helper. Both are open-source on our GitHub. Your admin pushes the install via your MDM (Jamf, Kandji, Workspace ONE).

Once installed, employees see a one-time consent prompt. Capture is paused until they accept; admins can re-show the prompt at any time.

routix · CLI

$ routix install --tenant acme --consent strict
→ pushed to 142/142 endpoints · 100% consented
$ routix observer status
→ healthy · 142 sensors · 0 paused · 18min since last sync

2. Your first agent

After ~5 days of capture, the pattern miner has enough signal to propose your first agents. Open the Patterns view, sort by hours-saved/week, and pick one.

Routix generates a complete workflow definition — including tool calls, prompts, retry policy, and verifier checks — that you can read, edit, or accept as-is.

The first agent should be one you'd be comfortable shipping behind a review queue from day one. Pick observability over autonomy. The verifier will earn its independence.

3. The review queue

Every agent ships first in shadow mode (Routix plans but doesn't act). After 100 successful shadow runs, promote to review (acts, human signs off each output). Once accuracy clears 95%, promote to autonomous with abstention.

Patterns

A pattern is a recurring, multi-step, cross-app sequence with stable entities. The miner uses sequence clustering (locality-sensitive hashing) plus entity resolution across apps to build the candidate list.

Agents

An agent is a state machine. Nodes are plan / call / verify / write / wait / escalate. Edges are conditions on tool outputs and verifier confidence. Routix compiles agents to Temporal workflows for durability.

The verifier

Independent model, separately trained on customer-corrected outputs. Its only job is to check the executor's work. It abstains when confidence drops below the agent's threshold, sending the output to the review queue instead of acting.

Workflow DSL

Workflows are TypeScript. We don't ship a proprietary YAML — it ages badly and locks customers in.

workflows/renewal-brief.ts

import { defineWorkflow, sf, slack } from "@routix/sdk";

export default defineWorkflow({
  name: "renewal-brief",
  trigger: cron("MON 09:00"),
  async run(ctx) {
    const renewals = await sf.query("renewals next 30 days");
    const drafts   = await ctx.draft("renewal_brief", renewals);
    const verified = await ctx.verify(drafts, { threshold: 0.92 });
    return slack.post("#renewals", verified);
  }
});

Custom tools

Register any HTTP API as a tool with a JSON schema. Routix wraps it with authz, rate limits, tracing, and a default eval set. MCP servers are auto-registered.

Observability

Every run emits OpenTelemetry traces. Export to Datadog, Honeycomb, or your warehouse. Dashboards for cost, latency, accuracy, abstention rate, and time-saved are shipped by default.

Last updated: 22 May 2026 · Suggest an edit →