Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/withastro/flue/llms.txt

Use this file to discover all available pages before exploring further.

Connectors adapt third-party sandbox providers into Flue’s SandboxFactory interface. They are not npm packages — they are small TypeScript files that your AI coding agent writes into your project.

​
How connectors work

When you run flue add <name>, the CLI fetches a markdown file containing connector installation instructions and pipes it to your coding agent. The agent reads the instructions and writes a TypeScript adapter file into your project. The adapter file wraps an already-initialized provider sandbox into Flue’s SandboxFactory interface. You create and own the sandbox lifecycle; the connector just adapts it. 
flue add                              # list available connectors
flue add daytona | claude             # install daytona connector via claude
flue add daytona | opencode           # or via opencode
flue add daytona | codex              # or via codex
flue add daytona | cursor-agent       # or via cursor-agent
When run by a human in a terminal, flue add prints a short copyable recipe. When run by an agent (or with --print), it pipes the full markdown instructions for the agent to act on.

​
Where connector files live

Connectors follow the same source layout convention as the rest of your Flue project:
  • .flue/ layout — ./.flue/connectors/<name>.ts
  • Bare layout — ./connectors/<name>.ts
If .flue/ exists at your project root, Flue uses the .flue/ location. Otherwise it uses the bare layout. The two never mix.

​
You own the sandbox lifecycle

Connectors are pure adapters. They never call sandbox.delete(), sandbox.terminate(), or sandbox.kill(). You create the sandbox, you decide when to destroy it. This makes it easy to reuse sandboxes across sessions or manage their lifetime from your orchestration code.

​
Building a connector for any provider

If a connector doesn’t exist for your provider yet, pass the provider’s docs URL as the starting point: 
flue add https://provider.dev --category sandbox | claude
Flue fetches the generic sandbox connector spec and pipes it to your agent along with the URL. The agent reads the spec and the provider’s docs, then builds a conformant SandboxFactory adapter from scratch.

​
Available connectors

Daytona

Full Linux containers with persistent filesystem, git, Node.js, and a declarative image builder. Best for coding agents and full dev environments.

E2B

Firecracker microVMs with fast startup and Python/Node.js support. Best for ephemeral code execution agents.

Cloudflare

Native container support inside Cloudflare Workers via @cloudflare/sandbox. Each session gets its own isolated Linux container.

Build your own

Implement SandboxApi for any provider. Full guide with the complete connector template and the SandboxFactory contract.

Build docs developers (and LLMs) love

Get started for freeTalk to us