sovseal-sdk’s store/recall as two CrewAI-native @tool-decorated functions, shared across every agent in your crew. Because store/recall talk to the local ONEBRAIN engine over framed IPC on your own machine, all memory calls complete at 0 network round-trip — recall adds no measurable latency to your task pipeline.
Installation
Crew setup with shared memory tools
The example below creates a two-agent crew — a researcher and a writer — that share memory tools backed by a singleAgentStateClient. The researcher stores architecture constraints it discovers; the writer recalls them before drafting output, ensuring consistency across the entire crew run.
crew.py
How memory flows between agents
Because both agents share the same
memory_tools list and the same AgentStateClient (backed by the same on-device native host), a fact stored by the researcher is immediately available to the writer in the same crew run — or in any future run on the same machine.
0 RTT local recall: all memory reads and writes go to the on-device LanceDB store at
~/.sovseal/db/memories.lance over local IPC — there is no network hop, so recall latency stays under 10 ms even for large memory stores. Requires the native host launcher at ~/.sovseal/native-host/run.sh (run npx -y @sovseal/mcp-server once to provision it — see SDK Reference: Overview).