nntrivi2001
9c573f1e3c
Decisions, environment quirks and pitfalls learned while working on AgentHub (docs/claude-memory/, indexed by MEMORY.md). Notes holding personal account details are left out. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.3 KiB
name, description, metadata
| name | description | metadata | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| agenthub-plugin-update-chicken-egg | AgentHub installs at v1.5.9 or older cannot self-detect updates; each machine needs one manual plugin-update command |
|
Until v1.5.10 (2026-09-14), no plugin-cache install of AgentHub could ever see a published release — pluginMarketplaceUrl rejected this repo's own "source": "./" marketplace entry, so the status endpoint answered release_check: "no_remote" and the UI showed no version at all.
The fix ships in v1.5.10, so an install running 1.5.9 or earlier carries the broken check and cannot detect it. Every such machine needs the update run by hand exactly once:
claude plugin marketplace update claude-code-agent-monitor-plugins && claude plugin update agenthub@claude-code-agent-monitor-plugins -y
Why: a broken update-detector cannot deliver its own fix; nothing on that machine will ever offer the newer version.
How to apply: when someone reports "Check for updates shows nothing" on AgentHub, ask for their version first. ≤1.5.9 ⇒ it is this, hand them the command; ≥1.5.10 ⇒ it is a real new bug, investigate server/lib/update-check.js.
Related: agenthub-release-state, agenthub-no-launchd-on-macos.