auto-updater
teylersf/openclaw-auto-updater
Automatically update OpenClaw nightly via cron job to keep your agent current.
What is auto-updater?
This skill sets up a nightly cron job that automatically stops the OpenClaw gateway, runs updates, and restarts it. Use it when you want your agent to stay up-to-date without manual intervention.
- Runs a scheduled cron job at 4 AM daily (customizable) to update OpenClaw
- Stops the gateway before updating and restarts it afterward
- Executes updates via a standalone shell script independent of the agent process
- Logs update activity to ~/openclaw-update.log for troubleshooting
- Allows manual immediate updates on demand
How to install auto-updater
npx skills add https://github.com/teylersf/openclaw-auto-updater --skill auto-updater- OpenClaw installed and configured
- Cron daemon available on the system
- Ability to execute shell scripts
How to use auto-updater
- 1.Say 'set up auto-updater' to enable nightly updates at 4 AM
- 2.The skill copies the update script to your home folder and creates the cron job
- 3.To change the update time, say 'change update time to [time]'
- 4.To run an update immediately, say 'update yourself now'
- 5.Check ~/openclaw-update.log if you need to troubleshoot update issues
Use cases
- Keep OpenClaw automatically updated with the latest version every night
- Ensure your agent has the newest features and bug fixes without manual action
- Run updates during off-peak hours (4 AM default) to minimize disruption
- Trigger manual updates immediately when needed without waiting for the scheduled time
- OpenClaw users who want hands-off maintenance
- Teams running agents that need to stay current with upstream releases
- Developers who prefer automated over manual update workflows
auto-updater FAQ
The agent cannot execute commands while the gateway is restarting. A standalone script runs independently of the agent process, ensuring updates complete successfully.
The default is 4 AM daily, but you can customize it by asking to change the update time.
Review the log file at ~/openclaw-update.log to see update history and any errors.
Yes, say 'update yourself now' to run the update script immediately.
Full instructions (SKILL.md)
Source of truth, from teylersf/openclaw-auto-updater.
name: auto-updater description: | Automatically update OpenClaw every night. Use when the user wants their agent to stay up-to-date with the latest OpenClaw version. Runs a cron job that stops the gateway, runs the update, and restarts. Triggered when user mentions: "update yourself", "auto update", "nightly update", "keep updated", "self update", or any variation of updating the agent.
Auto-Updater Skill
This skill keeps OpenClaw updated by running a nightly cron job that executes an external shell script — so the update works even when the gateway restarts.
Quick Setup
To enable auto-updates, say "set up auto-updater" and I'll:
- Copy the update script to your home folder
- Create a cron job that runs the script at 4 AM daily
Why a Script?
The agent can't run commands while the gateway is restarting. We use a standalone shell script that runs independently of the agent.
The Update Script
#!/bin/bash
# OpenClaw Auto-Updater
openclaw gateway stop
openclaw update.run
openclaw gateway start
Change Update Time
Tell me "change update time to [time]" and I'll update the cron schedule.
Manual Update
Say "update yourself now" and I'll run the script immediately.
Troubleshooting
Check the log file: ~/openclaw-update.log
Related skills
More from teylersf/openclaw-auto-updater and the wider catalog.
docx
Create, edit, and analyze .docx files with tracked changes, comments, and formatting preservation.
pptx
Create, edit, and analyze PowerPoint presentations (.pptx files) with text extraction, XML manipulation, and HTML-to-PPTX conversion.
xlsx
Create, edit, and analyze Excel spreadsheets with formulas, formatting, and data visualization.
debug-mantra
Four-step debugging discipline: reproduce reliably, trace the fail path, falsify hypotheses, cross-reference all observations.
management-talk
Rewrite engineering updates for leadership—shaped for JIRA, Slack, email, standup, or meetings.
post-mortem
Write the canonical engineering record of a fixed bug: root cause, mechanism, fix, validation, and how it slipped through.