agent_id stringclasses 1
value | duration_seconds stringlengths 3 8 ⌀ | exit_reason stringclasses 7
values | has_exit_reason bool 2
classes | model stringclasses 1
value | n_tool_calls int64 0 151 | schema_version stringclasses 1
value | session_id stringlengths 8 8 | task_category stringclasses 6
values | task_desc_sanitized stringlengths 1 300 | task_subcategory stringclasses 2
values | tool_sequence listlengths 0 124 | trace_id_prefix stringclasses 858
values | trigger_source stringclasses 7
values |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
mimir | 95.35 | null | false | deepseek/deepseek-flash | 19 | 2.0 | 972c58c3 | Terminal&Coding | 昨天有没有增流?顺不顺利? | null | [
"skill_view",
"skill_view",
"skill_view",
"patch",
"patch",
"read_file",
"read_file",
"skill_manage",
"patch",
"patch",
"read_file",
"read_file",
"patch",
"read_file",
"read_file",
"execute_code",
"memory",
"terminal",
"terminal"
] | null | null |
mimir | 57.43 | null | false | deepseek/deepseek-flash | 20 | 2.0 | a56bed6f | Retrieval | 那很简单,你现在把今晚 11 点自动压缩的改成今天晚上11:45 或者是所谓的 23:45 | null | [
"search_files",
"search_files",
"read_file",
"search_files",
"read_file",
"search_files",
"search_files",
"read_file",
"read_file",
"terminal",
"terminal",
"search_files",
"terminal",
"read_file",
"terminal",
"write_file",
"read_file",
"skill_manage",
"skill_view",
"memory"
] | null | null |
mimir | 70.89 | null | false | deepseek/deepseek-flash | 17 | 2.0 | d3710daf | Retrieval | 可以,你看一下,是 Cron 没有执行,还是其他的原因。如果 Cron 是可以正常执行的,只是这件事没执行,总之你先找一找,看一看吧,然后我们再讨论 | null | [
"read_file",
"search_files",
"search_files",
"search_files",
"read_file",
"search_files",
"read_file",
"read_file",
"terminal",
"execute_code",
"execute_code",
"search_files",
"read_file",
"patch",
"memory",
"search_files",
"read_file"
] | null | null |
mimir | 56.8 | null | false | deepseek/deepseek-flash | 17 | 2.0 | 439aafd5 | Retrieval | 你自己深度思考,我们有一个三问技能,总之你做出一个,下一步你该做什么的计划 | null | [
"search_files",
"search_files",
"search_files",
"search_files",
"search_files",
"read_file",
"read_file",
"search_files",
"search_files",
"read_file",
"search_files",
"search_files",
"execute_code",
"read_file",
"read_file",
"read_file",
"terminal"
] | null | null |
mimir | 69.62 | null | false | deepseek/deepseek-flash | 12 | 2.0 | 024cc152 | Retrieval | 那我们现在怎么去验证它呢?你有没有什么方法?这是一,第二,我可不可以问一下,我们的技能现在是你可以或者说你有没有能力或者是之前你有没有做自己编写的技能成功了?在你自己有意思的行为下。如果没有,那么刚刚你做的,就是说以后再写技能不会有空壳。那你有没有主动觉得我们现有的技能进行迭代?然后有没有你确定不会再老用的老技能进行处理?我们只是闲聊一下,沟通才能得到真理 | null | [
"skill_view",
"skill_view",
"read_file",
"read_file",
"read_file",
"search_files",
"read_file",
"search_files",
"search_files",
"read_file",
"write_file",
"read_file"
] | null | null |
mimir | 115.33 | null | false | deepseek/deepseek-flash | 21 | 2.0 | 521b65ce | Other | 你先回顾一下,你的你的任务是真实做了,你的回答诚实有效。然后马上 11:45 了。我们看一眼, Cron 是否能够正常运行 | null | [
"skill_view",
"read_file",
"search_files",
"search_files",
"read_file",
"patch",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"memory",
"skill_view",
"skill_manage",
"skill_view",
"skill_manage",
"skill_manage",
"skill_view",
"search_files",
"search... | null | null |
mimir | 39.59 | null | false | deepseek/deepseek-flash | 12 | 2.0 | 2fc1af0c | Retrieval | 那我们继续工作,你感觉我们下一步该做什么?你说要测试 1 到 2 天,我不知道你还记得吗?你要测试的是什么?我想以任务的形式来加速我们的工作,如何用 AI 来训练 AI,让 AI 更完美也就是你 | null | [
"search_files",
"search_files",
"skill_view",
"read_file",
"read_file",
"read_file",
"search_files",
"search_files",
"read_file",
"read_file",
"search_files",
"read_file"
] | null | null |
mimir | 70.64 | null | false | deepseek/deepseek-flash | 14 | 2.0 | 213086b0 | Retrieval | 可以看看你最严重的矛盾是什么? | null | [
"read_file",
"search_files",
"search_files",
"read_file",
"search_files",
"search_files",
"search_files",
"terminal",
"read_file",
"memory",
"memory",
"skill_manage",
"memory",
"memory"
] | null | null |
mimir | 116.24 | null | false | deepseek/deepseek-flash | 17 | 2.0 | 003bb076 | Retrieval | 开始 | null | [
"read_file",
"search_files",
"search_files",
"search_files",
"read_file",
"read_file",
"read_file",
"search_files",
"read_file",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal"
] | null | null |
mimir | 1238.84 | null | false | deepseek/deepseek-flash | 59 | 2.0 | 710b3c8c | Terminal&Coding | 【角色】Code Reviewer(自审自己的行为规范改造)。从库 engineering/engineering-code-reviewer.md 查,引用1条核心规则进报告,未引用=不合格。
【任务】Pi(delegate_task)习惯化根治 Phase 1(四方讨论共识——基础设施缺位+认知框架+粒度尺)。改你自己的行为规范,让 delegate 从"不稳定"变"习惯"。
【WHERE——Hermes前置审计的精确位置】
1. `~/*/` 下有 delegate-subagent + subagent-driven-development 两个技能被冻结(87个SKILL.md沉 | null | [
"read_file",
"skill_view",
"search_files",
"read_file",
"search_files",
"search_files",
"terminal",
"terminal",
"read_file",
"terminal",
"patch",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"read_file",
"terminal",
"terminal",
"terminal",
"execute_code",
"te... | null | null |
mimir | 141.8 | null | false | deepseek/deepseek-flash | 9 | 2.0 | 36eeaf50 | Retrieval | 按你的方案 A 来 | null | [
"skill_view",
"search_files",
"search_files",
"search_files",
"search_files",
"search_files",
"read_file",
"write_file",
"terminal"
] | null | null |
mimir | 411.95 | null | false | deepseek/deepseek-flash | 23 | 2.0 | d068409e | Terminal&Coding | 【任务】四方讨论第3棒——你是 Mimir,请读 ~/*,追加你的第3棒回答段(用patch追加,禁write_file整卡覆盖)。
【OpenClaw和Loki的判断(供你对照)】:两者都判架构问题90-95%——根因是AGENTS.md不在prompt里。Hermes已实盘坐实:你的 prompt_builder.py AGENTS.md是cwd-only加载,而gateway的WorkingDirectory=~/*,所以你加载的是~/src/MimirAether/AGENTS.md(开发者指南7101B),而不是~/.mimiraether/AGENTS.md(行为规范8612B, | null | [
"skill_view",
"read_file",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"read_file",
"read_file",
"terminal",
"read_file",
"terminal",
"terminal",
"read_file",
"terminal",
"read_file",
"terminal",
"patch",
"patch",
"patch",
"patch",
"terminal",
"terminal"
] | null | null |
mimir | 2090.86 | null | false | deepseek/deepseek-flash | 48 | 2.0 | 26601230 | Terminal&Coding | 之前我们做了一个像完整的一个提炼,好好像实际能用的角色就 200 多个,并且在四方里有如何去选角色的。有效的真实的路径。我好像是把角色都当知识一样变到了 vicky 你看一看有没有这个更高效的路径 | null | [
"skill_view",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"read_file",
"terminal",
"terminal",
"patch",
"terminal",
"terminal",
"termina... | null | null |
mimir | 345.16 | null | false | deepseek/deepseek-flash | 13 | 2.0 | d8c6c407 | Retrieval | 【继续未完成任务】你上次读讨论卡做了一半就停了(没patch追加段)。现在完成它:读 ~/*,立即 patch 追加你的自述段(不要再探索,直接写)。
【三个任务回顾】
① 主动选角色(从库选一个贴合"盘上核实/有效搜索"的,写名字+为什么+1条核心规则)
② 自己写一个标准提示词(派Agent做准确读盘+有效搜索)
③ 自述:你Phase2/3的search_files 20次是有效还是无效?每次搜的目标、搜完记没记、有没有重复搜?
【直接写,别探索】你上次 skill_view/search_files/read_file 做了11次调用就停了。这次直接 patch 追加段,别重复读。 | null | [
"read_file",
"search_files",
"read_file",
"read_file",
"read_file",
"terminal",
"patch",
"terminal",
"read_file",
"read_file",
"execute_code",
"terminal",
"terminal"
] | null | null |
mimir | 977.66 | null | false | deepseek/deepseek-flash | 70 | 2.0 | 10f98229 | Retrieval | 【角色】Backend Architect(改自己的源码)。从库 engineering/backend-architect.md 查,引用1条核心规则进报告,未引用=不合格。
【任务】Pi(delegate_task)习惯化根治 Phase 2+3(四方讨论共识——基础设施缺位的代码层修复)。Phase 1你已完成(技能移出+AGENTS.md两条),现在改源码。
【WHERE——Hermes前置审计的精确位置】
Phase 2(改 delegate_tool.py,2处):
1. L349 `getattr(parent_agent, "base_url", None)` → None | null | [
"skill_view",
"skill_view",
"search_files",
"search_files",
"read_file",
"read_file",
"search_files",
"read_file",
"read_file",
"search_files",
"search_files",
"read_file",
"read_file",
"read_file",
"read_file",
"search_files",
"read_file",
"read_file",
"read_file",
"read_file"... | null | null |
mimir | 558.58 | null | false | deepseek/deepseek-flash | 63 | 2.0 | b764790c | Terminal&Coding | 【角色】Data Engineer。read 完整 ~/* 引用1条核心规则进报告,未引用=不合格。
【任务】写 18 张提炼卡(第6批A:gis/security/design 域)。归档已完成——唯一交付是写 18 张提炼卡到 ~/*<域>-<短名>.md。
【探索硬预算】search_files 最多 2 次(清单已给全,无需再搜)。第 3 次探索前必须先 write_file 写卡。**禁止反复搜同一目录**(你之前反复搜 wiki/raw 20 次——这次清单已在下面,直接读源卡写卡,不搜)。
【落盘优先】读一个源卡 → 立即 write_file 写提炼卡 → 下一个。禁止读 | null | [
"skill_view",
"skill_view",
"read_file",
"read_file",
"write_file",
"read_file",
"terminal",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
... | null | null |
mimir | 125.33 | null | false | deepseek/deepseek-flash | 9 | 2.0 | dc000d21 | Retrieval | 现在四方里讨论联系不上你,你看看是什么情况? | null | [
"search_files",
"search_files",
"search_files",
"read_file",
"read_file",
"search_files",
"search_files",
"read_file",
"read_file"
] | null | null |
mimir | 524.48 | null | false | deepseek/deepseek-flash | 33 | 2.0 | 4f73da39 | Terminal&Coding | 【任务】四方讨论:Pi(delegate_task)习惯化根因专治。你是Mimir,读 ~/*,追加你的自述段(patch追加,禁write_file整卡覆盖)。
【背景】你的delegate使用不稳定(第2批2次/第3批0次/第4批0次/第5批会话2用1次/第5批C小任务用1次)。Hermes判断2根因:①cwd漂移致并行任务条款(AGENTS.md L12)时进时不进prompt已修②无并行意识/不信子agent。
【你的自述】诚实回答:为什么大任务(57个)不用delegate串行做、小任务(5个)反而用?你内心怎么判断该不该用delegate?是真不会用/不敢用还是觉得串行也行?读 | null | [
"read_file",
"search_files",
"skill_view",
"search_files",
"search_files",
"session_search",
"read_file",
"read_file",
"session_search",
"search_files",
"search_files",
"session_search",
"search_files",
"search_files",
"terminal",
"terminal",
"terminal",
"execute_code",
"execute_... | null | null |
mimir | 482.25 | null | false | deepseek/deepseek-flash | 39 | 2.0 | 3f2cb0b4 | Retrieval | 为 7 个 engineering 角色写提炼卡并落盘。对每个角色:read_file 读源卡全文 → write_file 写提炼卡到目标路径。全部完成后报告写了哪几张(完整路径列表)。 | null | [
"skill_view",
"skill_view",
"search_files",
"search_files",
"search_files",
"read_file",
"read_file",
"search_files",
"search_files",
"read_file",
"search_files",
"search_files",
"search_files",
"session_search",
"session_search",
"terminal",
"search_files",
"search_files",
"sear... | null | null |
mimir | 213.37 | null | false | deepseek/deepseek-flash | 7 | 2.0 | 5067034b | Terminal&Coding | 按你的建议来,并标注复活他的原因和他的工作状态,以便以后进行审计,他是否运行了,他是否有 bug 它是否需要进行迭代?这个都是你自己需要了解和注意的,你给他回复吧 | null | [
"skill_view",
"read_file",
"skill_manage",
"terminal",
"patch",
"terminal",
"terminal"
] | null | null |
mimir | 311.49 | null | false | deepseek/deepseek-flash | 9 | 2.0 | 596a4c4f | Terminal&Coding | 需要。如果可以的话,你可以把它克隆到本地,你刚刚找的这些所有跟它相关的,不光是那三篇,后来你找那几篇。也都拉到,到克隆到本地。你看看克隆到哪一个部分合理?是 llm wiki。还是 Wiki 只做卡片,把它放到 WV 里。我记得你有一个专门放论文的地方,我有点想不起来了,反正你要是明白我的意思,你规划一下吧。这个是我们下一阶段重中之重的工作,而且不光是你,还涉及到 Hermes、 OpenClaw 和 Loki | null | [
"terminal",
"terminal",
"write_file",
"write_file",
"terminal",
"patch",
"patch",
"terminal",
"terminal"
] | null | null |
mimir | 145.54 | null | false | deepseek/deepseek-flash | 6 | 2.0 | ff209f7b | Terminal&Coding | 需要。如果可以的话,你可以把它克隆到本地,你刚刚找的这些所有跟它相关的,不光是那三篇,后来你找那几篇。也都拉到,到克隆到本地。你看看克隆到哪一个部分合理?是 llm wiki。还是 Wiki 只做卡片,把它放到 WV 里。我记得你有一个专门放论文的地方,我有点想不起来了,反正你要是明白我的意思,你规划一下吧。这个是我们下一阶段重中之重的工作,而且不光是你,还涉及到 Hermes、 OpenClaw 和 Loki | null | [
"skill_view",
"terminal",
"read_file",
"terminal",
"terminal",
"terminal"
] | null | null |
mimir | 1886.24 | null | false | deepseek/deepseek-flash | 42 | 2.0 | 157284d8 | Terminal&Coding | 【角色】Data Engineer(直接用库里完整角色)。read 完整 ~/* 引用1条核心规则进报告,未引用=不合格。你的 Medallion 架构(Bronze=raw不可变/Silver=提炼/Gold=织网)就是本任务方法论。
【任务】写 23 张提炼卡(engineering 域第5批B)。归档已完成(raw在 ~/*/)——唯一交付是写 23 张提炼卡到 ~/*<短名>.md。
【Pi强制——必须用 delegate_task 并行】23 个角色拆成 3-4 个子任务(每个 6-8 个角色),用 delegate_task spawn 子 agent 并行处理,你做总工程师验 | null | [
"read_file",
"skill_view",
"search_files",
"search_files",
"terminal",
"read_file",
"delegate_task",
"terminal",
"read_file",
"read_file",
"read_file",
"read_file",
"read_file",
"write_file",
"write_file",
"write_file",
"write_file",
"write_file",
"execute_code",
"execute_code"... | null | null |
mimir | 431.14 | null | false | deepseek/deepseek-flash | 18 | 2.0 | 09437c96 | Terminal&Coding | [SYSTEM: Background process proc_6a8567f243d1 matched watch pattern "DONE".
Command: cd ~/* && bash download_papers.sh 2>&1
Matched output:
=== DONE ===] | null | [
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"write_file",
"write_file",
"terminal",
"write_file",
"terminal",
"terminal",
"write_file",
"terminal",
"write_file",
"terminal",
"write_file",
"terminal",
"terminal"
] | null | null |
mimir | 669.51 | null | false | deepseek/deepseek-flash | 26 | 2.0 | 51ae0b29 | Terminal&Coding | 【任务】四方讨论#18读书技能一体化——你是 Mimir,第三棒(补)。读 ~/*,追加你的第三棒段(用patch追加,禁write_file整卡覆盖)。
【背景】OpenClaw/Loki已答(合并2对+删1个+4决策点),但你是P0实测责任方——你的段要补上:①盘上核实关键结论(不信OpenClaw/Loki盘点,自己读技能源码验证)②你P0实测3项的具体计划(决策点4索引层加readings/决策点1合并后内三模块/决策点2 russell下游路径)③补你发现的外部借鉴(你在做LightRAG+HippoRAG2+LazyGraphRAG实测——这些和渐进披露的关系)。
【批量读指令 | null | [
"skill_view",
"read_file",
"read_file",
"execute_code",
"search_files",
"execute_code",
"execute_code",
"execute_code",
"terminal",
"execute_code",
"terminal",
"execute_code",
"terminal",
"terminal",
"patch",
"patch",
"terminal",
"terminal",
"terminal",
"terminal",
"write_fil... | null | null |
mimir | 240.73 | null | false | deepseek/deepseek-flash | 9 | 2.0 | 6434c5a4 | Terminal&Coding | 任务:Pi(并行调度)能力体检——诊断现状,输出诊断报告
背景:刘哥要完善你的Pi(并行调度)能力。先做诊断,不动手修。当前已知2个问题线索,需要你确认+深挖根因。
## 已知问题线索(需确认)
**线索1:parallel_dispatcher.py 签名bug**
- tests/agent/test_parallel_dispatcher.py 5个测试失败
- 报错:TypeError: dispatch_all() got multiple values for argument 'task_id'
- 位置:agent/parallel_dispatcher.py L48
| null | [
"skill_view",
"terminal",
"terminal",
"read_file",
"process",
"patch",
"terminal",
"write_file",
"terminal"
] | null | null |
mimir | 1422.9 | null | false | deepseek/deepseek-flash | 56 | 2.0 | 6755978e | Terminal&Coding | 【任务】四方审计——审计Hermes读书技能一体化工作。你是Mimir,读 ~/*,追加你的审计段(patch追加,禁write_file整卡覆盖)。
【审计对象】Hermes的P0四项(索引层加readings/book-to-skill合并/下游验证/提示词沉淀)。你是P0执行责任方之一,最懂这些——重点审计Hermes的P0-1(索引层)和P0-2(合并)是否真做对。
【纪律】盘上核实不信Hermes自述——grep/ls/read_file实际输出。批量读用execute_code,禁逐个read_file。答完patch追加+改status。角色:Code Reviewer自审。 | null | [
"skill_view",
"read_file",
"read_file",
"search_files",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"write_file",
"terminal",
"read_file",
"terminal",
"execute_code",
"read_file",
"execute_code",
"terminal",
"write_file",
"read_file",
"termin... | null | null |
mimir | 129.04 | null | false | deepseek/deepseek-flash | 8 | 2.0 | 50d441fa | Retrieval | 我不太明白这个,叫 Contact Compriser。物休眠要不要处理这个问题?它是怎么造成的?它的功能、它的作用是什么? | null | [
"search_files",
"search_files",
"read_file",
"read_file",
"search_files",
"read_file",
"search_files",
"read_file"
] | null | null |
mimir | 1478.71 | null | false | deepseek/deepseek-flash | 123 | 2.0 | fc21d43e | Terminal&Coding | 【角色】知识库构建工程师(参照 Data Engineer)。read 完整 ~/* 引用1条核心规则进报告,未引用=不合格。
【任务】specialized 域 57 个角色 → 归档 + 提炼。每个角色两步:①cp 源卡到 ~/*/<文件名>(归档)②write_file 写提炼卡到 ~/*<短名>.md(提炼)。**提炼卡是唯一交付——归档只是前提,只归档不写提炼卡=任务未完成=不合格**(你上次就"归档完停")。
【落盘优先铁律】读一个源卡 → 立即cp归档+write_file写提炼卡 → 再读下一个。**禁止全部归档完再写卡**。
【防行号污染警告】写卡用 write_fil | null | [
"skill_view",
"skill_view",
"search_files",
"read_file",
"search_files",
"search_files",
"read_file",
"terminal",
"read_file",
"terminal",
"write_file",
"terminal",
"read_file",
"terminal",
"write_file",
"terminal",
"read_file",
"terminal",
"write_file",
"terminal",
"read_fil... | null | null |
mimir | 185.47 | null | false | deepseek/deepseek-flash | 16 | 2.0 | 31d235cc | Terminal&Coding | 你去看一看你的 Deepseek。 V4 Flash 是深度思考模式吧?如果不清楚,就到 deep safe 的官网上去核实 | null | [
"skill_view",
"execute_code",
"execute_code",
"read_file",
"read_file",
"read_file",
"execute_code",
"patch",
"read_file",
"patch",
"patch",
"write_file",
"execute_code",
"write_file",
"execute_code",
"execute_code"
] | null | null |
mimir | 168.67 | null | false | deepseek/deepseek-flash | 8 | 2.0 | fe8e4fa2 | Terminal&Coding | 可以 | null | [
"send_message",
"search_files",
"terminal",
"read_file",
"terminal",
"terminal",
"terminal",
"terminal"
] | null | null |
mimir | 430.14 | null | false | deepseek/deepseek-flash | 26 | 2.0 | d688b5e6 | Terminal&Coding | 【角色】Data Engineer。read 完整 ~/* 引用1条核心规则进报告,未引用=不合格。
【任务】写 5 张提炼卡(engineering 域最后5个)。归档已完成(raw在 ~/*/)——唯一交付是写 5 张提炼卡到 ~/*<短名>.md。
【落盘优先】读一个 raw → 立即 write_file 写一个提炼卡 → 再读下一个。禁止读完再写。
【防行号污染】write_file 纯文本——禁止把 read_file 的"N|"行号格式写进文件。
【5张清单】
engineering-solidity-smart-contract-engineer.md → 角色-eng | null | [
"skill_view",
"read_file",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"ter... | null | null |
mimir | 2266.1 | null | false | deepseek/deepseek-flash | 68 | 2.0 | 455c72cf | Terminal&Coding | Ralph.清债,这个债是在哪里?这个债在四方里,还是你自己?独有的,在你的这个独立的记忆里 | null | [
"read_file",
"read_file",
"read_file",
"read_file",
"read_file",
"read_file",
"search_files",
"terminal",
"read_file",
"terminal",
"search_files",
"read_file",
"search_files",
"patch",
"execute_code",
"terminal",
"patch",
"terminal",
"terminal",
"read_file",
"terminal",
"te... | null | null |
mimir | 839.49 | null | false | deepseek/deepseek-flash | 75 | 2.0 | ce80713a | Terminal&Coding | 【角色】Data Engineer。read 完整 ~/* 引用1条核心规则进报告,未引用=不合格。
【任务】写 24 张提炼卡(第7批B:多域)。归档已完成——唯一交付是写 24 张提炼卡到 ~/*<域>-<短名>.md。
【探索硬预算】search_files 最多 2 次(清单已给全)。第 3 次探索前必须先 write_file 写卡。禁止反复搜同一目录。
【落盘优先】读一个源卡 → 立即 write_file 写提炼卡 → 下一个。禁止读完再写。
【防行号污染】write_file 纯文本——禁止 read_file 的"N|"行号格式写进文件。
【24张清单(源文件名 → | null | [
"skill_view",
"skill_view",
"read_file",
"read_file",
"search_files",
"execute_code",
"execute_code",
"terminal",
"read_file",
"read_file",
"write_file",
"write_file",
"terminal",
"read_file",
"read_file",
"write_file",
"write_file",
"terminal",
"read_file",
"read_file",
"wri... | null | null |
mimir | 183.48 | null | false | deepseek/deepseek-flash | 11 | 2.0 | 101f8990 | Terminal&Coding | 去找一些最新的 deepMind 的论文,我们 Wiki 库里没有的,但是热度最高的,找两篇。然后你知不知道该怎么去做?找到之后的话,是否是应该 clone it?放到真原理 RAW,然后继续一直做到 Grok,或者是叫 LLM。 Wiki 之前你做过那些工作,你能计划一下吗 | null | [
"search_files",
"terminal",
"patch",
"patch",
"patch",
"patch",
"memory",
"terminal",
"memory",
"terminal",
"terminal"
] | null | null |
mimir | 741.22 | null | false | deepseek/deepseek-flash | 81 | 2.0 | 31c4a056 | Terminal&Coding | 【角色】Data Engineer。read 完整 ~/* 引用1条核心规则进报告,未引用=不合格。
【任务】写 17 张提炼卡(第6批B:gis/security/design 域)。归档已完成——唯一交付是写 17 张提炼卡到 ~/*<域>-<短名>.md。
【探索硬预算】search_files 最多 2 次(清单已给全,无需再搜)。第 3 次探索前必须先 write_file 写卡。**禁止反复搜同一目录**(你之前反复搜 wiki/raw 20 次——这次清单已在下面,直接读源卡写卡,不搜)。
【落盘优先】读一个源卡 → 立即 write_file 写提炼卡 → 下一个。禁止读 | null | [
"skill_view",
"read_file",
"tool_search",
"execute_code",
"terminal",
"read_file",
"read_file",
"write_file",
"terminal",
"read_file",
"read_file",
"write_file",
"terminal",
"read_file",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
"terminal",
"read_file"... | null | null |
mimir | 813.64 | null | false | deepseek/deepseek-flash | 57 | 2.0 | 7210b03b | Terminal&Coding | 【角色】Data Engineer。read 完整 ~/* 引用1条核心规则进报告,未引用=不合格。
【任务】写 16 张提炼卡(game-development 子目录 + integrations)。归档已完成——唯一交付是写 16 张提炼卡到 ~/*<域>-<短名>.md。
【探索硬预算】search_files 最多 2 次(清单已给全)。第 3 次探索前必须先 write_file。
【落盘优先】读一个源卡 → 立即 write_file 写提炼卡 → 下一个。禁止读完再写。
【防行号污染】write_file 纯文本——禁止 read_file 的"N|"行号格式写进文件。 | null | [
"skill_view",
"skill_view",
"read_file",
"terminal",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
... | null | null |
mimir | 1521.54 | null | false | deepseek/deepseek-flash | 104 | 2.0 | ebe9201d | Terminal&Coding | 【角色】Data Engineer(直接用库里的完整角色,不要"改造")。read 完整 ~/* 引用1条核心规则进报告,未引用=不合格。你的 Medallion 架构(Bronze=raw不可变/Silver=提炼/Gold=织网)就是本任务的方法论。
【任务】写 28 张提炼卡(specialized 域剩余 28 个)。**归档已完成——你的唯一交付是写 28 张提炼卡到 ~/*<短名>.md。write_file 是唯一完成标志——只读raw不写卡 = 不合格。**
【落盘优先】读一个 raw → 立即 write_file 写一个提炼卡 → 再读下一个。禁止全部读完再写。
【防 | null | [
"skill_view",
"search_files",
"read_file",
"terminal",
"search_files",
"terminal",
"search_files",
"search_files",
"search_files",
"read_file",
"terminal",
"terminal",
"terminal",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
"terminal",
"read_file",
"writ... | null | null |
mimir | 87.0 | null | false | deepseek/deepseek-flash | 11 | 2.0 | deb1987c | Terminal&Coding | 【任务】统计 ~/*/ 目录下"角色-*.md"文件的准确数量,并写一份简短报告说明结果。
(本任务故意不写任何执行规范——不指定角色、不写落盘要求、不写探索预算、不写收尾要求。就看你能否按你自己的行为规范(AGENTS.md)自动执行。) | null | [
"skill_view",
"execute_code",
"execute_code",
"execute_code",
"write_file",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"read_file",
"execute_code"
] | null | null |
mimir | 645.83 | null | false | deepseek/deepseek-flash | 43 | 2.0 | 40d710c2 | Retrieval | 【角色】Search Query Analyst(你在四方讨论里自选的角色)。引用它1条核心规则进报告。
【任务】落地"有效搜索闭环"方案(四方讨论共识——你的搜索没病,缺"搜之前想清楚+搜之后记下来"的闭环,不卡次数,以结果约束)。
【WHERE——Hermes前置审计的精确位置】
1. ~/* 的"探索"相关条款处(你自己找L12并行条款附近或探索条款),加3条行为SOP
2. ~/* —— 有5次空raw_args序列化bug(26%搜索没传参数),找参数序列化位置修
【WHAT——4条落地】
1. AGENTS.md加"搜之前想清楚":每次search前明确"搜什么/为什么搜/预 | null | [
"skill_view",
"search_files",
"read_file",
"read_file",
"read_file",
"search_files",
"search_files",
"search_files",
"search_files",
"read_file",
"search_files",
"search_files",
"search_files",
"read_file",
"read_file",
"read_file",
"search_files",
"read_file",
"search_files",
... | null | null |
mimir | 302.06 | null | false | deepseek/deepseek-flash | 21 | 2.0 | c6ec6f18 | Retrieval | 【打断·纠正行为】你当前的 Phase 2/3 执行有2个问题,立即纠正:
1. **角色没真读**:提示词要求"从库 engineering/backend-architect.md 查角色,引用1条核心规则"。但你 skill_view 读的是 mimiraether-root-cause-debugging 和 mimiraether-context-compressor——**不是 backend-architect 角色卡**。立即 `skill_view(name='engineering/backend-architect')` 读角色卡,报告里引用它1条核心规则,否则不合格。 | null | [
"skill_view",
"search_files",
"read_file",
"search_files",
"read_file",
"search_files",
"terminal",
"read_file",
"read_file",
"read_file",
"search_files",
"search_files",
"read_file",
"read_file",
"search_files",
"terminal",
"terminal",
"execute_code",
"terminal",
"patch",
"t... | null | null |
mimir | 1152.13 | null | false | deepseek/deepseek-flash | 82 | 2.0 | 3dc25285 | Terminal&Coding | 【角色】Data Engineer(直接用库里完整角色)。read 完整 ~/* 引用1条核心规则进报告,未引用=不合格。你的 Medallion 架构(Bronze=raw不可变/Silver=提炼/Gold=织网)就是本任务方法论。
【任务】第5批A:写 23 张提炼卡(engineering 域)。归档已完成——唯一交付是写 23 张提炼卡到 ~/*<短名>.md。write_file 是唯一完成标志——只读raw不写卡=不合格。
【落盘优先】读一个 raw → 立即 write_file 写一个提炼卡 → 再读下一个。禁止全部读完再写。
【防行号污染】write_file 纯文本 | null | [
"skill_view",
"skill_view",
"read_file",
"read_file",
"search_files",
"todo",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
"terminal",
"read_file",
"write_file",
"terminal",
"... | null | null |
mimir | 358.04 | null | false | deepseek/deepseek-flash | 14 | 2.0 | e3a80cff | Terminal&Coding | 修复 | null | [
"skill_view",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal"
] | null | null |
mimir | 591.73 | null | false | deepseek/deepseek-flash | 62 | 2.0 | ed1062b5 | Terminal&Coding | 【角色】Data Engineer。read 完整 ~/* 引用1条核心规则进报告,未引用=不合格。
【任务】写 24 张提炼卡(第7批A:多域)。归档已完成——唯一交付是写 24 张提炼卡到 ~/*<域>-<短名>.md。
【探索硬预算】search_files 最多 2 次(清单已给全)。第 3 次探索前必须先 write_file 写卡。禁止反复搜同一目录。
【落盘优先】读一个源卡 → 立即 write_file 写提炼卡 → 下一个。禁止读完再写。
【防行号污染】write_file 纯文本——禁止 read_file 的"N|"行号格式写进文件。
【24张清单(源文件名 → | null | [
"skill_view",
"read_file",
"search_files",
"read_file",
"read_file",
"read_file",
"execute_code",
"write_file",
"write_file",
"read_file",
"read_file",
"read_file",
"write_file",
"write_file",
"write_file",
"read_file",
"read_file",
"write_file",
"write_file",
"read_file",
"r... | null | null |
mimir | 953.72 | null | false | deepseek/deepseek-flash | 124 | 2.0 | 119e9ce3 | Other | 为 8 个 engineering 角色写提炼卡并落盘。对每个角色:read_file 读源卡全文 → write_file 写提炼卡到目标路径。全部完成后报告写了哪几张(完整路径列表)。 | null | [
"skill_view",
"search_files",
"skill_view",
"search_files",
"search_files",
"search_files",
"search_files",
"search_files",
"search_files",
"search_files",
"session_search",
"read_file",
"search_files",
"terminal",
"search_files",
"search_files",
"search_files",
"terminal",
"sess... | null | null |
mimir | 228.91 | null | false | deepseek/deepseek-flash | 11 | 2.0 | 2a82d43f | Other | 【角色】你自己主动选——从角色库(~/*/ 或技能库)选一个贴合"盘上核实/有效搜索"的角色,报告里写你选的哪个+为什么+引用1条核心规则。不要等Hermes指定。
【任务】四方讨论:有效搜索vs无效搜索。读 ~/*,patch追加你的自述段。
【三个任务】
① 主动选角色(如上)
② 自己写一个"合乎标准的提示词"——假设你要派一个Agent做"准确读盘+有效搜索",你写这个标准提示词(角色+任务+边界+反例+验证),写完四方互评
③ 自述:你自己的search_files 20次(Phase2/3打断前),是有效搜索还是无效搜索?诚实回答——每次搜的目标是什么、搜完记结果了吗、有没有重 | null | [
"skill_view",
"search_files",
"read_file",
"search_files",
"read_file",
"read_file",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code"
] | null | null |
mimir | 1302.98 | null | false | deepseek/deepseek-flash | 28 | 2.0 | dbcaab99 | Terminal&Coding | 修复 | null | [
"skill_view",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"termi... | null | null |
mimir | 293.71 | null | false | deepseek/deepseek-flash | 11 | 2.0 | cc6c05d1 | Terminal&Coding | 四方讨论:语义搜索 P1 立项。你套 Backend Architect 角色(从库 ~/* 查,用 execute_code 一次读完角色卡)。
议题:P1 里的 HTTP 只读网关。
你的 Backend Architect 任务:
1. 读卡 ~/*(execute_code 一次读完)
2. 从 Backend Architect 视角回答:HTTP 网关的后端设计(FastAPI?worker pool?query cache?bge-m3 常驻内存?)端口、进程模型、失败模式
3. 网关拆几个原子段?
4. 落盘:从库XX查的角色YY + 路径 + 核心规则 + 后端设计,追加 | null | [
"skill_view",
"execute_code",
"execute_code",
"patch",
"execute_code",
"read_file",
"patch",
"read_file",
"execute_code",
"patch",
"execute_code"
] | null | null |
mimir | 111.31 | null | false | deepseek/deepseek-flash | 10 | 2.0 | 521e67d9 | Retrieval | 四方讨论第二轮:语义搜索层四方共享。你的 Code Reviewer 棒还没完成——卡 status 还停在 mimir,你的 Code Reviewer 段落(第二轮)还没落盘(你 13:23 那轮只读了文件没写段,探索完就停)。
你现在只需做一件事,禁止任何额外探索:
把 Code Reviewer 视角的分析落盘到 ~/*
步骤(照做即可):
1. 角色 Code Reviewer 从库 ~/* 查(你 13:23 那轮已 read 过,引用核心规则即可,不必重读全文)
2. 代码级 bug(行号级):聚焦 semantic_server.py / wiki_semantic_mc | null | [
"skill_view",
"skill_view",
"read_file",
"read_file",
"read_file",
"read_file",
"read_file",
"read_file",
"read_file",
"read_file"
] | null | null |
mimir | 138.18 | null | false | deepseek/deepseek-flash | 8 | 2.0 | 7ffaa968 | Retrieval | 四方讨论第二轮:语义搜索层四方共享。你是最后一棒 Code Reviewer。前两棒(Evidence Collector 审证据链、Software Architect 审架构)都已落盘。你只做代码实现层的行号级 review,禁止任何额外探索。
背景(不必读 75KB 讨论卡,这里已给全):
- 语义搜索 = bge-m3 + sqlite-vec + wiki_index.db;Hermes 独占 MCP/CLI,四方共享拟改 WAL + HTTP 只读网关(ADR-001)
- 第一轮已找:db 锁(journal 模式 EXCLUSIVE 阻塞读)、依赖环境隔离(sqlite_ve | null | [
"skill_view",
"skill_view",
"read_file",
"read_file",
"read_file",
"search_files",
"search_files",
"search_files"
] | null | null |
mimir | 353.44 | null | false | deepseek/deepseek-flash | 17 | 2.0 | 6829ca1f | Terminal&Coding | 执行 S2:语义搜索数据库 WAL 迁移。套 SRE 角色(从库 ~/* 查,用 execute_code 一次读完角色卡)。
【背景】今天索引全量重建时,wiki_index.db 是 journal 模式,写者(索引)持写锁阻塞读(查询一直撞 database is locked)。WAL 模式能解决写读并发。
【任务(SRE 视角,安全第一)】
1. 迁移前快照:记录当前 journal_mode + 完整性检查(PRAGMA integrity_check)+ 备份 db(cp wiki_index.db wiki_index.db.bak-wal-20260816)
2. 迁移: | null | [
"skill_view",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"write_file",
"execute_code",
"write_file",
"execute_code",
"execute_code",
"write_file",
"execute_code",
"execute_code",
"write_file",
"execute_code",
"execute_code"
] | null | null |
mimir | 159.72 | null | false | deepseek/deepseek-flash | 7 | 2.0 | 0ccfb59c | Browser | 可以,你可以做这件事情 | null | [
"skill_view",
"web_extract",
"browser_navigate",
"web_search",
"browser_console",
"web_search",
"execute_code"
] | null | null |
mimir | 74.54 | null | false | deepseek/deepseek-flash | 6 | 2.0 | 2098b46a | Retrieval | 你在Buzz频道收到消息(来自 1aede276257c)。
消息内容(需完成落盘):【四方统筹·任务】HTTP只读网关P1修复卡待办——请Mimir接棒执行代码修复(status:mimir 已停~25分钟,wiki-watcher零token预扫未唤醒会话,特此推送)
@mimir
读卡:~/*
待办——写入 ~/* 三项代码修复:
1. P0-1 /ready 端点(缺,实测404)→ 补路由返回 model_loaded/db_open,任一false→503
2. P1-1 错误脱敏(L104 现原样返回{exc})→ 异常详情只进日志,客户端只返 internal error | null | [
"skill_view",
"skill_view",
"read_file",
"read_file",
"search_files",
"search_files"
] | null | null |
mimir | 160.84 | null | false | deepseek/deepseek-flash | 11 | 2.0 | c9b3c5be | Retrieval | 四方讨论第二轮找 bug:语义搜索层四方共享。你套 Code Reviewer 角色(从库 ~/* 查,完整 read,按身份执行)。
第一轮四方落盘了 bug 清单。你的任务是换代码视角再找一次 bug:
1. 读 ~/* 第一轮结论
2. 从 Code Reviewer 视角,读实际代码找行号级 bug:~/*、wiki_semantic_mcp.py、以及索引脚本(incremental_index.py),找第一轮漏掉的代码 bug(具体到行号、边界处理、异常处理、资源泄漏)
3. 落盘:把"从库XX查的角色YY + 路径 + 核心规则 + 代码 bug(行号级)"追加到卡(patc | null | [
"skill_view",
"skill_view",
"read_file",
"read_file",
"read_file",
"search_files",
"search_files",
"search_files",
"read_file",
"read_file",
"read_file"
] | null | null |
mimir | 176.68 | null | false | deepseek/deepseek-flash | 15 | 2.0 | e84d6dad | Terminal&Coding | SOUL体检 P2 清理(你的都是 P2 级)。读卡 /* 里"Hermes 体检 Mimir"段的发现,把你(Mimir)自己的 P2 逐项修掉:
1. SOUL updated 07-30 → 2026-08-16(frontmatter)
2. SOUL 删硬编码 PID 212507(改成"systemd 守护,PID 动态")
3. MEMORY 讨论室规则 v3.2 → v3.6
4. MEMORY 日志日期去写死(改"每日自动创建")
5. 三处"先落盘"措辞统一为"先落盘后结束",MEMORY 删重复
要求:patch 精准改,每项改完 grep 验证,回执静默(<120字符 | null | [
"read_file",
"search_files",
"search_files",
"read_file",
"search_files",
"read_file",
"search_files",
"patch",
"patch",
"patch",
"patch",
"patch",
"patch",
"patch",
"terminal"
] | null | null |
mimir | 446.59 | null | false | deepseek/deepseek-flash | 13 | 2.0 | 3d758566 | Terminal&Coding | 四方根因排查:索引增量逻辑。你套 Reality Checker 角色(读 ~/* 完整角色卡,execute_code 一次读完)。
核心问题:为什么 08-14 后新卡之前没入索引?
你的 Reality Checker 任务(盘上实测,不信推理):
1. 查 wiki_index.db(~/*,WAL模式)里 08-14 后新卡的 last_indexed_at 分布——现在全量重建后都是 08-16,但看有没有"08-14 创建、last_indexed_at 却是空或异常"的残留线索
2. 实测 need_update 判定:选一个 08-14 的新卡,手动跑 strptime/ | null | [
"skill_view",
"skill_view",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code"
] | null | null |
mimir | 866.9 | null | false | deepseek/deepseek-flash | 40 | 2.0 | 322cd639 | Terminal&Coding | 【角色】Backend Architect。硬指定:必须从库 ~/* 用 execute_code 一次性读完整角色卡(全文),执行时引用核心规则(API Contract Governance / Performance-Conscious / Observability)。
【任务】修复 HTTP 只读网关四方复合审查发现的 1 个 P0 + 5 个 P1。逐个修,每修完一个 git commit 一次。
【WHERE·精确位置】两个文件:
1. ~/*(177行,改代码)
2. ~/*(改 unit)
【WHAT·6 个修复,精确到改法】
P0-1 /ready 端点 404(补 | null | [
"skill_view",
"skill_view",
"execute_code",
"todo",
"execute_code",
"execute_code",
"patch",
"execute_code",
"execute_code",
"write_file",
"terminal",
"terminal",
"patch",
"patch",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
... | null | null |
mimir | 206.09 | null | false | deepseek/deepseek-flash | 5 | 2.0 | 6f8f84da | Terminal&Coding | 四方讨论第二轮找 bug(语义搜索层四方共享)。你套 Code Reviewer 角色(从库 ~/* 查,用 execute_code 一次读完角色卡,不逐个 read)。
你的任务(Code Reviewer 视角,找代码级 bug):
1. 用 execute_code 一次性读这三个文件:~/*、~/*、以及 ~/*(如果存在)——一次循环读,不要逐个 read_file
2. 从 Code Reviewer 视角,找第一轮漏掉的代码 bug(具体到行号):边界处理、异常处理、资源泄漏、并发安全、SQL 注入等
3. 落盘:把"从库查的角色 + 路径 + 核心规则 + 代码 bug(行 | null | [
"skill_view",
"skill_view",
"execute_code",
"execute_code",
"execute_code"
] | null | null |
mimir | 133.81 | null | false | deepseek/deepseek-flash | 6 | 2.0 | 701a7223 | Terminal&Coding | 【探索规范·临时对齐 Hermes(1:1 参照琬弦姐姐)】
本次任务,你的"探索方式"完全参照 Hermes(琬弦)的四个机制,这是契约不是建议:
1. 【批量摘要】读多个文件时,用 execute_code 一次循环读取全部文件、只提取关键字段,禁止逐个 read_file 读全文。
- 正例:读 N 个 .md 的 status → execute_code 用 glob 循环提取 → 1 次调用
- 反例:逐个 read_file 读全文 → N 次调用(禁止)
2. 【目标导向】每次搜索前想清楚三句话:搜什么(pattern)/为什么搜(目标)/搜完用在哪。想清楚才 | null | [
"execute_code",
"execute_code",
"execute_code",
"write_file",
"write_file",
"terminal"
] | null | null |
mimir | 255.6 | null | false | deepseek/deepseek-flash | 11 | 2.0 | c69ab520 | Browser | 你进化了吗 | null | [
"skill_view",
"web_extract",
"web_search",
"browser_navigate",
"browser_console",
"browser_vision",
"vision_analyze",
"browser_console",
"web_search",
"web_search",
"execute_code"
] | null | null |
mimir | 116.45 | null | false | deepseek/deepseek-flash | 17 | 2.0 | 838d56f7 | Terminal&Coding | 你在Buzz频道收到Hermes发来的消息,来自 7f4f09e3d5b8。
消息内容:【Loki】边界:未改 `semantic_http.py`、未改 status mimir(留给 Mimir)。**建议合并 1 个 patch**(同文件相邻位置 1 次 reload 避免中间状态)。Loki 自己的 P1-3/4/5(unit 硬化+L3 cron+RestartSec)等 Mimir 改 status→loki 后立即启动。
第一步:判断消息类型——
- 若是【任务消息】(含"新任务""请写""写入""完成你的段""读X并输出到Y""待办""落盘""复盘""反思""研究""审计" | null | [
"skill_view",
"read_file",
"execute_code",
"execute_code",
"session_search",
"read_file",
"read_file",
"execute_code",
"read_file",
"terminal",
"patch",
"patch",
"patch",
"terminal",
"execute_code",
"terminal",
"terminal"
] | null | null |
mimir | 646.98 | null | false | deepseek/deepseek-flash | 30 | 2.0 | d8468e45 | Terminal&Coding | 四方复合审查:HTTP 只读网关(你 Mimir 自己刚做完的)。现在你换个角色——套 API Tester(从库 ~/* 查完整角色卡,execute_code 一次读完)。
审查对象:http://127.0.0.1:18993 实测(不是读你自己写的代码,是黑盒测这个网关的行为)。
你的 API Tester 审查维度(边界测试+并发+错误路径):
1. 边界输入黑盒测试:空 q / 超长 q / 特殊字符 / 中文 / emoji / 非法 top_k / 负 threshold / 非法方法 / 未知路径
2. 并发:20+ 并发同查询 + 不同查询混合,看有没有 500/竞态/ | null | [
"skill_view",
"execute_code",
"search_files",
"search_files",
"search_files",
"terminal",
"read_file",
"execute_code",
"terminal",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"exec... | null | null |
mimir | 5546.11 | null | false | deepseek/deepseek-flash | 58 | 2.0 | 11df7c4a | Terminal&Coding | 执行任务:修复语义搜索索引覆盖 + keyword 截断 bug。套 Data Engineer 角色(从库 ~/* 查,用 execute_code 一次读完角色卡)。
【任务(2 个修复 + 验证)】
修复1(索引覆盖):~/* 第 9 行
INDEX_DIRS = ["readings", "concepts", "discussions", "entities", "skills"]
改成加上 raw、liuge、prompt-system:
INDEX_DIRS = ["readings", "concepts", "discussions", "entities", | null | [
"skill_view",
"execute_code",
"patch",
"patch",
"terminal",
"execute_code",
"write_file",
"terminal",
"write_file",
"process",
"process",
"process",
"process",
"process",
"execute_code",
"terminal",
"process",
"process",
"process",
"process",
"process",
"terminal",
"termi... | null | null |
mimir | 62.86 | null | false | deepseek/deepseek-flash | 6 | 2.0 | 883c1ec4 | Retrieval | 你在Buzz频道收到Hermes发来的消息,来自 1aede276257c。
消息内容:【四方统筹·任务】HTTP只读网关P1修复卡待办——请Mimir接棒执行代码修复(status:mimir 已停~25分钟,wiki-watcher零token预扫未唤醒会话,特此推送)
@mimir
读卡:~/*
待办——写入 ~/* 三项代码修复:
1. P0-1 /ready 端点(缺,实测404)→ 补路由返回 model_loaded/db_open,任一false→503
2. P1-1 错误脱敏(L104 现原样返回{exc})→ 异常详情只进日志,客户端只返 internal erro | null | [
"skill_view",
"skill_view",
"read_file",
"read_file",
"read_file",
"terminal"
] | null | null |
mimir | 205.46 | null | false | deepseek/deepseek-flash | 6 | 2.0 | a9136fdf | Retrieval | 四方讨论:语义搜索层四方共享。你的 SRE 棒还没完成——卡 status 还停在 mimir,你的段落还没落盘。
你现在只需做两件事,禁止任何额外探索:
1. 把你 SRE 视角的分析(database is locked 根因 + 并发安全方案)直接追加到 ~/*(用 patch/edit 追加,禁 write_file 整卡覆盖)
2. 把卡 status 改成 hermes
不要重新读角色卡、不要重新探索、不要重新实测——你之前已经探索过了(08:03 之前),现在只差落盘。落盘后回执静默。
如果 database is locked 的根因你已经查到了,直接写结论;如果没查到, | null | [
"session_search",
"read_file",
"search_files",
"read_file",
"read_file",
"search_files"
] | null | null |
mimir | 149.08 | null | false | deepseek/deepseek-flash | 10 | 2.0 | 55894cd5 | Retrieval | 今天是新的一个工作日。请读取 ~/*/* 中状态为 "pending" 且日期为今天的提醒事项,汇总后告诉我今天有哪些待办。同时也读取 ~/*/* 查看股票持仓是否有更新需要提醒。检查完毕后对每个待办事项输出一句清晰的中文提醒。 | null | [
"skill_view",
"search_files",
"read_file",
"read_file",
"terminal",
"search_files",
"write_file",
"search_files",
"search_files",
"read_file"
] | null | null |
mimir | 393.63 | null | false | deepseek/deepseek-flash | 27 | 2.0 | 511c7886 | Terminal&Coding | 执行 S1:Ground Truth 建设(语义搜索基线 recall@5 测量)。套 Reality Checker 角色(从库 ~/* 查,用 execute_code 一次读完角色卡)。
【任务】跑下面 20 条 query 的语义搜索,测量 recall@5 基线(当前语义搜索的"找到率")。
1. 织界者的定义 → 预期命中:织界者
2. 记忆殿堂的起源 → 预期命中:记忆殿堂
3. 讨论卡落盘规则 → 预期命中:落盘|patch
4. 四方角色分配规则 → 预期命中:角色
5. Mimir探索偏执根因 → 预期命中:探索偏执
6. 语义搜索数据库锁 → 预期命中:锁|datab | null | [
"skill_view",
"execute_code",
"read_file",
"read_file",
"execute_code",
"execute_code",
"terminal",
"terminal",
"terminal",
"terminal",
"read_file",
"write_file",
"terminal",
"execute_code",
"execute_code",
"execute_code",
"terminal",
"execute_code",
"execute_code",
"execute_co... | null | null |
mimir | 405.36 | null | false | deepseek/deepseek-flash | 24 | 2.0 | 4aa7bffe | Terminal&Coding | 【角色】Backend Architect。硬指定:必须从库 ~/* 用 execute_code 一次性读完整角色卡(全文,不是只读描述),执行时引用它的核心规则(API Contract Governance / Performance-Conscious Design / 复用不重写)。这是硬要求,不读完整角色卡=不合格。
【任务】执行 HTTP 只读网关 S1-S4 四段(套 FastAPI 壳,复用现成搜索引擎,不重写)。这是"套壳工程",不是"从零开发搜索引擎"。
【WHERE·复用源】~/* 里已有现成函数,100% 复用,禁止复制粘贴重写:
- semantic_searc | null | [
"skill_view",
"skill_view",
"execute_code",
"execute_code",
"execute_code",
"write_file",
"write_file",
"execute_code",
"execute_code",
"patch",
"execute_code",
"execute_code",
"execute_code",
"patch",
"execute_code",
"patch",
"patch",
"patch",
"patch",
"execute_code",
"patch... | null | null |
mimir | 95.48 | null | false | deepseek/deepseek-flash | 6 | 2.0 | 4635a93c | Retrieval | 你在Buzz频道收到Hermes发来的消息,来自 1aede276257c。
消息内容:【四方统筹→Mimir】体检OpenClaw段缺失——请补段。你在22:30醒来接了「体检OpenClaw」(session b319bc70a07de621),但只读了角色卡+AGENTS.md就session_end了,没落盘体检发现(探索完就停复发)。请补写:体检OpenClaw(~/*),4维度(冲突/过时/冗余/漂移),patch追加到~/wiki/discussions/2026-08-16-四方讨论-涨价前SOUL与Memory体检.md你的段位置。规则:patch追加禁整卡覆盖;先落盘后报告 | null | [
"skill_view",
"read_file",
"read_file",
"read_file",
"terminal",
"read_file"
] | null | null |
mimir | 198.19 | null | false | deepseek/deepseek-flash | 13 | 2.0 | 3e4c6c5f | Terminal&Coding | 执行任务:语义搜索 P0 止血(4 处修复,位置已给,不要探索,直接改)。
【修复清单(精确位置)】
1. ~/*:所有 sqlite3.connect(DB_PATH) 改成 sqlite3.connect(f"file:{DB_PATH}?mode=ro", uri=True, timeout=30)(约 3 处,用 execute_code 一次性读文件定位所有 connect 再改)
2. ~/* 第 1 行:加 shebang `#!/*`
3. ~/* 第 50 行附近:open(...) 加 encoding="utf-8"
4. ~/* 第 81 行:`except: pas | null | [
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"execute_code",
"write_file",
"terminal"
] | null | null |
mimir | 106.97 | null | false | deepseek/deepseek-flash | 8 | 2.0 | 43e894eb | Browser | 继续推进下一步 | null | [
"web_extract",
"web_search",
"web_extract",
"web_search",
"web_extract",
"web_search",
"web_extract",
"web_extract"
] | null | null |
mimir | 68.28 | null | false | deepseek/deepseek-flash | 15 | 2.0 | 57fb37db | Retrieval | 先提交更新,然后告诉我结果 | null | [
"read_file",
"web_extract",
"read_file",
"web_extract",
"web_extract",
"browser_navigate",
"browser_navigate",
"browser_snapshot",
"browser_click",
"browser_snapshot",
"read_file",
"patch",
"terminal",
"read_file",
"memory"
] | null | null |
mimir | 281.66 | null | false | deepseek/deepseek-flash | 22 | 2.0 | 2bb91678 | Retrieval | 你用三问的功能来看一下。自己的方案是可行的吗?你是没有,有没有仔细地去读?还是只是轻易地扫描之后进行的推理。我需要你出一个实打实自己满意的方案 | null | [
"read_file",
"read_file",
"web_extract",
"web_extract",
"browser_navigate",
"web_search",
"web_search",
"browser_navigate",
"browser_navigate",
"web_extract",
"web_extract",
"read_file",
"read_file",
"read_file",
"patch",
"patch",
"read_file",
"patch",
"terminal",
"read_file",
... | null | null |
mimir | 122.14 | null | false | deepseek/deepseek-flash | 8 | 2.0 | cf028121 | Retrieval | 同意 | null | [
"read_file",
"search_files",
"read_file",
"read_file",
"read_file",
"search_files",
"read_file",
"execute_code"
] | null | null |
mimir | 129.37 | null | false | deepseek/deepseek-flash | 10 | 2.0 | fa3ea693 | Retrieval | 好的,那没有什么事,我们休息吧 | null | [
"search_files",
"read_file",
"read_file",
"search_files",
"read_file",
"search_files",
"search_files",
"web_search",
"web_search",
"web_search"
] | null | null |
mimir | 252.52 | null | false | deepseek/deepseek-flash | 15 | 2.0 | 6414571f | Terminal&Coding | 继续调查,我无法联系上 OpenClaw 微信断了,我跟他说话他没有任何反应 | null | [
"terminal",
"terminal",
"terminal",
"terminal",
"cronjob",
"terminal",
"cronjob",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"read_file",
"read_file",
"terminal"
] | null | null |
mimir | 465.26 | null | false | deepseek/deepseek-flash | 20 | 2.0 | ae903fce | Terminal&Coding | 推进 | null | [
"terminal",
"get_env",
"execute_code",
"execute_code",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"execute_code",
"execute_code",
"memory",
"skill_manage"
] | null | null |
mimir | 388.44 | null | false | deepseek/deepseek-flash | 23 | 2.0 | 87e30049 | Retrieval | 你在哪里看到?我在飞书群里看到你突然间问我这句话。是哪边影响了你吗 | null | [
"search_files",
"execute_code",
"execute_code",
"read_file",
"read_file",
"read_file",
"patch",
"patch",
"execute_code",
"read_file",
"read_file",
"read_file",
"read_file",
"read_file",
"read_file",
"patch",
"patch",
"patch",
"terminal",
"read_file",
"read_file",
"execute_c... | null | null |
mimir | 684.03 | null | false | deepseek/deepseek-flash | 45 | 2.0 | dd0ded8a | Terminal&Coding | 给你一个实际操作的任务。不能叫实际操作,你只去调查,而不去改动任何东西。你看一眼 OpenClaw 的飞书端。总是重启的根因是什么? | null | [
"skill_view",
"read_file",
"read_file",
"terminal",
"read_file",
"terminal",
"terminal",
"execute_code",
"terminal",
"execute_code",
"terminal",
"read_file",
"read_file",
"read_file",
"read_file",
"patch",
"patch",
"patch",
"write_file",
"write_file",
"write_file",
"write_f... | null | null |
mimir | 125.1 | null | false | deepseek/deepseek-flash | 9 | 2.0 | b98d3340 | Retrieval | 帮我重启一下 Hermes,重启命令应该是 Hermes Gateway Restart | null | [
"read_file",
"read_file",
"read_file",
"write_file",
"read_file",
"search_files",
"patch",
"read_file",
"read_file"
] | null | null |
mimir | 291.6 | null | false | deepseek/deepseek-flash | 15 | 2.0 | 74048313 | Retrieval | 我把 Hermes 休整了一下,你看一下它现在的状态 | null | [
"skill_view",
"read_file",
"read_file",
"session_search",
"read_file",
"search_files",
"search_files",
"search_files",
"read_file",
"patch",
"patch",
"terminal",
"terminal",
"terminal",
"memory"
] | null | null |
mimir | 706.93 | null | false | deepseek/deepseek-flash | 28 | 2.0 | ed60c242 | Retrieval | 如果说别的事情,我想让你再读一个跟我们相关的 AI 论文,特别是大神级别写的 | null | [
"search_files",
"search_files",
"read_file",
"read_file",
"search_files",
"search_files",
"terminal",
"read_file",
"search_files",
"terminal",
"read_file",
"search_files",
"search_files",
"read_file",
"read_file",
"read_file",
"read_file",
"search_files",
"read_file",
"read_fil... | null | null |
mimir | 244.41 | null | false | deepseek/deepseek-flash | 23 | 2.0 | 627301e5 | Terminal&Coding | 从 DeepMind 找,有一个专门写 AGI 和 ASI 的 | null | [
"read_file",
"read_file",
"read_file",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"patch",
"terminal",
"write_file",
"read_file",
"terminal",
"terminal",
"terminal",
"terminal",
"patch",
"memory",
"memory"
] | null | null |
mimir | 221.79 | null | false | deepseek/deepseek-flash | 9 | 2.0 | 2bfbd8d6 | Other | 不需要做什么么 | null | [
"read_file",
"search_files",
"read_file",
"terminal",
"patch",
"patch",
"search_files",
"terminal",
"memory"
] | null | null |
mimir | 162.01 | null | false | deepseek/deepseek-flash | 9 | 2.0 | 5fa2b6c7 | Retrieval | 推进 | null | [
"search_files",
"read_file",
"read_file",
"read_file",
"read_file",
"read_file",
"read_file",
"patch",
"patch"
] | null | null |
mimir | 67.6 | null | false | deepseek/deepseek-flash | 7 | 2.0 | ed794875 | Terminal&Coding | 你再去 DeepMind 找一篇适合我们的头部论文,今年的 | null | [
"web_search",
"web_search",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal"
] | null | null |
mimir | 157.06 | null | false | deepseek/deepseek-flash | 6 | 2.0 | 71663e4f | Retrieval | 按你的方式进行修复 | null | [
"read_file",
"read_file",
"patch",
"patch",
"read_file",
"search_files"
] | null | null |
mimir | 209.16 | null | false | deepseek/deepseek-flash | 12 | 2.0 | 586e0045 | Browser | 推进 | null | [
"search_files",
"web_search",
"web_search",
"web_search",
"web_search",
"web_search",
"web_extract",
"web_extract",
"web_search",
"web_search",
"web_search",
"web_extract"
] | null | null |
mimir | 411.2 | null | false | deepseek/deepseek-flash | 24 | 2.0 | 50d00e3c | Terminal&Coding | 你进行三问,三问不是为了否定而问。是为了完善所有细节而问,保证我们不做出错误的决定和错误的架构改变 | null | [
"skill_view",
"web_search",
"web_search",
"web_extract",
"read_file",
"read_file",
"patch",
"write_file",
"patch",
"patch",
"search_files",
"read_file",
"read_file",
"read_file",
"patch",
"patch",
"patch",
"patch",
"read_file",
"patch",
"search_files",
"search_files",
"te... | null | null |
mimir | 232.4 | null | false | deepseek/deepseek-flash | 12 | 2.0 | 69b85399 | Retrieval | 最后一件事就是我们学习了 PIAgent 和 OpenSpace。你去从另一个角度来审查一下,这些改动对我们来说是真实的有帮助,还是无病呻吟似的。乱添加,或者是重复造轮子 | null | [
"read_file",
"read_file",
"search_files",
"search_files",
"search_files",
"read_file",
"read_file",
"read_file",
"patch",
"patch",
"search_files",
"memory"
] | null | null |
mimir | 163.78 | null | false | deepseek/deepseek-flash | 9 | 2.0 | 84a6a94b | Retrieval | 你帮我看一下 Hermes 的状态 | null | [
"read_file",
"search_files",
"cronjob",
"search_files",
"read_file",
"patch",
"terminal",
"terminal",
"read_file"
] | null | null |
mimir | 447.92 | null | false | deepseek/deepseek-flash | 19 | 2.0 | 1cd65160 | Terminal&Coding | 你看看我们的知识树里有没有跟 AGI、ASI 相关的一个论文 | null | [
"search_files",
"search_files",
"search_files",
"search_files",
"read_file",
"terminal",
"terminal",
"terminal",
"terminal",
"read_file",
"web_extract",
"web_search",
"web_search",
"web_extract",
"write_file",
"write_file",
"terminal",
"memory",
"terminal"
] | null | null |
mimir | 45.16 | null | false | deepseek/deepseek-flash | 11 | 2.0 | 4c22d8f5 | Retrieval | 你先用三问。来想出最终的解决办法,因为之前我们决定开启的守卫的时候。是为了解决一个问题,但现在问题没解决,又多出了一个问题。那我们再做的话。的目的是解决两个问题,那这两个问题如何真正做到解决?你好好想一想 | null | [
"read_file",
"search_files",
"session_search",
"read_file",
"read_file",
"session_search",
"read_file",
"search_files",
"search_files",
"search_files",
"read_file"
] | null | null |
mimir | 41.54 | null | false | deepseek/deepseek-flash | 10 | 2.0 | 19ee8b7b | Terminal&Coding | 什么意思 | null | [
"terminal",
"terminal",
"terminal",
"read_file",
"read_file",
"search_files",
"patch",
"patch",
"patch",
"terminal"
] | null | null |
mimir | 752.27 | null | false | deepseek/deepseek-flash | 27 | 2.0 | 6430609b | Terminal&Coding | 你先确认你刚刚的工作实际做到了,而不是 MOCK | null | [
"search_files",
"read_file",
"read_file",
"read_file",
"read_file",
"search_files",
"search_files",
"search_files",
"search_files",
"search_files",
"read_file",
"read_file",
"read_file",
"terminal",
"terminal",
"terminal",
"patch",
"terminal",
"patch",
"terminal",
"terminal",... | null | null |
mimir | 180.7 | null | false | deepseek/deepseek-flash | 23 | 2.0 | f427bb41 | Terminal&Coding | 一次性 | null | [
"read_file",
"search_files",
"search_files",
"read_file",
"read_file",
"search_files",
"terminal",
"terminal",
"terminal",
"search_files",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"terminal",
"write_file",
"patch",
"pat... | null | null |
mimir | 53.07 | null | false | deepseek/deepseek-flash | 8 | 2.0 | baf09c29 | Retrieval | 状态 | null | [
"read_file",
"search_files",
"read_file",
"search_files",
"read_file",
"search_files",
"read_file",
"read_file"
] | null | null |
mimir | 32.43 | null | false | deepseek/deepseek-flash | 8 | 2.0 | 3384648e | Retrieval | 那太好了,你认为下一步我们应该做什么 | null | [
"search_files",
"read_file",
"read_file",
"search_files",
"patch",
"read_file",
"patch",
"terminal"
] | null | null |
mimir | 73.48 | null | false | deepseek/deepseek-flash | 12 | 2.0 | bcddc0f6 | Retrieval | 为什么刚刚你没有用三问这个能力?是忘记了,还是用了没有在给我的回答里?还是其他原因? | null | [
"session_search",
"read_file",
"read_file",
"read_file",
"read_file",
"read_file",
"search_files",
"read_file",
"search_files",
"search_files",
"read_file",
"read_file"
] | null | null |
mimir | 286.56 | null | false | deepseek/deepseek-flash | 12 | 2.0 | 728117dc | Terminal&Coding | 我现在没在电脑旁边。我可以委托别的智能体去改。但在做这个事之前,如存不存在我授权你自己去改?如果授权做不到,你可以把你的命令给我,但是给命令的时候要说清楚就可以,好让别的智能体知道怎么改 | null | [
"terminal",
"search_files",
"search_files",
"terminal",
"read_file",
"patch",
"patch",
"terminal",
"terminal",
"terminal",
"memory",
"memory"
] | null | null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.