XMemo Memory for Cindy

Durable context for Cindy.
Local-first memory, cloud continuity, and safe recovery after an interruption.

About XMemo · Install · Use · Privacy · Marketplace

XMemo Memory gives Cindy durable project context that remains useful without a network connection. It saves context to Cindy's private local storage first and, when enabled, synchronizes it to XMemo for continuity across sessions and devices.

Status: v1.0.0 candidate, tested locally in Cindy. Official marketplace availability is pending maintainer review.

About XMemo

XMemo is a user-owned, identity-aware memory layer for AI agents. It lets you keep durable context under your control instead of leaving it isolated in a single chat or tool. Your XMemo account can carry context between supported AI clients, while retaining export and deletion controls.

XMemo Memory brings that continuity to Cindy without making the cloud a single point of failure:

XMemo provides	This Cindy plugin adds
Durable, cross-client context	A private local-first copy for offline work and interruption recovery.
Identity-aware memory history	Cindy-specific project state, milestones, TODOs, decisions, and checkpoints.
User-controlled export and deletion	Explicit, safe memory deletion and controlled synchronization.
A single memory layer for multiple agents	A focused Cindy experience: ask naturally, then resume with relevant context.

Learn more at xmemo.dev or manage your account and API keys at xmemo.dev/me.

Why use it

You need	XMemo Memory does
Work through a network interruption	Keeps a private local copy and queues only safe cloud writes.
Resume where you stopped	Saves active state and a restart checkpoint before an interruption.
Continue on another device	Synchronizes durable context to your authorized XMemo account.
Keep work entirely local	Runs in local-only mode without OAuth or an API key.
Avoid duplicate remote changes	Holds uncertain non-idempotent operations until you explicitly approve replay.

Install

Until the official listing is available, install a local .cindy package:

1. Obtain xmemo-memory-1.0.0.cindy.
2. In Cindy, open Plugins, then drag in the package or select it from disk.
3. Review the requested tool, network, session-context, and private-file permissions.
4. Enable XMemo Memory and open its settings.

Choose one of these modes:

Mode	Local memory	XMemo cloud	Best for
Hybrid (default)	Yes	When available	Everyday work with offline resilience.
Local-only	Yes	Never contacted	Private work with no cloud connection.
Cloud-only	No	Required	Workflows that deliberately require cloud memory.

For cloud synchronization, choose an authentication method in the plugin settings:

• XMemo account (recommended): Cindy completes OAuth in your browser and keeps access and refresh tokens in its encrypted vault.
• API key (compatibility): existing users can save an XMemo API key with memory:read and memory:write scopes in Cindy's encrypted vault.

The plugin never reads credential values. Cindy injects only the selected credential at the final network boundary, and only for its corresponding XMemo host.

Use XMemo Memory

Ask Cindy to use $xmemo when you want it to:

• remember a decision, preference, fact, or handoff;
• recall relevant context before continuing work;
• track project state, milestones, TODOs, and decisions;
• save progress before a restart or interruption;
• restore the latest compatible checkpoint;
• inspect or safely synchronize queued work.

How it works

flowchart LR
  C["Cindy conversation"] --> W["Local-first write"]
  W --> L["Private Cindy storage"]
  W -->|"Hybrid mode"| Q["Safe sync outbox"]
  Q --> X["XMemo cloud"]
  C --> R["Recall context"]
  R --> L
  R --> X
  X -. "offline or unavailable" .-> F["Marked local or cached fallback"]
  L --> F

Safe recovery and deletion

Progress snapshots are written locally before cloud synchronization, so Cindy can resume from a compatible checkpoint while offline. Safe, idempotent writes may be synchronized later; uncertain operations that could create duplicates are held until you explicitly approve replay.

Forgetting a memory requires its exact ID. The default is a recoverable soft deletion. Permanent deletion requires an explicit hard-delete mode and a second confirmation, and uncertain network outcomes never claim that a deletion succeeded.

Privacy and safety

• Credentials stay in Cindy's encrypted vault. Plugin code never receives OAuth tokens or API-key values.
• Local memory is private but not encrypted by this plugin. Protect the device and do not store secrets in memory content.
• Obvious credentials are redacted before memory and timeline writes. This is a safeguard, not a substitute for keeping secrets out of prompts.
• Cloud synchronization is optional. local-only mode makes no XMemo cloud request.
• Uninstalling removes local plugin data. Synchronize or export anything you need before uninstalling.

Official Cindy marketplace

The marketplace proposal is under review in makecindy/cindy-official-plugins#84.

Marketplace publication follows Cindy's official process: maintainer acknowledgement of the proposal, a focused DCO-signed pull request to the official plugins repository, then automatic packaging and publication after merge. This repository does not publish to the Cindy marketplace through tags or GitHub Releases.

Contributing

Issues and pull requests are welcome. Keep changes focused, test the relevant behaviour, and explain any change to the safety contract. New marketplace plugins must follow the official proposal and review process above.

License

MIT © 2026 Yonro