We became increasingly frustrated with having to re-explain our tasks, workflows, common mistake patterns, etc. anytime we switched agents. We found no good free alternatives out there, so we built our own and fully open-sourced it!
Beacon hooks into 20+ different agent harnesses, captures session telemetry (prompts, tool calls, command executions, etc) in one normalized format, and distills it into common patterns and repeatable workflows with a human-approval step. This compounded knowledge is then accessible to any future agent via skills / MCP.
We believe your agent data is yours to own and should not be locked behind any frontier lab's ecosystem or closed memory infrastructure. We built Beacon to make working across agents way more transparent and efficient.
Try it out and tell us what you think: https://github.com/Asymptote-Labs/agent-beacon
The projects need to remember things, not the agents.
When they're a blank slate coming in, I get more reliable outputs.
I just have one orchestrator/secretary/router with long-term memory, but I don't switch its harness.
Here's a link to our product page, if it's helpful: https://beacon.sh
Beacon keeps the full execution trace (prompts, reasoning, tool calls, commands) outside the agent's context and distills lessons from it. Ultimately the agent still only has access to snippets of information (via skill progressive disclousure) but it's drawn from much richer session data rather than what you remembered to note down. Also you don't have to maintain it yourself!
I don't even know how obsidian works.
And I use a harness where the agents can easily look up & search other sessions, or past sessions.
I am the founder of Substrate, a tool that allows you to see all of the memory and also delete a specific entry. Is your agent allowed to write its own workarounds in your setup?