The v0.0.2 release of Knowledge-and-Memory-Management is exactly what a clean release should look like: no leftover personal paths, no hardcoded /home/you/ dangling in the config, and a clear split between knowledge collection and memory management. If you've been following the 0.0.x line, this is the release where the tool finally becomes portable across machines and agents. Here's what changed and why it matters.
$AGENT_HOME: The Portability Fix
The most visible change in v0.0.2 is the replacement of all absolute personal paths with the $AGENT_HOME environment variable. Previously, the agent’s knowledge store was tied to a specific filesystem layout — a dealbreaker if you're running agents in containers, across multiple users, or on ephemeral CI runners.
Now, every collection, memory index, and metadata file resolves against $AGENT_HOME. If the variable is unset, the agent falls back to a sensible default (typically ~/.agent), but the contract is explicit: set AGENT_HOME once, and the entire knowledge pyramid moves with it.
Here's the core path-resolution logic that now underpins everything:
