> 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/ai-workbench-qore/console/console-operator/agents-and-connections.md).
# Agents & connections
Choose which agents and Integration Hub connections the Console Operator can use.
The Console Operator gets work done through agents, and reaches third-party systems through connections. The side panel of every conversation shows both, and lets you decide which ones the Operator may use.
Open any Operator conversation. The side panel is on the right; if it is hidden, use the panel icon beside **+ New Conversation**.
## At a glance
| Task | Where | Scope of the change |
| --------------------------------------- | ------------------------------------------------------------------------------------ | -------------------- |
| Stop the Operator using a system agent | **Agents** → **System** → the agent's **⋯** | You, in this project |
| Let the Operator use one of your agents | **Agents** → **User** → the agent's **⋯** | You, in this project |
| Let the Operator use a connection | **Connections** → the connection's **⋯**, or **+** → **Connections** in the composer | The Console Operator |
| Connect a new system | **All integrations** | The project |
## Agents
**Agents** lists the agents the Operator can hand work to, in two tabs.
**System** — agents provided with Qore and preconfigured for the account:
| Agent | Takes on |
| ------------------------------- | ------------------------------------------------------------- |
| **App Builder Agent** | Building and changing apps |
| **Agent Builder Agent** | Building and changing agents |
| **Knowledge Builder Agent** | Building knowledge bases from files and websites |
| **Document AI Agent** | Extracting, classifying, summarising and generating documents |
| **Treasury Operations Analyst** | Treasury operations questions |
| **Platform Q\&A Agent** | Questions about how Qore works |
**User** — agents built in this project, for example a `Knowledge Base Resolver` you created. Only agents on the current agent runtime are listed; an agent on an older runtime doesn't appear until it is moved to the current one.
System agents start **on**. Your own agents start **off**, so the Operator never hands work to one of them until you choose to. An agent created later also appears **off**. Use an agent's **⋯** menu to turn it on or off. Each agent is turned on or off individually; there is no switch for all of them at once.
A turned-off agent is invisible to the Operator: it doesn't consider it, mention it, or delegate to it. With every agent off, the Operator still answers, and says it has nothing to hand the work to.
The setting applies to you, in this project; colleagues keep their own choices. It sticks across new conversations and sessions. A change takes effect on your next request; work already running isn't cancelled. You can't turn an agent off while it is working on a run.
Keep the list to the agents you need. The Operator reads the description of every agent that is on each time it plans, so a long list costs it room to think and makes its choice of agent less accurate.
While agents run, the section header counts them, for example `1 working`, and a green dot marks each busy agent.
## Connections
**Connections** lists the Integration Hub connections already set up for this project, with whether the Operator may use each one. When the project has none, it reads *"No connections configured for this project."*
Every connection starts **off**: having a connection in Integration Hub doesn't by itself let the Operator use it. Turn one on, and the Operator can act in that system on your behalf; turn it off again, and it can't. The setting isn't tied to one chat; it applies to every conversation.
Some connections have each person bring their own credentials. Turning one of those on asks for nothing; you are asked for your credentials the first time the Operator actually needs the connection.
A connection removed in Integration Hub disappears from this list too.
Each connection's **⋯** menu holds:
**Manage** — choose which of the connection's actions the Operator may use, and how closely each is supervised.
**Enable / Disable** — let the Operator use the connection, or stop it.
**Manage in Integrations** — open the connection's details in the integrations catalog.
Select a connection's name to open its page in Integrations in a new tab.
The same list is in the composer: select **+** → **Connections**. A chip beside the effort picker shows the icons of the connections that are on; select it to open the list.
Only the Operator itself uses these connections. Agents it hands work to don't inherit them.
### Connect a new system
**All integrations**, under the list, opens the full integrations catalog in a window, with a count of what is available, for example `228`. Connect one there, and it appears in **Connections** when you close the window, turned off until you turn it on.
When a request needs a system the Operator has no connection for, it says so in the conversation: it names an existing connection to turn on, or an integration you could connect.
## Notes and limitations
* **This is Console only.** In Control Center, the Governance Operator's agents are always available: its side panel lists its agents and connections, but you can't turn any of them on or off.
### Related
| Title | Description | Target |
|---|
| Console Operator | Conversations, the composer, and what the Operator does. | Console Operator |
| Integrations Hub | The catalog of systems you can connect. | Integrations Hub |
| Schedules | Choose which agents a scheduled run may use. | Schedules |
***
{% columns %}
{% column width="83.33333333333334%" %}
Maintained by Abhishek Paul
AI-assisted, human-approved
{% endcolumn %}
{% column width="16.666666666666664%" %}
{% endcolumn %}
{% endcolumns %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.uptiq.ai/ai-workbench-qore/console/console-operator/agents-and-connections.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
