-
Notifications
You must be signed in to change notification settings - Fork 1
Lifecycle
github-actions[bot] edited this page Sep 18, 2026
·
5 revisions
How to refresh plugins after a release, pin a version, or roll back.
Canonical: docs/LIFECYCLE.md · tags: docs/RELEASE.md.
flowchart LR
A[New tag on GitHub] --> B[Refresh marketplace catalog]
B --> C[Update each group plugin]
C --> D[Reload client]
D --> E[Re-run setup if core changed]
| Action | Command |
|---|---|
| Refresh catalog | /plugin marketplace update nanlabs-agent-toolkit |
| Update plugin |
/plugin update nanlabs-core (repeat per group) |
| Disable / uninstall |
/plugin disable · /plugin uninstall
|
| Pin / rollback | Pin version in plugin manifest or marketplace source SHA; then refresh |
Team Marketplace: Refresh / Auto Refresh. Local installs: git fetch + checkout the tag, keep the same symlinks, reload the window.
agent plugin marketplace add registers a catalog; it does not install a plugin. Use --plugin-dir against a tagged checkout for local CLI loading.
copilot plugin update nanlabs-core
copilot plugin uninstall nanlabs-core
copilot plugin install nanlabs/agent-toolkit:plugins/nanlabs-coreRepeat for other groups.
npx skills update -g
npx skills remove <skill-name> -gPin a tag:
npx skills add nanlabs/agent-toolkit#v0.4.0 -g -yNaNLABS workstations set NAN_AGENT_TOOLKIT_VERSION in ~/.config/nanlabs/agent-toolkit.env.
Re-run /nanlabs-core:setup if core changed. Re-complete MCP OAuth only if a server URL changed (rare). Then verify.