mirror of
https://github.com/agentscope-ai/ReMe.git
synced 2026-10-03 02:24:31 +00:00
354837f9af
* refractor(proactive): upgrade proactive feature with disentangled job and steps * refactor(proactive): apply audit fixes - rename read-side job 'proactive' -> 'proactive_read' (less confusing vs the refresh pipeline) - drop dedicated agent_wrapper.proactive; extraction reuses the default wrapper - simplify schema: remove unused ProactiveExtractOutput/TopicUpdate, drop resource_paths - extract no longer scans resource/ directly (daily notes already carry resource content) - update tests and docs accordingly * feat(proactive): strict extract-output gate and prompt total budget - parse_extract_reply now requires a contract section (follow_ups/extends/updates as a list); non-empty replies with misspelled section names trigger the existing one-shot retry instead of silently checkpointing changed files - pack_paths gains max_total_chars; extract packs newest daily material first, keeps the first file on overflow, and records omitted files in a trailer (default budget 300000 chars, configurable via max_total_chars) - tests: schema gate unit, schema-error retry e2e, budget unit + e2e * feat(proactive): add scenario-card plan step and generative agenda step * feat(proactive): digest-personal profile personalization and leaner LLM contract - extract/plan/agenda now draw a user profile block from <digest_dir>/personal/*.md (frontmatter description + body excerpt, per-file budget, profile.md fallback) - all daily access honours the configured daily_dir (prompt paths parameterized, config-driven fallbacks) so workspaces using e.g. memory/ work unchanged - schema trim: drop dead fields errors/material_paths, carry_forward_all -> count - shrink LLM output contract: new topics emit title/reason/confidence/paths only; keywords removed end-to-end, evidence derived from paths[0] (updates keep it) * fix(proactive): skip checkpoint when extract reply stays unusable after retry Two consecutive unparseable replies now short-circuit the round without checkpointing, so the same material is retried next round instead of being silently consumed (closes the residual audit #1 gap: the structural gate detected schema-wrong output but a double failure still checkpointed). * fix(proactive): replace running bool with reference-counted job activity tracker for the idle gate * refactor(proactive): remove job activity tracking and idle gate, restore job tree to upstream * fix(proactive): address second audit round (readonly reader, mtime checkpoint, wider fallbacks, profile containment, horizon content, expiry boundary) * refactor(dream): strip interests.yaml ownership from dream, proactive is now the sole writer * refactor(dream): separate proactive topic generation * ci: update renamed auto dream smoke test * fix(proactive): complete refresh migration and docs --------- Co-authored-by: jinli.yl <jinli.yl@alibaba-inc.com>
76 lines
2.7 KiB
Markdown
76 lines
2.7 KiB
Markdown
---
|
||
title: 常见问题
|
||
description: ReMe 安装、服务、模型、检索、文件和插件问题的快速答案。
|
||
---
|
||
|
||
# 常见问题
|
||
|
||
## 基础文件操作需要模型 API Key 吗？
|
||
|
||
不需要。`write`、`read`、`list`、`stat`、BM25 搜索、wikilink 遍历和 `proactive_read` 可以在没有模型凭据时
|
||
运行。`auto_memory`、`auto_resource`、`auto_dream` 和 proactive refresh 需要 LLM。
|
||
|
||
## 为什么配置了 Embedding Key 仍然只有 BM25？
|
||
|
||
Embedding 默认未启用。除了凭据，还必须配置 `as_embedding`、`embedding_store`，并让 `file_store.default.embedding_store` 指向该组件。参见[基础配置](./configuration.md#embedding-配置)。
|
||
|
||
## 为什么 `reme reindex` 没有发现新文件？
|
||
|
||
`reindex` 只从当前 `file_chunks` 重建 BM25 或 embedding 索引，不扫描 workspace。检查 `index_update_loop` watcher、文件目录、后缀和 `health_check`。
|
||
|
||
## 怎样使用另一个 workspace？
|
||
|
||
启动时传入稳定的绝对路径：
|
||
|
||
```bash
|
||
reme start workspace_dir=/absolute/path/to/memory
|
||
```
|
||
|
||
普通 CLI 调用会发现运行服务，不必重复 workspace 参数。
|
||
|
||
## 端口 2333 被占用怎么办？
|
||
|
||
不要停止未知监听者。选择另一个端口：
|
||
|
||
```bash
|
||
reme start service.port=8181
|
||
```
|
||
|
||
然后用 `reme find_reme` 确认发现结果。
|
||
|
||
## 为什么插件安装后仍然没有对应 Job？
|
||
|
||
安装只让 distribution 在当前 Python 环境中可见。还需要在应用配置中启用：
|
||
|
||
```bash
|
||
reme start plugins='["auto-fin"]'
|
||
```
|
||
|
||
修改安装或启用状态后需要重启已运行的服务。
|
||
|
||
## 可以直接编辑 workspace 中的 Markdown 吗？
|
||
|
||
可以。文件是事实源，watcher 会摄取修改。应保留有效 frontmatter、使用完整 workspace-relative wikilink，并避免同时由多个编辑器无条件覆盖同一文件。
|
||
|
||
## 可以把服务暴露到公网吗？
|
||
|
||
默认配置不适合直接公网暴露。服务包含写入和删除 Job，HTTP CORS 宽松，且没有通用认证层。请使用受控网络或带 TLS、认证、访问控制的反向代理，并限制 `service.jobs`。
|
||
|
||
## 怎样备份和迁移？
|
||
|
||
停止写入后备份整个 workspace。`session/`、`resource/`、`daily/` 和 `digest/` 是最重要的用户数据；`metadata/` 可以随同备份，也可以从源文件重建。详见[诊断、备份与恢复](./operations.md)。
|
||
|
||
## Studio 找不到怎么办？
|
||
|
||
基础 `reme-ai` 包不包含前端资源。安装 `reme-ai[web]` 或 `reme-ai[core]`，或通过 `service.web_static_dir` 指向构建产物。Studio 缺失不会影响 Job API。
|
||
|
||
## 当前服务到底开放了哪些能力？
|
||
|
||
运行：
|
||
|
||
```bash
|
||
reme help
|
||
reme app_config
|
||
```
|
||
|
||
静态文档描述默认配置；运行服务可能由自定义配置和插件改变。
|