opwizardx
Joined 1 year ago
Karma
39
Submissions
49
Member since
Sep 13
Recent submissions
Comment · 1 month ago
I did similar tests on my own corpus when was considering whether to keep semantic search in default path for pond.
On 3 months of my own sessions I’ve seen that BM25 search was finding the correct answer in ~61%, where semantic had shown only ~37% of success.
After that it was easy for me to make the decision.
Got all info on how I did evals in here, if interested: https://github.com/tenequm/pond/tree/main/docs/researches/26...
Comment · 1 month ago
Why do you need an MCP server at all when the spec itself is so simple?
Comment · 1 month ago
plain text + fts covers all the basic needs, adding vector search, in my experience, adds more hassle and failures then helps
Comment · 1 month ago
I had been building https://github.com/tenequm/pond for this exact purpose for a while, and it works like a charm in my case.
Give it a try, hope it will help you to solve your need without injecting anything in your context all the time.
Comment · 2 months ago
That is exactly what I'm building pond for myself: one store for all my sessions, Codex and Claude Code both and a bunch of others including OpenClaw, and my agents can access it over MCP. It also happens really often that when my agents cannot find something, they just call pond search themselves. Faster that way. Whenever I need a session from a while ago now, I just know it's in pond. Repo, if you'd be willing to give it a try: github.com/tenequm/pond
Comment · 2 months ago
Same worry got me to build pond for myself: it imports all of my sessions on a cron schedule every 5 mins into one store, and my agents can access it over MCP. Whenever I need a session from a while ago now, I just know it's in pond, because all of my sessions for about the last 1.5 years are collected in there. It also happens really often that when my agents cannot find something, they just call pond search themselves. Faster that way.
Codex, Pi, Hermes, Openclaw and bunch of others a getting pulled in automatically too. Repo: https://github.com/tenequm/pond
Comment · 2 months ago
Like we used to have all of that time before with docker-compose.yaml.
It would have been so neat to have agents.yaml in your repo and know it will be sourced by a harness you use.
Author of pond, an open-source archive and search for AI agent sessions: github.com/tenequm/pond
github.com/tenequm x.com/opwizardx [email protected]