Connecting to Agents

Creating or filling a base does not automatically connect it to an AI Agent. You create the link in the agent editor, under Knowledge. Selecting at least one base makes SquadOS enable the search_knowledge_base search internally; you do not need to add that search under Tools.

Before connecting

• The agent and base must belong to the active organization.
• Your role must allow you to edit the agent (agents.write) and edit bases (bases.write). The first permission opens the editor; the second is also required to save the link.
• Wait until the required items are Processed. The searchable items number in the editor totals every item in the selected bases, including items still processing or ending in an error; the number alone does not prove that the content can already be retrieved.

If you still need to add content, see Document Upload.

Selecting the bases

1. Open Admin → Agents and choose Edit for the agent.
2. In the editor sidebar, open Knowledge.
3. Under Knowledge bases, select one or more bases.
4. Check the name, description, and item count shown for each base.
5. If a warning says a base has no description, select Manage and describe what it covers on the base itself. The agent receives this catalog to decide whether search applies to the question.
6. Select Save.

Discard restores the last saved state. If you try to switch sections with pending changes, the editor asks for confirmation before abandoning them.

Caution

If you can select bases but get Could not save this agent’s knowledge, ask an administrator to check bases.write as well as agents.write. The interface currently shows the controls before validating that second permission.

Understanding the search instruction

Expand The instruction the agent receives to review the guidance assembled by SquadOS. It contains, in this order:

1. the general rule to search the organization’s material before answering from memory;
2. the name and description of every selected base;
3. the Rule for this agent only, when provided.

The agent-specific rule is optional, accepts up to 500 characters, and appears last with explicit precedence over the general guidance. Use it to restrict or prioritize searches for that agent without repeating the base catalog. For example:

Search these bases only for questions about plans, policies, and setup.

If a base has no description, the agent receives only its name. Adding the description makes it clearer when search applies for every agent that uses it.

More than one base

Select multiple bases when the agent must search different domains, such as technical support, commercial policies, and a product catalog. Search remains restricted to the selected bases and may combine relevant excerpts from more than one source.

Avoid contradictory versions or highly repetitive content across bases selected for the same agent. The connection defines where to search, but it does not guarantee that a question will retrieve the right excerpt. Content quality, processing, and retrieval relevance must be validated separately.

AutoLearn

After at least one base is selected, the AutoLearn area appears. Enable Log unanswered questions to make gap reporting available to the agent. The runtime instructs it to log an opportunity when search says exactly that no relevant information was found, or when the excerpts clearly concern another topic — only for questions within the agent’s scope.

Logging is a model-invoked tool, so do not assume every incomplete answer guarantees that an opportunity was created. The area shows recent gaps for that agent, and Review opportunities opens the review queue. See Learning Opportunities (AutoLearn) to review, approve, or ignore those records.

When you clear the last selected base and save, SquadOS disables search and AutoLearn for that agent.

Bases and context blocks are different

The same section shows Context blocks beside the bases. A base is searched on demand; an active block is loaded in full on every agent reply. Use Reusable Context Blocks to choose the right mechanism and understand the token impact.

Caution

The Save button writes both bases and blocks in this section. If you change both groups at once and receive an error, check both again before retrying: the current operations are not atomic, and part of the configuration may already have been persisted.

Validating the connection

After saving, use the editor’s test panel with a small, controlled set:

• a question whose answer is in a Processed item;
• a paraphrase that does not repeat the document literally;
• a question that requires information from two selected bases;
• a question about an unselected base;
• a question outside the agent’s scope.

Review the reply and execution details to verify whether search was called and which sources reached the model. A successful call proves that the configuration ran; it does not, by itself, prove that the retrieved content was sufficient or correct.