> ## 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 connect update

> Refresh installed Memanto agent instructions to the latest template version.

# memanto connect update

Bring every active Memanto integration — local and global — up to the latest agent-instruction template.

```bash theme={null}
memanto connect update [OPTIONS]
```

Memanto stamps each instruction file and `SKILL.md` it writes with a template version. When a newer Memanto release ships improved instructions, previously connected agents keep running the older text until you update them.

**Options:**

* `-p, --project-dir TEXT` - Project directory to scan for local integrations (default: `.`)

There is no target argument and no `--global` flag: one run updates every active integration it finds, in both the project and the user-global scope.

**Examples:**

Update everything connected to the current project and to your user account:

```bash theme={null}
memanto connect update
```

Update using a different project directory as the local scope:

```bash theme={null}
memanto connect update --project-dir ./my-project
```

**Output (example):**

```
Updated MEMANTO section in CLAUDE.md
Deployed skill to .claude/skills/memanto-memory/SKILL.md
Installed Memanto hooks and scripts
Added permissions

🎉 Successfully updated all active agent instructions to v1.0.0!
```

## How Memanto decides what to update

An integration counts as **active** when its instruction file or its `memanto-memory` `SKILL.md` carries a version marker:

```html theme={null}
<!-- memanto-template-version: 1.0.0 -->
```

Every active integration is reinstalled through the normal `memanto connect` path, so the update also refreshes skills, hooks, and permissions — not just the instruction text.

If nothing is connected, the command reports `No active Memanto integrations found to update.` and changes nothing.

## What is preserved

Memanto only owns the region between its sentinels:

```html theme={null}
<!-- MEMANTO-MANAGED-SECTION -->
...Memanto instructions...
<!-- /MEMANTO-MANAGED-SECTION -->

<!-- MEMANTO-DYNAMIC-MEMORIES -->
...memories injected by `memanto memory sync`...
<!-- /MEMANTO-DYNAMIC-MEMORIES -->
```

An update rewrites the managed section only. Your own instructions elsewhere in the file, and the dynamic memories block written by [`memanto memory sync`](/cli/data/sync), are left untouched.

## How you find out an update is available

Memanto compares the **lowest** version found across all active files against the version bundled with your installed release, and surfaces a notice in two places:

* [`memanto status`](/cli/core/status) prints an **Agent Instruction Status** section.
* [`memanto memory sync`](/cli/data/sync) prints a one-line notice after syncing.

```
⚠️ Notice: Your Memanto agent instructions are out of date (v0.0.0 installed, v1.0.0 available).
   Run `memanto connect update` to apply the latest instruction hardening.
```

**Notes:**

* Upgrading the `memanto` package does not rewrite already-installed instruction files. Run this command after upgrading.
* Run [`memanto connect list`](/cli/connect/list) to see which targets are installed in each scope.