Skip to main content

​
memanto connect update

Bring every active Memanto integration — local and global — up to the latest agent-instruction template.
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:
Update using a different project directory as the local scope:
Output (example):

​
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:
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:
An update rewrites the managed section only. Your own instructions elsewhere in the file, and the dynamic memories block written by memanto memory 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:
Notes:
  • Upgrading the memanto package does not rewrite already-installed instruction files. Run this command after upgrading.
  • Run memanto connect list to see which targets are installed in each scope.