> ## Documentation Index
> Fetch the complete documentation index at: https://docs-xcor.paloaltonetworks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Operator interface reference

> Reference for the controls, message elements, and keyboard shortcuts in Cortex XCOR Operator.

[Operator](https://docs-xcor.paloaltonetworks.com/navigate/operator) presents the same conversation in two
surfaces in Palo Alto Networks Cortex XCOR: a side panel that stays open as
you move between pages, and a full page. Use this reference to identify the controls
in each surface, the elements that make up a conversation, and the keyboard shortcuts
that Operator supports.

## Panel and page controls

### Side panel header

The side panel header displays the **Operator** title and these controls:

* ** Copy URL** copies a link to the current conversation.
  This control appears only after you send a message, and doesn't appear for
  accounts in [temporary mode](https://docs-xcor.paloaltonetworks.com/navigate/operator#availability-and-permissions).
* ** New chat** starts a conversation, ending any
  response in progress.
* ** Chat history** opens a searchable list of your recent
  conversations. Enter text in **Search chats** to filter the list. When no
  conversation matches, the list displays `No chats found`.
* ** Go to chat page** moves the current conversation to
  the full-page view.
* ** Close Panel** closes the panel.

### Full page controls

The full page displays the **Operator** header and a **Chat history** sidebar
containing:

* ** New chat**, which is selected when no conversation
  is open.
* A **Recents** list of your saved conversations, most recently updated first.
* ** Close chat history**, which collapses the
  sidebar to a rail. The rail displays ** New chat** and
  ** Open chat history**.

## Message field

The message field accepts multiple lines and expands as necessary. To enter a
manual line break, press <kbd>Shift</kbd> + <kbd>Enter</kbd> (<kbd>Shift</kbd> +
<kbd>Return</kbd> on macOS).

### Slash commands

Type `/` at the start of the field to open a menu of
**[Skills](https://docs-xcor.paloaltonetworks.com/navigate/operator/capabilities.md#skills).** Each entry lists the
command and a description of what it does. Continue typing to filter the menu,
use the arrow keys to select a command, and press <kbd>Enter</kbd>
(<kbd>Return</kbd> on macOS) or click a command to insert it.

### Send and stop

The circular button at the right of the message field reflects the state of the
conversation:

* ** Send message** submits your prompt.
* ** Stop generating** ends a response in progress.

### Context gauge

When a conversation has consumed part of its context window, a gauge appears next
to the message field displaying the percentage used. Hold the pointer over the
gauge to view a precise token usage count.

The gauge changes color and message as usage increases:

* Under 80%, it reports the percentage and token count.
* At 80% or higher, it turns amber and advises you to clear the chat soon.
* At 100%, it turns red, reports that the context window is full, and advises you
  to clear the chat or start a new thread to continue.

Start a [new chat](#side-panel-header) to reset the context window.

## Conversation elements

A conversation alternates between messages you send and responses from
Operator. Responses can contain several element types.

### Your messages

Your messages display in a shaded block. When the page you're on differs from the
page of your previous message, a chip preceding the message names the page
context, such as **Dashboard**, **Alert**, or **Metrics explorer**. Hold the
pointer over the chip to view the full URL, which you can click to open in a new
tab. For more information, see
[Page context](https://docs-xcor.paloaltonetworks.com/navigate/operator#page-context).

### Reasoning

While Operator works out its approach, it displays animated `Thinking...`
text, or the current step of its reasoning. After it finishes, the reasoning
collapses into a row reporting how many seconds it thought for, which you can
expand to inspect in full.

### Tool calls

Operator displays each search, query, and command it runs. A single step
displays as its own row. Two or more consecutive steps collapse into one group
labeled **Ran** followed by a count of tool calls, commands, or both.

Groups expand automatically while Operator is working and collapse when it
finishes. Click a group to change its state.

Each step displays its status:

* A spinner while the step is running.
* A green  check icon with the step name struck
  through after it completes.

Expand a step to view its **Input:** and **Output:**. Shell commands display the
command that ran, prefixed with `$:`, followed by its output. Failed commands
display their error output in red.

Steps that use a [skill](https://docs-xcor.paloaltonetworks.com/navigate/operator/capabilities.md#skills) name the skill
and report whether Operator is using it, used it, or failed to use it. Expand
a failed skill to view the error.

### Code blocks

Operator returns queries and structured data in code blocks labeled with
their language. Every code block has a ** Copy code** button.

Code blocks that contain a query also have an **Open in Explorer** button, which
opens the query in the matching explorer with the time range Operator used.
This button appears for PromQL, logging queries, change event queries, and
Graphite queries.

Long blocks scroll rather than expanding the conversation. While Operator is
still writing a long block, the block header displays `Generating...`.

### Timestamps

Operator writes timestamps as chips formatted in your account's
[time zone and clock preferences](https://docs-xcor.paloaltonetworks.com/navigate#your-account).

### Investigation cards

When Operator starts or checks an [investigation](https://docs-xcor.paloaltonetworks.com/investigate/investigations), it
displays an **Investigation** card rather than raw output. The card names what's
being investigated, such as a dashboard panel or an alert, and displays a status:

* **Investigation in progress**, which displays `Starting investigation` as its
  initial summary
* **Report ready for review**
* **Investigation complete**
* **Investigation incomplete**, when the investigation fails

Click **View full investigation** to open the investigation in a new tab. For how
to read what the card links to, see
[Read an investigation report](https://docs-xcor.paloaltonetworks.com/investigate/investigations/reports.md).

## Rate a response

Each completed response displays rating controls:

1. Click ** Helpful** or
   ** Not helpful**.
2. Optional: Add detail in the **Tell us more about your feedback** dialog, and
   then click **Submit rating**. To record only the rating, click **Cancel**.

Ratings are recorded per response, and you can't change a response after
submitting it.

## Manage conversations

Unless your role prohibits it, Operator saves your conversations. You can
[resume](#resume-a-conversation) or [share](#share-a-conversation) your saved
conversations from the [chat history](#side-panel-header).

### Resume a conversation

To resume a saved conversation, open [chat history](#side-panel-header) and select
it. Unless your account is in
[temporary mode](https://docs-xcor.paloaltonetworks.com/navigate/operator#availability-and-permissions), the chat
history retains your 20 most recent conversations.

Cortex XCOR names each conversation after your first message in it,
truncated if the message is long. You can't rename, delete, or export
conversations.

### Share a conversation

To share a conversation, click ** Copy URL** in the side
panel header, or copy the URL of the Operator page while the conversation is
open. Cortex XCOR displays `Copied` to confirm.

When another account opens the link, the conversation appears read-only with an
alert naming the account that shared it. The message field doesn't appear, so
recipients can't continue a conversation you shared. To ask their own questions,
they can start a new chat.

Accounts in [temporary mode](https://docs-xcor.paloaltonetworks.com/navigate/operator#availability-and-permissions)
can't share conversations.

## Errors

When a response fails, Operator displays a **Couldn't get a response** alert
next to the message field with **Try again** to resubmit your prompt. The alert
describes the cause:

| Message | Cause |
| - | - |
| `We could not reach Operator. Check your connection and try again.` | Cortex XCOR couldn't reach the Operator service. |
| `Operator rejected this request. If the issue persists, clear the chat or start a new thread.` | Operator refused the request, which often indicates a full context window. |
| `Something went wrong. Please try again.` | Any other failure. |

## Keyboard shortcuts

The following table lists Operator's supported keyboard shortcuts:

| Shortcut | Action |
| - | - |
| <kbd>A</kbd> | Open or close the Operator side panel. Unavailable on the Operator page. |
| <kbd>/</kbd> | Open the slash command menu, when typed at the start of the message field or after a space. |
| <kbd>Enter</kbd> (<kbd>Return</kbd> on macOS) | Send the prompt, or accept the selected slash command when the menu is open. |
| <kbd>Shift</kbd>+<kbd>Enter</kbd> (<kbd>Shift</kbd>+<kbd>Return</kbd> on macOS) | Insert a line break without sending. |
| <kbd>Control</kbd>+<kbd>Enter</kbd> (<kbd>Command</kbd>+<kbd>Return</kbd> on macOS) | Send the prompt. |

To view the shortcuts available on the current page, press <kbd>Control</kbd>+<kbd>/</kbd>
(<kbd>Command</kbd>+<kbd>/</kbd> on macOS).


## Related topics

- [Operator capabilities reference](https://docs-xcor.paloaltonetworks.com/navigate/operator/capabilities.md)
- [Palo Alto Networks Telemetry Pipeline release notes](https://docs-xcor.paloaltonetworks.com/ingest/pipeline/v2/release-notes.md)
- [Navigate the Palo Alto Networks Telemetry Pipeline web interface](https://docs-xcor.paloaltonetworks.com/ingest/pipeline/navigate.md)
- [Navigate the Cortex XCOR interface](https://docs-xcor.paloaltonetworks.com/navigate.md)
- [Palo Alto Networks Telemetry Pipeline concepts](https://docs-xcor.paloaltonetworks.com/ingest/pipeline/v2/concepts.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.