Operator

Operator is Conduit’s workspace assistant. It helps you create agents, write Skills, inspect data, understand escalations, and manage configuration from the current workspace context. Open Operator from the main workspace sidebar. You can also open the Operator sidebar from V3 build pages.

​

Operator Versus Agents

Operator is not the same thing as a deployed customer-facing agent. It can help you build and debug agents, but a specific agent’s behavior is still controlled by that agent’s Persona, Skills, Tools, Behavior, and Settings.

​

Full-Page Operator

Use the full-page Operator when you want a focused workspace assistant session. Operator can keep thread history so you can return to previous work. Common tasks:

• Create a new chat agent from a plain-language description
• Draft or revise Skills
• Inspect Knowledge gaps or conflicting content
• Help reason about escalations
• Generate reports or exports when your workspace has the required access
• Navigate you toward the right configuration page

​

Operator Sidebar

The Operator sidebar appears alongside many build surfaces. Use it when you want help while editing the page you are already on. Examples:

• Ask Operator to turn a rough policy into a Skill while you are on the Skills page
• Ask what an agent needs before you publish it
• Ask for a Knowledge article draft while reviewing a source
• Ask how a tool should be described before enabling it for an agent

​

Operator Settings

Open Operator settings from the Operator header. Operator tool access is separate from agent tool access. If Operator needs to inspect a system, give Operator the right tool. If a deployed agent needs to take an action, give that agent the right tool.

​

Good Operator Requests

Be explicit about the workspace artifact you want changed or inspected.

​

Safety

Operator can help configure your workspace, but you should still review staged changes before publishing agents, enabling tools, deleting sources, or changing automation behavior.