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

# memanto use

> Switch where Memanto keeps memories: Memanto Cloud, or Memanto local with Moorcheh Cloud or on-prem.

# memanto use

Switch where Memanto keeps memories. Tools you connected with `memanto connect` follow automatically; there is nothing to reconnect.

```bash theme={null}
memanto use TARGET
```

**Arguments:**

* `TARGET` - One of:

| Target | Backend | Shown as |
| - | - | - |
| `cloud` | [Memanto Cloud](https://docs.memanto.ai/cloud/overview.md) | `memanto-cloud` |
| `moorcheh` | Memanto local with Moorcheh Cloud (Moorcheh API key) | `moorcheh-cloud` |
| `on-prem` (alias `local`) | Memanto local with Moorcheh on-prem (Docker) | `moorcheh-on-prem` |

The names in the last column work as targets too.

**Examples:**

```bash theme={null}
memanto use cloud
memanto use moorcheh
memanto use on-prem
```

**Output:**

```
Switched backend to moorcheh-on-prem.
Active session was cleared.
```

**Notes:**

* A backend that was never set up runs its setup first: `cloud` signs you in ([`memanto login`](https://docs.memanto.ai/cli/auth/login)), `moorcheh` asks for a Moorcheh API key, `on-prem` runs the [on-prem setup](https://docs.memanto.ai/on-prem/quickstart.md).
* Switching never moves or deletes memories. Each backend keeps its own agents. To copy local memories to Memanto Cloud, run [`memanto migrate to-cloud`](https://docs.memanto.ai/cli/migrate/migrate#move-to-memanto-cloud).
* The active agent is always cleared, because agents and sessions belong to one backend.
* Switching to the backend that is already active does nothing.
* `memanto use` replaces `memanto config backend`, which was removed.
* See [Backend Switching](https://docs.memanto.ai/on-prem/backend-switching.md) for what is kept on each side.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.