Flue

Create a Flue project

mkdir my-agent && cd my-agent
npm init -y
npm pkg set type=module
npm add "@flue/runtime@npm:@rivet-dev/labs-flue-runtime"
npm add --save-dev "@flue/cli@npm:@rivet-dev/labs-flue-cli"
npx flue init --target node

Install the integrations

npm add @rivet-dev/flue @rivet-dev/agentos @rivet-dev/agentos-flue rivetkit

• @rivet-dev/labs-flue-*: Rivet-maintained preview builds of Flue’s proposed extension APIs.
• @rivet-dev/flue: Runs Flue agents and workflows as Rivet Actors.
• @rivet-dev/agentos: Provides the isolated VM actor.
• @rivet-dev/agentos-flue: Connects Flue’s sandbox API to agentOS.

Register agentOS with the Rivet target

Create actors.ts:

import { agentOS, setup } from "@rivet-dev/agentos";

const vm = agentOS({
	// Configure software, permissions, mounts, and resource limits here.
});

export const registry = setup({
	use: { vm },
});

Update flue.config.ts:

import { defineConfig } from "@flue/cli/config";
import { rivet } from "@rivet-dev/flue";

export default defineConfig({
	target: rivet({ actors: "./actors.ts" }),
});

The generated Flue server adds its agent and workflow actors to this registry. It keeps Flue’s native router as the public HTTP service; the Rivet target only selects and hosts the durable actors behind those routes.

Use agentOS as the Flue sandbox

Create agents/assistant.ts:

import { type AgentRouteHandler, createAgent } from "@flue/runtime";
import { agentOSSandbox } from "@rivet-dev/agentos-flue";
import { registry } from "../actors.js";

export const route: AgentRouteHandler = async (_context, next) => next();

export default createAgent(() => ({
	model: "anthropic/claude-sonnet-5",
	instructions:
		"Help the user work in /workspace. Use filesystem and shell tools when asked.",
	sandbox: agentOSSandbox({ actor: "vm", registry }),
}));

Set the provider key required by your model, such as ANTHROPIC_API_KEY, in .env.

Run Flue

npx flue connect assistant local

Flue builds the Rivet target, starts the local Rivet engine, and connects to the assistant/local actor.

Ask it to use both filesystem and shell operations:

Write hello from Flue to /workspace/hello.txt, run wc -c /workspace/hello.txt, then read the file back.

Reconnect to assistant/local and ask it to read the file again. The same Flue context reconnects to the same agentOS actor and persistent filesystem.

Deploy

By default, Rivet stores actor state on the local file system.

To scale Rivet in production, follow a guide to deploy to your hosting provider of choice: