-
-
Notifications
You must be signed in to change notification settings - Fork 80.7k
[Bug]: 2026.5.27 Refresh still says stale #87730
Copy link
Copy link
Closed
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.ClawSweeper found an open linked pull request for this issue.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.This issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.
Description
Metadata
Metadata
Assignees
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.ClawSweeper found an open linked pull request for this issue.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.This issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.
Type
Fields
Priority
None yet
Bug type
Behavior bug
Beta release blocker
No
Summary
On 2026.5.27, a manual plugin refresh on my source-checkout install still leaves the CLI warning that the saved plugin list is stale.
Steps to reproduce
Expected behavior
After the manual refresh, the next plugin list command should use the saved plugin list or report no stale-source warning.
Actual behavior
The refresh updates the saved plugin list, but the next command still ignores it and reports
persisted-registry-stale-source.OpenClaw version
2026.5.27 (
27ae826)Operating system
macOS 26.5, Node v22.22.3
Install method
Source checkout at
~/dev/openclaw-src, built locally. Main CLI is installed through pnpm at~/Library/pnpm/openclaw.Model
No model call is involved in this repro. The live default agent model on this install is
openai/gpt-5.5withagentRuntime.id = codex.Provider / routing chain
No provider request is made. The repro is CLI-only:
Additional provider/model setup details
The live default agent config follows the same Codex setup used in prior reports:
No token material is included here.
Logs, screenshots, and evidence
Version and CLI path:
The manual refresh writes a fresh saved plugin list with no diagnostics:
The next plugin list command still falls back to the derived list:
The saved list contains both built plugin paths and source plugin paths:
For at least some bundled plugins on this checkout, only the source path exists:
Impact and severity
Low to medium for source-checkout installs. The plugin list still works, but the warning survives the exact repair command it recommends, so operators cannot tell whether the saved plugin list is healthy.
Additional information
This looks like an OpenClaw bug rather than local deployment state because the refresh command updates OpenClaw's own saved file successfully, then the next OpenClaw command says that same saved file is stale.