oleksiibond

4 ms·

1.
by oleksiibond 3mo ago
Repo for anyone who wants to look under the hood: https://github.com/oleksiijko/pmb
2.
by oleksiibond 3mo ago
Proper Framing - AGENTS.md is fixed and always contextual irrespective of its relevance; memory is the exact opposite of it. PMB does not dump the store in, rather extracts only a small top-k relevant chunk per task (a few hundred tokens ge
3.
by oleksiibond 3mo ago
It is a legitimate worry, but I would make it two separate questions since bloating and poisoning have their own solutions. Bloating: PMB does not inject anything into the store, just gets a small top-k relevant snippet for every task - nor
4.
by oleksiibond 3mo ago
Agreed, and point number two is the tricky one. Creating a list of tasks is easy; evaluating them is not. You need a consistent task set, a "clean slate" control (i.e., Claude code without memory is your proper control) and an eva
5.
Show HN: PMB – local memory for coding agents that shows if it is used(pmbai.dev)
26 points by oleksiibond 3mo ago|9 comments
6.
by oleksiibond 3mo ago
Fair enough, you are correct that both can be self-hosted, and thus "local" by itself is not the moat. And I do not want to make claims about being able to beat them in recall, since I have no benchmark to compare against, and I b
7.
by oleksiibond 3mo ago
But if what you need is a hosted, managed memory API, which you can plug into your own app, both Mem0 and Zep have great offerings and are more developed along those lines: - Not local but hosted, meaning the memory will be stored remotely
8.
by oleksiibond 3mo ago
Loops - Two. Write: while working, PMB stores facts, decision, and learnings on MCP (automatically using hooks). Everything is saved to SQLite, gets embedded, and the entities get linked to a graph. Read: before answering the prompt, a hook
9.
Show HN: PMB – local-first memory for AI coding agents over MCP(github.com)
7 points by oleksiibond 3mo ago|6 comments