Skip to main content
This feature is in Early Access (EA), and might not be visible in your app. To learn more about this program and the features it contains, see the Early access page.
A workspace holds the draft files that Operator writes during a conversation. Use it to review proposed changes to dashboards, notebooks, monitors, SLOs, and notification policies before they take effect. Nothing changes in Palo Alto Networks Cortex XCOR until you select Create or Save on a file. Each workspace belongs to one conversation, so a single request can draft related changes together. For example, this prompt updates a dashboard and its monitors in the same workspace:

Update the on-call dashboard and its monitors for the new checkout-v2 service.

For the resource types that workspaces support, see Resources in workspaces.

When Operator uses a workspace

Operator edits the dashboard or notebook you have open in place, as described in Operator capabilities. It writes to a workspace when it can’t change the page that you’re viewing, such as:
  • Changes to monitors, SLOs, and notification policies.
  • Changes to several resources at once.
  • Changes to a dashboard or notebook that isn’t open.
  • Requests that you make from a page unrelated to the resource.
To change an existing resource, Operator reads the live resource and writes a draft named after its slug, changing only the fields the request requires. To create a resource, Operator writes a new draft file. To make Operator use a workspace file instead of editing the open dashboard or notebook, ask for it in your prompt. When a workspace file already exists for the resource you have open, Operator makes the change in place, then deletes the file so that no conflicting copies remain.

Open a workspace

After Operator writes its first file, the workspace appears in the conversation. Where it appears depends on the surface and the width of the window:
  • On the full page with enough room beside the conversation, a Workspace card lists the files.
  • In the side panel or a narrow window, a card at the foot of the conversation summarizes the changes, such as 2 workspace changes. Click Open workspace to review to move the conversation to the full page with the workspace open.
When Operator writes the first file during a response, the file opens in the viewer automatically. Opening an existing conversation doesn’t open the viewer. Click Close workspace to close the viewer and return to the conversation. The file list remains in the card. The workspace also opens on its own page, which lists files grouped by resource type. For descriptions of each control, see Workspace controls.

Review a file

Select a file to open it in the viewer. The viewer offers up to three views:
  • Preview renders the draft as the resource appears in XCOR. Dashboards, notebooks, monitors, and SLOs have previews.
  • Source shows the file contents. The source is read-only. To change the file, ask Operator. Click Copy source to copy it.
  • Diff compares the file with the existing resource. The view appears only for a resource that already exists and differs from the file. The header reads Compare with existing followed by the resource type, and badges count the lines added and removed.
When a file differs from the existing resource, or describes a resource that doesn’t exist yet, an Unsaved badge appears on the file. Hold the pointer over the badge to see what’s unsaved. Ask Operator in the conversation to adjust any file. Operator updates the existing file instead of creating a copy.

Save or create a resource

Apply files one at a time. Workspaces have no action to approve every file at once. XCOR validates each change and applies it with your permissions, the same as when you edit the resource manually. To save a file to an existing resource:
  1. Open the file and review its Preview and Diff views.
  2. Click Save.
  3. In the Save changes to dialog, confirm the resource, and then click Save.
To create a resource from a file:
  1. Open the file and review its Preview view.
  2. Click Create.
  3. In the Create dialog, enter a name. The name defaults to the filename.
  4. Select a collection. Notebooks default to your user collection and can’t belong to a service collection. Dashboards, monitors, and SLOs default to your personal collection, and you can select a team or other collection instead.
  5. Click Create.
When the action succeeds, a confirmation message appears. For a dashboard, the message includes a View dashboard link. When it fails, the message names the cause, such as a validation error or a permissions problem, and the resource stays unchanged. Saving replaces the resource’s configuration with the file’s contents. Saving a dashboard keeps its existing name, collection, and labels. After you save a file, Save is disabled and its tooltip reports when you saved it. Save is also disabled with the tooltip No changes to save when the file matches the resource. If Operator later changes the file, Save becomes available again.

Resolve out-of-date files

Save is locked when the live resource changed after Operator wrote the file or after you last saved it. The lock prevents a save from overwriting changes made by someone else. A lock icon appears on the button, and the tooltip explains the cause:
  • The dashboard was changed on DATE, after this file was written. The resource changed in XCOR and the file didn’t.
  • This file and the dashboard have both changed since this file was applied. Both the resource and the file changed since you last saved.
The tooltip names the resource type, such as dashboard or monitor. To update a file, click Resolve conflicts with Operator in the tooltip. XCOR fills the message field with a prompt that asks Operator to read the latest resource and merge its changes into the file, keeping edits you made in the workspace. XCOR doesn’t send the prompt, so you can edit it first. Press Enter (Return on macOS) to send it. When a live change and a workspace edit modify the same setting, Operator keeps the workspace edit and tells you what it chose.

Resources managed in code

XCOR blocks Save for dashboards and notebooks that you manage with Terraform, Chronoctl, the Kubernetes operator, or Prometheus sync. The tooltip reads This dashboard is managed by Terraform. Edit it there to save changes., naming the resource type and the source. XCOR doesn’t confirm whether monitors, SLOs, and notification policies are managed in code. Before you save one, confirm that no code repository manages it. Otherwise, the next apply from your code overwrites your change. Terraform files, which have a .tf extension, and other file types are source only. To use Terraform files that Operator drafts, copy the source and apply it through your existing Terraform workflow.

Share a workspace

A workspace is shared with its conversation. To share a draft, copy the link to the conversation as described in Share a conversation. Anyone in your tenant who has the link can open the conversation and its workspace. Recipients see the conversation as read-only. They can open, preview, and compare each file, but they can’t ask Operator to change your draft. Recipients with a role that grants edit permissions can also create or save files from your draft. To build on a draft, a recipient starts a new chat.

Availability and limitations

  • Workspaces are available only in saved conversations. Accounts in temporary mode don’t have a workspace for their own conversations.
  • A workspace lives as long as its conversation. You can’t rename or delete either.
  • Workspaces can save changes to existing notification policies but can’t create one. A policy’s diff shows the entire policy, because saving a policy changes routing for every monitor that uses it.
  • Diff requires that the resource already exists in XCOR.
  • Rate any Operator response to report what worked and what didn’t. See Rate a response.
Generative AI features can produce incorrect results, hallucinate data, and deliver inaccurate analysis. Use generative AI features with care, and independently verify all information produced by generative AI tools before applying it.Certain prompts, data, or other inputs might produce irrelevant content. Don’t rely on generative AI features or responses for any uses that exceed their designed scope.