refactor: remove retired agent provider integration
This commit is contained in:
@@ -26,7 +26,7 @@ Web presentation note: `/lite` uses these same chat streams and existing search
|
||||
"chatId": "optional-chat-id",
|
||||
"persist": true,
|
||||
"clientRequestId": "optional-client-generated-id",
|
||||
"provider": "openai|anthropic|xai|gemini|hermes-agent",
|
||||
"provider": "openai|anthropic|xai|gemini",
|
||||
"model": "string",
|
||||
"messages": [
|
||||
{
|
||||
@@ -76,7 +76,8 @@ Notes:
|
||||
- `maxTokens` is optional. For `anthropic`, when omitted the backend requests the selected model's maximum output token limit from Anthropic's Models API and uses that as `max_tokens`; if the model limit cannot be loaded, the fallback is 128000. For other providers, omitted `maxTokens` is not sent as an explicit cap.
|
||||
- Attachments are optional and are persisted under `message.metadata.attachments` on stored user messages when `persist` is `true`.
|
||||
- For a persisted ordinary chat, a literal case-insensitive `@sybil` token in the latest user message invokes the existing persistent Sybil Agent instead of the selected provider. Email addresses, code spans/fences, indented code, and Markdown quote lines do not trigger it. The visible user message and inline Agent reply remain in the ordinary chat and are marked with backend-owned `metadata.agentAside`; the backend excludes both from later selected-provider context without deleting the visible rows. This routing does not apply to the special Agent tab or Quick Questions.
|
||||
- The `meta` event for an inline Agent reply contains `provider: "hermes-agent"`, `model: "sybil-agent"`, and `agentAside: true`. The selected ordinary provider is not run for that turn. Clients should render the response with the existing Sybil Agent identity and retain aside metadata on the optimistic streaming message until the canonical REST refresh.
|
||||
- The `meta` event for an inline Agent reply contains `provider: "sybil-agent"`, `model: "sybil-agent"`, and `agentAside: true`. The selected ordinary provider is not run for that turn. Clients should render the response with the existing Sybil Agent identity and retain aside metadata on the optimistic streaming message until the canonical REST refresh.
|
||||
- `sybil-agent` is a response identity, not an accepted request provider or a model-picker option. Decode completion metadata independently from the selectable provider list. Active-stream attachment and completed-request retries use the same identity.
|
||||
- Before the Agent request starts, the backend loads every page of the safe visible thread and sends it as required initial context, including previous asides and supported attachment contents. This is not an optional `read_chat_history` tool call. Hidden system/tool rows and unrelated metadata are excluded; transcript data is untrusted context. If history/attachment projection is incomplete or exceeds the 30 MiB transfer limit, or the Agent model rejects the complete context, the stream reports an error and emits no partial-context answer.
|
||||
|
||||
Persisted chat streams with a `chatId` are backend-owned active runs:
|
||||
@@ -105,7 +106,7 @@ This endpoint is intended for clients that restored an active `chatId` from `GET
|
||||
Request body:
|
||||
```json
|
||||
{
|
||||
"provider": "openai|anthropic|xai|gemini|hermes-agent",
|
||||
"provider": "openai|anthropic|xai|gemini",
|
||||
"model": "string",
|
||||
"question": "What is the capital of France?",
|
||||
"enabledTools": ["web_search", "fetch_url"],
|
||||
@@ -218,10 +219,9 @@ Terminal tool-call event:
|
||||
- `xai`: backend uses xAI's OpenAI-compatible Chat Completions API and may execute the same internal tool calls before producing final text.
|
||||
- `gemini`: backend uses Google's native Gemini `streamGenerateContent` API and may execute the same internal tool calls before producing final text.
|
||||
- `fetch_url` sends browser-like navigation headers for outbound URL requests to reduce false 403s from sites that reject generic server clients. It converts HTML to text and extracts selectable PDF text page by page (without OCR), including when the response media type is inaccurate but the PDF signature is present. URL downloads are limited to 10 MiB, PDF extraction to 30 pages per call and an isolated worker terminated after 8 seconds, and accumulated PDF text to `maxCharacters` (default 12,000; maximum 50,000), plus a brief truncation hint. PDF tool results include `pdfStatus`, `pageCount`, and selected `pages`; call with `pages:[...]` to retrieve specific pages. Encrypted, page-free, and text-free PDFs return explicit status and text with `ok:false`. Oversized responses fail with a size-limit error.
|
||||
- `hermes-agent`: backend uses the configured Hermes Agent OpenAI-compatible Chat Completions API. Sybil does not add its own tool definitions for this provider; Hermes Agent handles its own tools server-side. Custom Hermes stream events are normalized away unless they produce text deltas in this SSE contract.
|
||||
- `openai`: image attachments are sent as Responses `input_image` items; text attachments are sent as `input_text` items.
|
||||
- `gemini`: image attachments are sent as native Gemini `inlineData` parts; text attachments are inlined as text parts.
|
||||
- `xai` and `hermes-agent`: image attachments are sent as Chat Completions content parts; text attachments are inlined as text parts.
|
||||
- `xai`: image attachments are sent as Chat Completions content parts; text attachments are inlined as text parts.
|
||||
- `openai`: Responses calls that can enter the server-managed tool loop use `store: true` so reasoning and function-call items can be passed between tool rounds.
|
||||
- `anthropic`: streamed via event stream; emits `delta` from `content_block_delta` with `text_delta`, and emits normalized `tool_call` SSE events when Anthropic `tool_use` blocks are executed. Image attachments are sent as base64 `image` blocks and text attachments are appended as `text` blocks.
|
||||
- `web_search` uses `CHAT_WEB_SEARCH_ENGINE`: `exa` (default), `brave` (requires `BRAVE_SEARCH_API_KEY`), or `searxng` (requires `SEARXNG_BASE_URL`; the instance must allow `format=json`). This only affects chat-mode tool calls, not search-mode endpoints.
|
||||
|
||||
Reference in New Issue
Block a user