← ClayCONTENT HISTORY
WHAT CHANGED
Update to Clay
Snapshot Nov 18, 2026 · 06:19 UTC · version 2.38.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Clay and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Keep Clay up to date. Use when the user asks to update or upgrade Clay, the plugin, or the `clay` CLI; when `clay update` reports the CLI is pinned / managed by the plugin; or to check whether a newer version is available. The plugin and CLI update independently; migrate older plugin-managed installs through setup.",
"included_files": [],
"name": "update",
"skill_md_contents": "---\nname: update\ndescription: Keep Clay up to date. Use when the user asks to update or upgrade Clay, the plugin, or the `clay` CLI; when `clay update` reports the CLI is pinned / managed by the plugin; or to check whether a newer version is available. The plugin and CLI update independently; migrate older plugin-managed installs through setup.\nallowed-tools: Bash(clay --version), Bash(clay update --check), Read\n---\n\n# Keeping Clay up to date\n\nBefore using this skill, read the `clay` entry skill if you haven’t already this session, and follow its access guidance.\n\nThe CLI is installed independently. The plugin declares its minimum compatible CLI\nin `cli-min-version`; a newer CLI is fine. Updating one does not automatically update\nthe other.\n\n## 1. Check and update the CLI\n\nRun `bash \"<PLUGIN_ROOT>/scripts/check-cli.sh\" plain`, resolving `<PLUGIN_ROOT>` two\nlevels above this skill. If it reports a missing, old, or plugin-managed executable,\nfollow the `cli-setup` skill to locate the executable and choose the appropriate action:\nexisting native CLIs upgrade through their own `clay update`, npm CLIs through npm,\nand missing or plugin-managed CLIs use installation or migration. An old plugin forwarder needs\nmigration even when a cached launcher still responds. Preserve the installation method\nand existing sign-in.\n\nOnce the independent executable works, run `clay update --check` to check the latest\npublished release. Show the user what's new from the release URL when one is returned.\nFor a native installation, run `clay update`. For an npm installation, use\n`npm install --global --ignore-scripts @clay-run/cli@latest`; `clay update` identifies\nnpm installs and provides that direction. Use the verified absolute executable path\nif the current session's PATH has not refreshed.\n\n## 2. Update the plugin\n\nThe marketplace is named `clay-plugins` and the plugin is `clay`. Pick your harness:\n\n### Claude Code\n\nRefresh the marketplace, then update the plugin:\n\n```bash\nclaude plugin marketplace update clay-plugins\nclaude plugin update clay@clay-plugins\n```\n\nThen have the user run `/reload-plugins` (or restart Claude Code) so the new version\nloads. If the plugin still shows the old version after that, the marketplace\nclone was stale — the explicit `claude plugin marketplace update clay-plugins` above\nforce-refreshes it; as a last resort, uninstall and reinstall the `clay` plugin.\n\n### Codex\n\nRefresh the marketplace snapshot, then restart the Codex session:\n\n```bash\ncodex plugin marketplace upgrade clay-plugins\n```\n\n`codex plugin marketplace upgrade` pulls the latest plugin version; restart Codex so\nthe running session picks it up.\n\n### Cursor\n\nCursor is UI-driven — tell the user to do this (there's no reliable CLI path):\n\n- Open **Customize** in the sidebar, find the **Clay** plugin, and click **Refresh**.\n- With Auto Refresh enabled, Cursor picks up new commits atomically on its next refresh\n cycle; a manual **Refresh** forces it.\n- If the content still looks stale, uninstall and reinstall the Clay plugin.\n\n## 3. Verify both installations\n\nAfter refreshing the plugin, read its new `cli-min-version` and run its\n`scripts/check-cli.sh` again. If the minimum increased, run the current plugin's\n`cli-setup` skill. Confirm `clay --version` is at least that minimum. Only investigate\nsign-in if an authenticated command reports an auth error; an update does not require\nanother login.\n\nThe session-start hook makes the same local readiness check. It does not poll releases\nor install software. Hosts without hooks use the `clay` skill's readiness check instead.\n"
}SHA-256 of public snapshot: 857d647d56f67054cc5f27812dc50168c12b379162625a67b24b243aff0f3eee