Skip to content

Operator and Agents (Preview)

The LyftData Operator is an AI agent that runs inside the LyftData server on the embedded AI runtime. You ask it for operational help in the LyftData UI, and it works through LyftData tools on your behalf. This is separate from the client-hosted MCP server, which lets an external assistant connect to LyftData.

  • Home is the central Operator surface. The composer reads Ask LyftData Operator or search. Conversations show the tool calls the Operator made as receipts, and you can stop a run that is still working.
  • Agents (/agents) lists agent requests, proposals, roles, and returned work. It has Requests, Proposals, Roles, and Packs tabs.
  • Settings → AI integration (/settings/integrations/ai) is where provider accounts are configured and where each AI feature is turned on or off.

The Operator requires the ai-operator license feature. That feature depends on ai-runtime, the embedded AI runtime, and takes effect only when both are granted. Current Community+, Standard, and Enterprise offers include them; Community Edition does not. Your signed license is authoritative. See Licensing.

A license is necessary but not sufficient. You also need a configured provider account and recorded consent.

  1. Configure a provider account. In Settings → AI integration, a platform admin adds a provider account. You can use an API key or sign in with ChatGPT (device sign-in or browser sign-in). Then choose a model and verify the connection. Provider usage may incur charges with that provider.
  2. Record Operator consent. Setting up a connection does not turn on either AI feature. Each one needs its own recorded consent. LyftData asks for Operator consent when you submit your first Operator request. Only an admin can record consent. Consent applies to one tenant and environment and to the provider accounts listed in the dialog.

The consent dialog asks you to confirm that your Operator prompts, conversation history, relevant configuration, identifiers, evidence, and tool-derived context can leave this installation and go to the listed provider accounts. The dialog says this is not a guarantee of redaction or metadata-only transmission.

Once you consent, this request and later requests within the same disclosed scope are sent without asking again. Operator consent does not turn on Data Awareness, and it does not grant separate write or effect approvals.

To withdraw consent, open Settings → AI integration → Independent AI controls and choose Disable LyftData Operator. Disabling the Operator retires its queued work and signals known in-flight runs to cancel. It does not change Data Awareness.

  • Cancelling provider work that is already running is best effort, so some outcomes may remain uncertain.
  • Data that has already been transmitted cannot be recalled.
  • If the control shows Off · cleanup pending, no new work is authorized until cleanup finishes. Use Retry withdrawal to settle the remaining local work.
  • It acts as you. An Operator run uses the signed-in user’s LyftData permissions. It can only use tools that your account is allowed to use, and the server sets the tenant, environment, and provider binding. Choosing the Operator does not grant a role or widen your tenant scope.
  • Ordinary writes use ordinary authorization. If you can perform an operation yourself, the Operator can perform it for you under the same permission checks. LyftData does not add a separate approval step for those operations.
  • Some effects need your approval. When a tool requires approval, the run pauses and links you to Governed effect review on the Agents page. The review shows the target and the proposed change, and you choose Approve effect or Reject effect. Your decision applies only to the proposal on screen. If the proposal changes, it must be reviewed again, and LyftData checks current authority before any effect runs. If the target or change details are unavailable, do not approve.
  • Proposals are validated and approved before they are applied. On the Proposals tab, you can approve a proposal only after it has been validated, and you can apply it only after it has been approved. Use Apply preview to check the change first. Applying asks for confirmation.
  • Evidence previews do not dispatch work. When you open the Agents page from another LyftData page, you can choose Build evidence preview. This creates a read-only preview for that subject. It does not dispatch provider work, approve a proposal, or apply changes.
  • The Operator is Preview in 3.0.
  • Operator and Data Awareness have separate consent. Turning one on or off does not affect the other.
  • Cancelling provider work that is already running is best effort, and data that has already been transmitted cannot be recalled.
  • Known issue: server or supervisor shutdown may not drain in-flight Operator runs cleanly.