* feat(assistant): let the assistant check MCP services and retrieval Add a probe risk for operations that change nothing but do real work (connecting to a service, running a retrieval). Probes use POST, run without approval at every access level, and are capped per run. Open three operations on top of it: - mcp_service.test: connect with the saved settings and report why not - mcp_service.list_tools: list what a service offers before binding it - knowledge_base.search: raw hybrid recall with thresholds, to explain why a document is or is not found x-agent can now name one method when a handler documents several, and catalog parameters accept numbers. * feat(assistant): let the assistant try an agent it set up Add try_agent: the assistant asks an agent one question the way a user would and gets back its answer, the tools it called and the documents it cited, so it can check a setup before calling it done. - The trial runs as the signed-in user in a new agent_trial session kind, which ordinary listings already exclude and the API cannot create, and the session is removed afterwards. Runs are non-interactive, so tools that would ask the user are refused. Long-term memory is untouched: it is written only by the HTTP handler. - The assistant itself, the Wiki fixer and the skill installer cannot be tried, nor any agent granted the operation catalog. - A trial spends model calls and runs the agent's own tools, so it is a write for the access level: confirm asks, auto_write runs, read_only does not offer it. The confirmation card names the agent and question; ConfirmedTool now lets a wrapped tool supply that text. - At most 3 trials per turn, 4 minutes each; the tool timeout is raised above that. Answers, tool errors and references are capped. - The runner is bound to the session service after the container builds it, since the session service depends on the agent service. * feat(assistant): let the user allow similar changes for the conversation The confirmation card for a recoverable change now offers "allow this for the rest of the conversation". Once chosen, later calls of the same kind in the same session run without asking, so a batch tidy-up no longer needs a click per item. - What a grant covers is derived on the server, never taken from the model: the same catalog operation on the same knowledge bases (a document's knowledge base comes from the target read) or the same agent; the same Wiki tool on the run's Wiki knowledge bases; trials of the same agent. Deletions and operations without such a scope, such as creating a knowledge base, always ask. - No new storage: the gate looks for an earlier approved prompt in the session with the same grant and allow_in_session set, for the same tenant and user. Grants therefore survive suspend/resume and replicas, and end with the conversation. A failed lookup asks again. - The response validator accepts allow_in_session only on approval and only when the prompt offered a grant, so a client cannot widen it. - The card shows the scope in the user's language. The model is told such calls may run without a card and that deletions always ask. - describeTarget now returns its target read so the grant reuses it instead of reading again. * feat(assistant): tell the assistant about settings pages and chat answers Pages now report which page is open and, for the agent editor, which section. The model and MCP settings name the model or service open for editing, and chat answers gain an "ask the assistant" button that attaches that answer. The backend resolves these for the assistant only: models and MCP services in the caller's tenant without endpoints or credentials, and messages through the caller's session read access, with the question, an answer excerpt and cited sources quoted as data. * feat(assistant): link the user to pages and filled-in forms The assistant gains open_page, which shows a button to a knowledge base or document, a Wiki page, an agent's editor at a tab, a model or MCP service to edit, or a new model or MCP service with its form filled in. Targets are read through the operation catalog as the user, so a link never points at something they cannot open. Drafts take no credentials and only http(s) endpoints without user info; the card shows the endpoint, and the user enters keys and saves the form themselves. * feat(assistant): manage MCP services, model names and skills * fix(assistant): prefill model drafts on initial navigation * feat(assistant): document tags, model catalog reads, clearer cards, live page refresh - Operations project lists of objects; knowledge.get/list report tags. - model.get shows provider, endpoint and capabilities; new model.list_providers and model.get_provider read the model catalog, including vendors an admin added. - open_page and ask_user guidance: offer page buttons whenever the next step is the user's, word choices for the user. - Chat cards: redesigned open-page card pinned under the final answer, ask-user inputs in the dock style, approval card with aligned fields, translated labels and a question built from the operation summary. - Open pages reload after assistant changes: deletes and moves wait for the background task, Wiki edits now report their changes, KB list counts, tags and chat model selectors refresh. - The assistant panel stays open across reloads within the tab. * fix(ci): format assistant operation code and wrap long lines * feat(assistant): let the assistant see, fill and open the page beside it - read_page / fill_page tools answered by the browser over a page_action prompt, with refs, redaction, in-place text edits, undo card and a page-access switch - composer shows the open page, dialog and selection; a selection bubble and an editor toolbar entry ask the assistant about the selected text - edits scroll into view with a highlight and an inline undo bar - open_page reaches any settings section, toolbox tool and list page, and can navigate there itself to read it, keeping the button when edits are unsaved * feat(assistant): let the assistant open the tab it needs A visible tab can be selected and re-read, and system settings can open straight to user management, so the next step is no longer blocked on the wrong tab. * feat(assistant): expose read-only conversation operations Add session.list, message.list, message.search and message.chat_history_stats to the operation catalog, restrict the sessions and messages areas to non-mutating operations, and search messages with the raw query instead of the log-sanitized one. * style(chat): restyle open-page and page-edit cards * fix(ci): comply with assistant card styles and Go line limits |
||
|---|---|---|
| .. | ||
| assets | ||
| design | ||
| images | ||
| poc/docker-sandbox | ||
| LITE.md | ||
| README.md | ||
| docs.go | ||
| release-v0.8.3-audit.md | ||
| swag.overrides | ||
| swagger.json | ||
| swagger.yaml | ||
| swagger_contract_test.go | ||
README.md
文档已迁至 website-docs
产品、部署、API 和开发文档统一维护在 website-docs。已迁移、重复和过时的旧手写文档已删除;历史内容可从 Git 历史查看。
本目录仅保留以下工程资源及本入口说明:
docs.go、swagger.json、swagger.yaml与契约测试:参与后端编译和测试,生成物仍由make docs更新。LITE.md:Lite 发布包复制为离线 README。images/、assets/:README、Helm 等仍使用的图片资源。poc/docker-sandbox/:独立 Go 实验模块,保留源码和运行说明,不作为当前产品指南。
这些资源尚有编译、发布或历史实验用途,不能直接整目录删除。新的产品说明不要再放入此处。