> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/console/console-operator.md).

# Console Operator

The Console Operator—build and run work from one chat, scoped to a project.

The Console Operator is the chat surface in Console. Describe your goal, and it assigns work to the right agent or builds the required asset. It returns the result in the same conversation.

Use it to build and use apps, agents, knowledge bases, and agentic applications. It can also search the web, crawl a website, answer questions about data, and build presentations.

It replaced the Console dashboard. The dashboard listed existing assets. The Operator gives you one place to ask and act.

For general orchestration, see [Operator](/core-concepts/operator.md). This page covers Console behavior.

## At a glance

* **Where:** Console, in your selected project
* **Scope:** **Project** apps, agents, knowledge bases, design systems, and context
* **Acts:** immediately. It dispatches when you ask—there is no approval step
* **Also builds:** apps, agents, knowledge bases, and agentic applications
* **Searches:** the web and public websites

## What it does

**It routes work to your agents.** The Operator interprets your intent, identifies the agent that can complete each task, and combines its updates into one response.

**It builds.** Ask for a knowledge base, app, agent, or agentic application. The Operator creates it in the current project. You can test a new agent in the same conversation.

**It uses the web as input.** Ask it to search the web or crawl a public website. Given a URL, it can use the site's content to create a knowledge base. It can also use the website's design system when building an app.

**It works inside one project.** Everything it creates belongs to the selected project. Switching projects changes what the Operator can reach. See [Accounts, Projects, Spaces](/start-here/how-qore-is-organized.md) for these boundaries.

## What you do not control

The agent team the Operator dispatches to is **preconfigured for the account**. You don't assemble it, and the agents on it aren't yours to edit from the Operator. The set is expected to grow as more capabilities ship.

### Related

<table data-view="cards"><thead><tr><th>Title</th><th>Description</th><th data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td><strong>Operator</strong></td><td>How an Operator coordinates a team of agents.</td><td><a href="/core-concepts/operator.md">Operator</a></td></tr><tr><td><strong>Governance Operator</strong></td><td>The Control Center Operator, and how it differs.</td><td><a href="/control-center/governance-operator.md">Governance Operator</a></td></tr><tr><td><strong>Accounts, Projects, Spaces</strong></td><td>Accounts, projects, and what each surface can reach.</td><td><a href="/start-here/how-qore-is-organized.md">Accounts, Projects, Spaces</a></td></tr><tr><td><strong>Console</strong></td><td>The project workspace where the Operator works.</td><td><a href="/start-here/console.md">Console</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.uptiq.ai/console/console-operator.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.