You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs(turing): major documentation refactoring into focused pages
Split genai-llm.md into dedicated pages:
- embedding-stores.md: ChromaDB/PgVector/Milvus + embedding model selection
- tool-calling.md: full reference for all 27 native tools across 7 categories
- mcp-servers.md: MCP server configuration (stdio/HTTP transport, sync/async modes)
- ai-agents.md: agent composition, configuration form, execution flow diagram
- genai-llm.md refactored as overview with RAG architecture and pointers
Split security-keycloak.md into focused pages:
- security-authentication.md: native session login + API Key (everyday reference)
- security-keycloak.md: Keycloak OAuth2/OIDC full 6-step production setup only
Extracted from developer-guide.md:
- rest-api.md: full REST API reference (search, autocomplete, spell check, GenAI, token usage)
- developer-guide.md now focused on dev environment, SDK, and contributing
Updated sidebars-turing.ts, index.md, and all cross-references across:
assets.md, chat.md, llm-instances.md, token-usage.md, sn-concepts.md,
getting-started/core-concepts.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
description: Configure, compose, and deploy AI Agents in Turing ES — combining LLM Instances, Tool Callings, and MCP Servers into purpose-built assistants.
5
+
---
6
+
7
+
# AI Agents
8
+
9
+
An **AI Agent** is the central composition object in Turing ES's GenAI system. It combines a specific [LLM Instance](./llm-instances.md), a selected set of [Tool Callings](./tool-calling.md), and a set of [MCP Servers](./mcp-servers.md) into a single, named, deployable assistant.
10
+
11
+
Each agent has its own personality, capability set, and visual identity. In the **Chat** interface, every configured agent appears as a separate tab — users choose which agent to interact with based on its name and description. See the [Chat](./chat.md) page for the full interface documentation.
12
+
13
+
AI Agents are configured in **Administration → AI Agents**.
14
+
15
+
---
16
+
17
+
## Configuration Form
18
+
19
+
| Field | Description |
20
+
|---|---|
21
+
|**Name**| Display name shown as the tab label in the Chat interface |
22
+
|**Avatar**| Image representing the agent in the chat UI |
23
+
|**Description**| Brief explanation of the agent's purpose and specialization — shown below the name in the agent tab |
24
+
|**LLM Instance**| The LLM provider and model this agent uses for inference. See [LLM Instances](./llm-instances.md)|
25
+
|**Tool Callings**| Which of the 27 native tools are available to this agent. See [Tool Calling](./tool-calling.md)|
26
+
|**MCP Servers**| Which external MCP servers this agent can call. See [MCP Servers](./mcp-servers.md)|
27
+
28
+
---
29
+
30
+
## Composing Agents for Specific Roles
31
+
32
+
Because each agent independently selects its LLM Instance, tools, and MCP servers, it is straightforward to build purpose-specific assistants. Give each agent a focused set of tools — a lean tool list reduces prompt length and helps the LLM make more precise tool choices.
33
+
34
+
**Enterprise Search Agent**
35
+
36
+
An agent that helps users find and explore indexed content across the organization.
Copy file name to clipboardExpand all lines: docs-turing/chat.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ description: Use the Turing ES Chat interface to interact with LLMs, AI Agents,
9
9
The **Chat** interface is the primary way users interact with the AI capabilities of Turing ES. It is organized into three tabs: a direct **LLM chat**, a **Semantic Navigation** chat for searching indexed sites, and dynamic **AI Agent** tabs — one per configured and enabled agent.
10
10
11
11
:::info LLM required
12
-
The Chat interface is only available when at least one LLM Instance is configured and enabled. See [Generative AI & LLM Configuration — LLM Providers](./genai-llm.md#llm-providers) to set one up.
12
+
The Chat interface is only available when at least one LLM Instance is configured and enabled. See [LLM Instances](./llm-instances.md) to set one up.
13
13
:::
14
14
15
15
---
@@ -125,7 +125,7 @@ Each **AI Agent** configured and enabled in **Administration → AI Agents** app
125
125
|**Native Tools**| A selection from the 27 native tool callings (code interpreter, search, weather, finance, etc.) |
126
126
|**MCP Servers**| External tool servers connected specifically to this agent |
127
127
128
-
For full configuration details — composing agents, tool selection, and MCP Server registration — see [Generative AI & LLM Configuration — AI Agents](./genai-llm.md#ai-agents).
128
+
For full configuration details — composing agents, tool selection, and MCP Server registration — see [AI Agents](./ai-agents.md).
129
129
130
130
---
131
131
@@ -235,4 +235,4 @@ curl -X POST "http://localhost:2700/api/v2/llm/agent/my-agent/chat" \
Copy file name to clipboardExpand all lines: docs-turing/developer-guide.md
+4-156Lines changed: 4 additions & 156 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -197,163 +197,11 @@ Turing ES maintains high code quality standards. You can check the project healt
197
197
198
198
## REST API
199
199
200
-
Turing ES exposes a rich REST API for integrating search and AI capabilities into any application. All endpoints use **JSON** and authenticate via an **API token** passed as a custom request header.
200
+
Turing ES exposes a REST API for integrating search and AI capabilities into any application. All endpoints use **JSON**. Authentication uses the `Key` header with an API Token created in **Administration → API Tokens**.
201
201
202
-
### Authentication
202
+
For the full endpoint reference — search, autocomplete, spell check, latest searches, GenAI chat, and token usage — see **[REST API Reference](./rest-api.md)**.
203
203
204
-
All API requests require a `Key` header containing the API token:
205
-
206
-
```
207
-
Key: <YOUR_API_TOKEN>
208
-
```
209
-
210
-
**Generating an API Token:**
211
-
212
-
1. Sign in to the Administration Console at `http://localhost:2700`.
213
-
2. Navigate to **Administration → API Tokens**.
214
-
3. Click **New** and fill in a title and description.
215
-
4. Copy the generated token immediately — it will not be shown again.
216
-
217
-
For full details on managing users, groups, roles, and tokens, see the [Administration Guide — API Tokens](./administration-guide.md#api-tokens).
For interactive exploration, use the built-in Swagger UI at `http://localhost:2700/swagger-ui.html` or the OpenAPI spec at `http://localhost:2700/v3/api-docs`.
357
205
358
206
---
359
207
@@ -374,4 +222,4 @@ Check the open [GitHub Issues](https://github.com/openviglet/turing/issues) for
0 commit comments