openclaw - ✅(Solved) Fix Feature proposal: `openclaw update hint` for agent/skill update notifications [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#59304Fetched 2026-04-08 02:26:11
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Participants
Timeline (top)
cross-referenced ×1

Error Message

  1. Does nothing on error — designed to be silent in preamble contexts

Root Cause

  • Zero friction upgrades. The agent sees the hint and can suggest upgrading. No manual polling.
  • Zero network cost. Reads a local file, no API calls.
  • Zero risk. Silent on errors, best-effort only. The outer try/catch swallows everything.

Fix Action

Fixed

PR fix notes

PR #59298: feat(skills): notify agents of available updates via skill preambles

Description (problem / solution / changelog)

Summary

  • Add openclaw update hint subcommand that reads cached ~/.openclaw/update-check.json and prints an UPGRADE_AVAILABLE one-liner when a newer version exists. Zero network calls — reads the state file maintained by the gateway's periodic update check. Silent on errors, designed for preamble contexts.
  • Add bash preamble blocks to all 7 .agents/skills/*/SKILL.md files so every skill invocation surfaces update availability to the agent context.
  • --json mode always emits a JSON object ({ "updateAvailable": false } when current, full object when update available), consistent with every other openclaw ... --json command.

Feature proposal: #59304

Why it matters

There is no way to know a newer OpenClaw version is available when working inside a skill. Users have to remember to run openclaw update manually. This brings the same seamless upgrade notification pattern used by gstack to OpenClaw — the agent sees the hint in context and can suggest upgrading.

How it works

  1. The gateway's existing periodic update check writes ~/.openclaw/update-check.json with lastAvailableVersion.
  2. openclaw update hint reads that file, compares against the running VERSION, and prints:
    UPGRADE_AVAILABLE 2026.3.28 2026.4.1 (latest). Run: openclaw update
  3. Each skill's preamble runs: _UPD=$(openclaw update hint 2>/dev/null || true); [ -n "$_UPD" ] && echo "$_UPD" || true
  4. The agent sees the output and can suggest upgrading.

What changed

  • New file: src/cli/update-cli/hint.ts — 76-line command implementation
  • New file: src/cli/update-cli/hint.test.ts — 9 tests (no state file, no version, up-to-date, newer available, JSON output with update, JSON output without update, local-newer, corrupt JSON)
  • Modified: src/cli/update-cli.ts — registers the hint subcommand under openclaw update
  • Modified: 7 .agents/skills/*/SKILL.md — identical 4-line preamble block each

Test plan

  • 9 unit tests covering all paths including --json no-update output
  • pnpm check (tsgo + lint + format) passes
  • Manual: run openclaw update hint with/without a stale update-check.json
  • Manual: invoke a skill in Claude Code and verify the preamble surfaces the hint

Co-Authored-By: Claude Opus 4.6 (1M context) [email protected]

Changed files

  • .agents/skills/openclaw-ghsa-maintainer/SKILL.md (modified, +6/-0)
  • .agents/skills/openclaw-parallels-smoke/SKILL.md (modified, +6/-0)
  • .agents/skills/openclaw-pr-maintainer/SKILL.md (modified, +6/-0)
  • .agents/skills/openclaw-release-maintainer/SKILL.md (modified, +6/-0)
  • .agents/skills/openclaw-test-heap-leaks/SKILL.md (modified, +6/-0)
  • .agents/skills/parallels-discord-roundtrip/SKILL.md (modified, +6/-0)
  • .agents/skills/security-triage/SKILL.md (modified, +6/-0)
  • src/cli/update-cli.ts (modified, +17/-2)
  • src/cli/update-cli/hint.test.ts (added, +134/-0)
  • src/cli/update-cli/hint.ts (added, +76/-0)
RAW_BUFFERClick to expand / collapse

Problem

When a maintainer invokes an OpenClaw skill in Claude Code, there's no way to know a newer version is available. The user has to remember to run openclaw update manually. Tools like gstack solve this with a preamble pattern — every skill invocation runs a lightweight version check, and the agent sees the result in context.

Proposal

Add openclaw update hint, a zero-network subcommand that:

  1. Reads the cached state file (~/.openclaw/update-check.json) already maintained by the gateway's periodic update check
  2. Compares against the running VERSION
  3. Prints a one-liner: UPGRADE_AVAILABLE 2026.3.28 2026.4.1 (latest). Run: openclaw update
  4. Does nothing on error — designed to be silent in preamble contexts

Then embed a 4-line bash preamble in each .agents/skills/*/SKILL.md so the hint surfaces automatically on every skill invocation.

Why this matters

  • Zero friction upgrades. The agent sees the hint and can suggest upgrading. No manual polling.
  • Zero network cost. Reads a local file, no API calls.
  • Zero risk. Silent on errors, best-effort only. The outer try/catch swallows everything.

Implementation

PR ready: https://github.com/openclaw/openclaw/pull/59298

  • src/cli/update-cli/hint.ts — 76 lines, the command implementation
  • src/cli/update-cli/hint.test.ts — 9 tests covering: no state file, no version, up-to-date, newer available, JSON output, local-newer, corrupt JSON, and --json no-update paths
  • 7 SKILL.md preamble additions (identical 4-line block each)
  • --json mode always emits a JSON object (including { "updateAvailable": false } when current), consistent with other openclaw ... --json commands

Open to feedback on scope, naming, or approach before maintainer review.

extent analysis

TL;DR

Implement the proposed openclaw update hint subcommand to provide automatic version update hints for maintainers.

Guidance

  • Review the provided PR (https://github.com/openclaw/openclaw/pull/59298) to understand the implementation details of the openclaw update hint subcommand.
  • Test the openclaw update hint command in different scenarios, such as when an update is available, when the version is up-to-date, and when errors occur, to ensure it behaves as expected.
  • Consider the benefits of zero-friction upgrades, zero network cost, and zero risk provided by the proposed solution.
  • Evaluate the added preamble in each .agents/skills/*/SKILL.md file to ensure it effectively surfaces the update hint on every skill invocation.

Example

No explicit code example is provided, but the implementation details can be found in the mentioned PR, specifically in src/cli/update-cli/hint.ts and src/cli/update-cli/hint.test.ts.

Notes

The proposed solution relies on the existing cached state file (~/.openclaw/update-check.json) and does not introduce any new network requests, making it a low-risk and efficient approach.

Recommendation

Apply the proposed workaround by implementing the openclaw update hint subcommand, as it provides a seamless way to notify maintainers of available updates without requiring manual checks.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING