AgentLayer▸docs
Run it

Updating

Pull a new plugin version, then reconcile your home with the upgrade skill.

Updating is two steps because the plugin and your home are two different things. A plugin update replaces plugin code. Your home (AGENTS.md, SOUL.md, settings, rules) was copied out of templates once at init and has been yours to edit since. A code update cannot safely overwrite it, so the home is reconciled separately, on your terms.

Coming from agent-kevin?

Going from agent-kevin to agentlayer 1.0 is a move, not an update. /agent-kevin:move copies your home to a new folder, and 1.0's upgrade finishes the move there. Your old home stays as it was. See Moving from agent-kevin.

Pull the new version

Plugin updates are not automatic for third-party marketplaces. Inside a session:

/plugin marketplace update agentlayer     # refresh the catalog
/plugin update agentlayer@agentlayer      # pull the new version
/reload-plugins                           # activate without restarting

Local dev install? Use the agentlayer-dev marketplace on both lines: agentlayer-dev and agentlayer@agentlayer-dev. Auto-update is a per-marketplace toggle (/plugin → Marketplaces); it refreshes every plugin from that marketplace at startup, so leave it off if you want to control when each one changes.

Reconcile the home

Run the upgrade skill (/agentlayer:upgrade or $upgrade). It:

  • reads the CHANGELOG's Upgrade blocks from your home's recorded baseline up to the installed version;
  • backs up every file it will touch;
  • runs bun install in the version you just pulled when its packages changed. If that fails, upgrade stops, hands you the command, and records nothing until a re-run succeeds;
  • applies the mandatory changes, and asks before touching anything you may have personalized;
  • on a home wired for Codex, rewrites the .codex/ wiring.

An upgrade notice tells you when one is pending: above the prompt in the Claude Code terminal, with a button that runs upgrade, and in the session banner everywhere else. The dashboard shows a badge too. None of it makes a network call: the home records its template version in .state/version.json and compares it to the installed plugin.

How the release and upgrade contract works underneath: Upgrades and releases.

On this page