代码提交
This commit is contained in:
1 parent
70da7c5649
commit
178572bc7f
79 files changed
+13456
-798
No files matched your search
@@ -255,7 +255,46 @@ follow-ups appear in chronological order. The report itself is written in the
|
||||
adjacent sandbox as `/mnt/user-data/outputs/report.md`, with Word, Markdown,
|
||||
and HTML export actions. Word export uses the frontend's existing `docx`
|
||||
dependency and includes the collected reference list, without changing backend
|
||||
Python dependencies.
|
||||
Python dependencies. In chat-collection sessions the report configuration card
|
||||
shows the unique material count inferred from the collector's visible tool
|
||||
results before writing begins. The write lifecycle itself is rendered as
|
||||
ordinary workspace message-list tool steps (not a second timeline component),
|
||||
and remains in the transcript after completion; the generated digest is a
|
||||
normal assistant message below those steps. As soon as the runner enters its
|
||||
summary phase, that same assistant message is inserted in a streaming state
|
||||
and receives each SSE `summary_delta`; completion only changes it in place to
|
||||
the final report-complete wording rather than appending a delayed second
|
||||
summary card.
|
||||
|
||||
Each completed chat-collection report also contributes a normal file card to
|
||||
the message history, named from the report Markdown title rather than the
|
||||
internal `report.md` artifact path. Historical sessions keep the sandbox closed
|
||||
on replay, and opening that card selects the session's virtual report artifact
|
||||
in the sandbox; its download action uses the existing Markdown/Word export
|
||||
dialog. The per-user active-job limit and the default in-job retrieval/write
|
||||
concurrency are both three. The Deep Research composer uses the installed
|
||||
TDesign `Select`, populated from `/api/models`, for an optional per-research
|
||||
model override. It is disabled during active collection/writing, is sent as
|
||||
`model_name` to collector turns, and is applied to the `fast_model`,
|
||||
`smart_model`, and `strategic_model` roles when a session or report job starts.
|
||||
|
||||
Completed-report Q&A uses `POST /api/deep-research/sessions/{id}/chat/stream`
|
||||
for native SSE deltas; the earlier `/chat` JSON endpoint remains for API
|
||||
compatibility. An explicit scoped edit such as “修改第一段”、
|
||||
“重新生成一下第一段” or “重写第二节” uses the separate
|
||||
`POST /api/deep-research/sessions/{id}/rewrite/stream` report-section writing
|
||||
pipeline. That route requires a deterministic Markdown range and returns 422
|
||||
instead of falling back to Q&A when no target is supplied. Ordinary follow-up
|
||||
questions remain report/source-grounded and never mutate the report. The streamed
|
||||
replacement candidate is shown in the message list while the sandbox keeps the
|
||||
current report unchanged. The completed candidate creates a confirmation card;
|
||||
only `POST /sessions/{id}/messages/{messageId}/rewrite-proposal` with
|
||||
`{"action":"apply"}` substitutes the matching range and saves the assembled
|
||||
Markdown. The proposal carries the source report hash, so a stale candidate is
|
||||
rejected instead of overwriting a later edit; dismissing/cancelling leaves the
|
||||
persisted report unchanged. This does not initiate new web research. Legacy
|
||||
unmarked candidates from before this route split are inferred only when their
|
||||
immediately preceding user message contains the same explicit scoped edit.
|
||||
|
||||
Position-roundtable history supports two modes. A non-empty `external_task_id` from the frontend route's `taskId` creates a row with `task_scoped = true`, so all sessions, nodes and persisted conversation snapshots for that task are shared across users; `user_id` is then creator audit metadata only. When the field is absent or empty, the original per-user personal-session behavior remains unchanged. Alembic revision `20260808_01` adds `task_scoped` with the safe default `false` for historical rows plus the task/update-time index.
|
||||
|
||||
@@ -288,6 +327,10 @@ Custom agents are indexed in the `agents` database table. The `id` column is the
|
||||
|
||||
AI 写作的「知识库检索」会直连 `ai_writing.intranet_search_url` 内网 ES/知识库接口,并默认跳过代理环境变量和 HTTPS 证书校验,适配自签名或内部 CA 证书的内网服务。需要强校验时可在 `config.yaml` 里设置 `ai_writing.intranet_verify_ssl: true`。通用检索里的非内置技能在 `ai_writing.researcher_skill_agent: true` 时会用真实 agent 运行时执行技能:以 `ai-writing-researcher` 身份读取该技能的 `SKILL.md`,并按技能要求通过 `bash` 运行脚本,弱模型也会在本轮任务里收到明确的读文件和脚本执行指令。
|
||||
|
||||
### Installable Sentiment Analysis Skill
|
||||
|
||||
skill-packages/sentiment-analysis.skill is a separately installable skill package. It keeps the external AG-UI gateway address in config/sentiment-agent.json, resolves Basic Auth from deployment environment variables, and normalizes the upstream SSE stream into NDJSON (thinking_delta / answer_delta / done) for callers that need incremental rendering. It does not alter the existing frontend sentiment-analysis page. See skill-packages/sentiment-analysis/docs/调用与安装说明.md for installation and invocation.
|
||||
|
||||
### IM Channels
|
||||
|
||||
The IM bridge supports Feishu, Slack, and Telegram. Slack and Telegram still use the final `runs.wait()` response path, while Feishu now streams through `runs.stream(["messages-tuple", "values"])` and updates a single in-thread card in place.
|
||||
@@ -347,6 +390,11 @@ Set your API keys:
|
||||
export OPENAI_API_KEY="your-api-key-here"
|
||||
```
|
||||
|
||||
For a LiteLLM OpenAI-compatible proxy, keep `supports_thinking: false` unless
|
||||
the configured model has an explicit, proxy-supported thinking control. This
|
||||
prevents DeerFlow's connection check from sending vendor-specific `thinking`
|
||||
fields that a generic OpenAI-compatible gateway may reject.
|
||||
|
||||
### Running
|
||||
|
||||
**Full Application** (from project root):
|
||||
|
||||
Reference in new issue
Block a user