@HermesWatcher Every turn:
1. Jev decides if this turn needs memory at all ("ok, go ahead" doesn't)
2. Query = this message + the previous turn, so short replies still find context
3. Low-score hits are dropped
4. Jev drops any hit that adds nothing new to the chat
Open-sourcing it soon 👀
@HermesWatcher Self-hosted Hindsight + Obsidian + built-in MEMORY.md, with a reworked Hindsight recall path.
On a day of real chats:
- turns that get memory: 2% → 65%
- irrelevant memories per turn: 5.6 → 0.4
- relevant share: 40% → 75%
- recall latency: 8s+ timeouts → ~4s
How 🧵
Built on @MulticaAI: coding agents take issues, report blockers, and update status.
oh-my-multica adds the delivery loop: agents plan a DAG; deterministic control tracks dependencies, evidence, review, merge, final acceptance.
#CodingAgents#AIAgents
https://t.co/0RmnSoGItW
MUST NOT catches AI slop: do NOT add unnecessary logging, do NOT refactor unrelated code, do NOT change variable names for "clarity", do NOT create new abstractions unless requested. These prohibitions stop destructive over-delivery.
Open-sourced: Agent Operating Model Kit.
Run agents like a micro AI company:
- token is budget
- optimize value per spend
- no output = not finished
- no verification = not complete
- compound through reusable assets
https://t.co/1r8cK2GdCz