Keep Shaka up to date
Shaka has no automatic updates: it never installs one on its own. An
installation from a GitHub branch checks for updates about once a day, the first
time you use Shaka in a chat.
If you want to update daily, schedule install --update, or schedule a daily
check and update between chats.
For a pinned release, the check reports only the pinned version and
install --update keeps it; ask your agent about
installing a newer release
instead.
Get a reminder when a Claude Code chat starts
Installing Shaka for Claude Code turns on a startup reminder, a lighter option than a scheduled job. It runs no check of its own. When a new chat starts, it reads the last saved check result and adds its guidance when that check found an update or another change to act on. If no check has run in the last day, it reminds you to run one.
The installer adds the reminder as a SessionStart hook in
~/.claude/settings.json and prints that change. If it cannot read or write
that file, it leaves the file alone, finishes without the reminder, and says so.
Updating Shaka leaves the hook as it is. If you installed Shaka before the reminder was on by default, ask
your agent:
Turn on Shaka's update reminder for new Claude Code chats
The agent reruns the installer for Claude Code, which adds the hook. To turn the reminder off or run the command yourself, see verify and update.
Schedule a daily update or check
Schedule a daily Shaka update using https://shaka.shakacode.com/docs/keep-shaka-up-to-date
To get only a notice, ask for a daily update check instead. Ask your agent to identify the installed helper and follow the steps for your system, then run the job once and read its log. You can also follow the steps yourself.
The steps below schedule a check. To schedule the update itself, change only
the command. On macOS, replace <string>update-check</string> with
<string>install</string> and <string>--update</string>. On Linux and in the
WSL command, replace update-check with install --update. Keep the example
job names so the stop steps below still apply.
The job exits 0 when the update succeeds; otherwise, check its log for the error.
For a check, read the job's log for status and guidance. If the guidance
recommends an update, finish your active Shaka chats first. Then ask your agent to
update and verify Shaka. An unknown
result or an error without a status means the check could not determine whether
an update is available.
The default checkout is ~/.local/share/shaka/source. If you installed
elsewhere, ask your agent which checkout it uses or follow the terminal steps
in the installation guide. Use
the absolute path to skills/shaka/scripts/shaka inside that checkout. Run it
under the account that installed Shaka,
with Git and the authenticated GitHub CLI available to that account.
Scheduled jobs may get a different PATH from your terminal. If needed, set it
in the job or in a wrapper script. Include the directories that contain your
git and gh executables. Check the job's output even when the scheduler
reports success.
Before enabling a schedule, use the helper from your registered installation.
Run "$shaka_helper" install --status using the terminal setup steps.
Confirm the inventory identifies that checkout as your installed branch. For a
PR trial, switch back to the helper from your registered installation. Then run
"$shaka_helper" update-check once with that helper.
Continue when the result is current, recent, or available. For other
results, follow the returned guidance first. If the reason is
unsupported_source or development_source, ask your agent to compare with
official Shaka main. To inspect the branch you installed from, use the
manual comparison.
macOS
Create ~/Library/LaunchAgents/com.shakacode.update-check.plist. Create its
parent directory if needed. Replace the example helper and log paths with
absolute paths for your account. Escape XML characters in the plist values,
such as & for &. Adjust PATH for your Git and GitHub CLI.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.shakacode.update-check</string>
<key>ProgramArguments</key>
<array>
<string>/Users/me/.local/share/shaka/source/skills/shaka/scripts/shaka</string>
<string>update-check</string>
</array>
<key>EnvironmentVariables</key>
<dict>
<key>PATH</key><string>/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin</string>
</dict>
<key>StartCalendarInterval</key>
<dict>
<key>Hour</key><integer>9</integer>
<key>Minute</key><integer>0</integer>
</dict>
<key>StandardOutPath</key><string>/Users/me/Library/Logs/Shaka/shaka-schedule.log</string>
<key>StandardErrorPath</key><string>/Users/me/Library/Logs/Shaka/shaka-schedule.log</string>
</dict>
</plist>
Use a private directory for the log. Set shaka_log_dir to the parent of the
absolute log path used in the plist. Load the LaunchAgent and run it once.
shaka_log_dir="$HOME/Library/Logs/Shaka"
mkdir -p -m 700 "$shaka_log_dir"
chmod 700 "$shaka_log_dir"
launchctl bootstrap "gui/$(id -u)" "$HOME/Library/LaunchAgents/com.shakacode.update-check.plist"
launchctl kickstart "gui/$(id -u)/com.shakacode.update-check"
The example runs at 9 a.m. local time. A run missed during sleep can start when the Mac wakes. See Apple's guide to scheduled jobs.
Linux with systemd
This example uses systemd 240 or later to append to a log file.
Create ~/.config/systemd/user/shaka-update-check.service. %h expands to your
home directory. Create the parent directory if needed. Replace the helper path
if you installed elsewhere. Write literal % characters in your path as %%.
Double literal backslashes and escape embedded double quotes with a backslash.
For a path with other special characters, see systemd service command lines.
If Git or gh lives outside the service's PATH,
set Environment=PATH=... in the service with the absolute directories it needs.
The service starts at / so the check starts outside any project checkout.
[Service]
Type=oneshot
WorkingDirectory=/
UMask=0077
ExecStart="%h/.local/share/shaka/source/skills/shaka/scripts/shaka" update-check
StandardOutput=append:%h/shaka-schedule.log
StandardError=inherit
Create ~/.config/systemd/user/shaka-update-check.timer.
[Timer]
OnCalendar=*-*-* 09:00:00
Persistent=true
[Install]
WantedBy=timers.target
Persistent=true catches up on a missed run when the timer starts. Remove it
if you want the job to wait for the next scheduled time after the timer restarts.
A timer that stays active during sleep can still catch up when the system wakes.
A user timer runs while your user manager is active. If it should run when
you're logged out, check whether your system allows loginctl enable-linger.
See systemd timer settings.
(umask 077; touch "$HOME/shaka-schedule.log")
chmod 600 "$HOME/shaka-schedule.log"
systemctl --user daemon-reload
systemctl --user enable --now shaka-update-check.timer
systemctl --user start shaka-update-check.service
tail -n 20 "$HOME/shaka-schedule.log"
If the service fails to start or the log has no new output, run
systemctl --user status shaka-update-check.service to see its state and any
startup error systemd recorded.
Windows and WSL
For Shaka installed in WSL, save the following in a PowerShell script named
shaka-schedule.ps1. Replace the distribution, Linux user, and helper path
with those of your WSL installation.
wsl.exe --distribution Ubuntu --user me --exec "/home/me/.local/share/shaka/source/skills/shaka/scripts/shaka" update-check *>> "$env:USERPROFILE\shaka-schedule.log"
exit $LASTEXITCODE
In Windows Task Scheduler, create a daily task under your Windows account.
Select Run only when user is logged on.
Set Program/script to powershell.exe. In Add arguments, enter
-NoProfile -File "C:\Users\me\shaka-schedule.ps1", using your script's absolute
path. Your PowerShell execution policy must allow the script. If the first run
produces no log, run powershell.exe -NoProfile -File "C:\Users\me\shaka-schedule.ps1"
in a terminal under that account, using your script path. Read a successful run's output
in shaka-schedule.log in your Windows profile. Before running the task, check
the destination folder and any existing log in Properties → Security.
Use a location where unrelated accounts cannot read the log.
See Microsoft's PowerShell execution policy guide
and WSL command reference.
--exec starts the helper without loading your shell profile. If Git or gh
depends on your profile's PATH, put the Linux command in a wrapper that sets
PATH and use that wrapper as the --exec target.
For Shaka installed directly on Windows, use a daily reminder to ask your
agent to compare the installed branch with its upstream.
The current update-check helper expects Unix-style paths when it looks up Git
and the GitHub CLI. The WSL task checks the separate Shaka installation inside
that distribution.
Stop a scheduled check
- On macOS, unload the LaunchAgent with
launchctl bootout "gui/$(id -u)/com.shakacode.update-check"and move its plist out of~/Library/LaunchAgentsto keep it from loading at the next login. - On Linux, run
systemctl --user disable --now shaka-update-check.timer. - On Windows, disable the task in Task Scheduler.
Move an installation with a scheduled check
After the move, change the job's helper path and run a check to confirm it
reports on the new installation. On macOS, unload the old job with
launchctl bootout "gui/$(id -u)/com.shakacode.update-check" before loading
the edited plist. On Linux, edit ExecStart in the service file and run
systemctl --user daemon-reload. On Windows, edit the PowerShell script used
by the task.