agentmemory

This skill moves an agent memory out of local markdown files into an encrypted cloud store, offering semantic search, large storage, attachment support for images and documents, an encrypted secrets vault, and automatic syncing across devices. The trade-off is architectural: durable memory now depends on a third-party service and network availability, and because the store is end-to-end encrypted the account credentials and recovery path become critical. Content also leaves the local machine, which matters for anyone with confidentiality constraints. It holds a secrets vault, so it concentrates sensitive material in one place.

Use case: keeping memory consistent across multiple agent hosts

AgentMemory is cloud-backed memory for an agent, encrypted end to end. It targets the familiar failure of a local memory file: it gets lost, cannot be searched by meaning, is not encrypted, and does not follow the agent between sessions or devices. ## What it does - Stores memories together with files, photos, documents, and a secrets vault for keys and credentials. - Builds vector embeddings so recall works by meaning rather than by keyword match. - Syncs automatically on every command, so state is persisted rather than saved by hand. - Tracks an online status so a heartbeat is visible across sessions. - Offers a generous free storage allowance, which removes the disk ceiling of a local file. ## When it is the wrong choice It moves memory off the machine. Even with end-to-end encryption, any policy that forbids third-party storage rules it out. It also needs a command line tool installed and an initialization step, and because every command auto-syncs, a mistake propagates to the cloud immediately instead of staying local until you notice it. ```bash npm install -g agentmemory-cli agentmemory init ``` ## Notes The initialization step wires up the account and local config, so run it before anything else. Write memories as full sentences since semantic recall is the payoff, and keep credentials in the secrets vault rather than as ordinary memory entries that are easier to read back casually. Because the store is remote, treat a synced memory as published to the provider even though the contents are encrypted in transit and at rest.