[Upstream #159] 太消耗zep了，为啥不考虑自建库呢？

[ivanzud]

Upstream Issue Mirror

• Upstream issue: 太消耗zep了，为啥不考虑自建库呢？ 666ghj/MiroFish#159
• Upstream repository: 666ghj/MiroFish
• State: open
• Author: codetsang
• Labels: enhancement
• Last updated: 2026-03-12T03:30:23Z

Summary

zep的额度太低了，要真正进行分析，需要大量的Episode。能否考虑基于其他开源方案，重写zep部分？

Local Coverage

• Status: tracked
• Summary: Tracked under beads issue mirofish-zx6p: another upstream request for a self-hosted or non-Zep graph backend is preserved locally, but implementing it safely still requires the broader graph-backend abstraction work already tracked under mirofish-8eg instead of wiring an ad hoc replacement into the current graph/simulation pipeline.
• Local refs: .beads/issues.jsonl, docs/upstream-triage.md, https://github.com/ivanzud/MiroFish/issues/97
• Notes: Mirrored into fork issue [Upstream #159] 太消耗zep了，为啥不考虑自建库呢？ #97 on March 12, 2026. This request overlaps the existing non-Zep backend and self-hosted graph follow-ups from upstream issues [Upstream #63] 卡在Debugger PIN: 137-310-617，无法往下走了，是为甚麽 #55, [Upstream #27] Zep的免费计划总是报错：Rate Limit Exceeded #76, 能否采用除了zep的别的知识图谱 666ghj/MiroFish#106, and 能不能不要画zep图？我只要推演和角色互动 666ghj/MiroFish#156.

Recent Upstream Comments

• chrischeng192 at 2026-03-12T03:30:23Z: 你暂时可以看看这里