Use cases
Four things the engine was asked to do
Each page is a snippet that was executed against the published package, plus the limit that snippet runs into. No framework is required. The adapters are on the integrations pages. Three of them were re-run from main. Docker and Node were not executed.
On this page
- An agent that remembers a project decision
A coding agent’s useful memory is a decision made while working, stored when it happens, and still there after the process is gone. This is that, with no transcript mining afterwards.
- A ledger line outranks a line from chat
An agent hears that the balance is forty dollars and reads a ledger file that says forty-two ten. Both can be memories. Only one carries a source. On a real brain, activate() returned the sourced one first.
- A long run that can be killed
The contract this site will stand behind is small. checkpoint() returns, then a new process opens the same directory and the memory is there. A flush that does not checkpoint was tried. The new process did not see it.
- An agent with no server and no embedder
connect_embedded opens a directory and runs the engine in the process. Nothing is listening on a port. With no vector passed in, a cue has to share tokens with what was stored. That is the whole offline behaviour, and it was printed.
The three calls
experience() writes. activate() recalls from a cue. checkpoint() is what a second process was able to read. A flush of working memory, without checkpoint(), was not visible to a new process in the same test.