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.
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 agent-kevin@agentlayer # pull the new version
/reload-plugins # activate without restartingLocal dev install? Swap agentlayer for agentdev-kevin. 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 (/agent-kevin: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 when deps changed, auto-applies the mandatory changes, and asks before touching anything you may have personalized. On a Codex home it also regenerates the .codex/ wiring.
The SessionStart banner and the dashboard badge tell you when an upgrade is pending, with no network call: the home records its template version in .kevin/version.json and compares it to the installed plugin.
How the release and upgrade contract works underneath: Upgrades and releases.