> ## Documentation Index
> Fetch the complete documentation index at: https://docs.praxa.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Memory CLI setup

> Generate dry-run federation setup plans without connecting a provider or starting synchronization.

These local-only planning commands are published in `@praxa/cli@0.3.0`. The explicit `praxa` bin
is required because the package preserves both the current `praxa` and legacy `aura` binaries.

## Preview a source entry

```bash theme={null}
npx --package=@praxa/cli@0.3.0 praxa memory source add mem0 --mode federated --dry-run
```

Supported provider IDs are `mem0`, `zep`, `graphiti`, `langgraph`, `letta`, and `openai_agents`.
Use `--project-dir DIR` to inspect a different existing project directory.

The dry run returns local source metadata: source ID, provider, `federated` mode, read-only access,
and enabled state. It does not accept or store a provider credential, plan an endpoint or secret
reference, call the provider, connect an account, or write a memory.

## Preview a synchronization plan

```bash theme={null}
npx --package=@praxa/cli@0.3.0 praxa memory sync plan --dry-run
```

This inspects whether a proposed federation configuration is structurally complete. It does not
start a job. There is no `sync run`, mirror, import, or cutover command because Praxa has not shipped
the credential vault, durable scheduler, authenticated management qualification, or transition
receipts those commands would require.

<Note>
  Keep provider credentials in your server-side vault. Generated files must contain references,
  never secret values.
</Note>