Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.operator.io/llms.txt

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

Operator is the agent on the other side of every conversation at operator.io/chat. You describe what you want in plain language. It spins up instances, writes skills, manages secrets, schedules automations, and reports results, all without leaving the chat window.

​
How it works

You type a goal. Operator decides the steps, picks the tools, and executes them. It has access to every dashboard section: creating instances, browsing files, granting secrets, reading activity logs, writing skills, setting up automations, and sending messages into the agents running on those instances. 
Direct a 10 minute short film. Script the story, storyboard with FLUX,
generate shots with Sora and Veo, score it with Suno, and cut a final
edit with burned captions.
Operator lays out the approach, creates an instance for the project, writes the skill that captures the plan, and starts producing output. It checks in when it needs a decision and keeps going on its own when the next step is obvious.

​
Conversations persist

Each chat keeps its full history. Operator remembers which instance it created for which project, what it’s already produced, what’s in flight, and what failed last time. Come back a week later and pick up where you left off: 
Clone the top 2 storyboards and generate four more variants of each with
warmer lighting. Keep the original character designs.

​
What Operator can do

CategoryActions
InstancesCreate, delete, restart, read logs, browse files
SkillsWrite, install, update, preview before deploying
SecretsCreate, grant, revoke, scope per instance
ConfigRead and update any instance setting
AutomationsSchedule cron jobs on an instance
ChannelsWire Telegram or Discord to a specific agent
FleetOperate across multiple instances in a single turn

​
Mentioning files and agents

Type @ in the chat to mention a specific file or agent. The popover searches across every active instance and inserts a visible chip into the message. Operator routes the work to whichever instance owns the mention: 
@mulholland.jpg pull the color palette from this image and apply it to
the scene board for scene 4 on @daniel.
See Files for how uploads and references work together.

​
Scheduling vs triggering

Two ways to run Operator without being at the keyboard:

Automations

Cron-based jobs that fire on a schedule. The agent inside the target instance runs the prompt.

Channel messages

Send a message to a connected Telegram or Discord bot and the agent responds.

Quickstart

Deploy your first agent from chat.

Agents

Build, test, evolve lifecycle for a single agent.

Skills

How Operator captures and reuses approaches across chats.