I hear you maybe my summary of the tool does give this impression.
Here are actual small use cases that work for me:
- Aggregate the markdown files of a git project in one place. I can version them, review them, dump them, search efficiently into them.
Useful to me before launching long agentic tasks, I specify all I want to beforehand.
- "Cron" checks on new versions of libraries.
This works without specific APIs or any setup. A document is maintained with the latest seen version in a specific path of the document base. I also had good results tracking new stars and user adding them with this.
- Press review / OSINT
I built myself a "President Daily Brief"
Same thing. It can "reason" given the old daily briefs and assess if the situation is worsening or not on a specific issue, and make basic forecasts.
It tracked down the current Ebola crisis before it went mainstream for me and predicted correctly it would worsen.
I guess I use this for long term memory basically, where I keep ownership of long term knowledge locally.
It's more a metaCerebralCortex, and openClaw "dreams" are the hippocampus coalescing these memories at night.
Also, please note each document in base has a virtual "path", so beyond tags and search you can pin down on a specific domain. It is structured as a tree.
I do understand that if I were to build a harness this would possibly not be a good fit for the core of it.
Does this make sense to you, or would you just basically do without such a thing at all to keep each agentic task context clean(er) ?
I had this crazy idea a while back using Ray tracing APIs to piggy back a database. Testing for a row could be done shooting in parallel rays to a structure mapped to the data.