Daily sync

The sync engine (~/.claude-sync/sync.sh, see ~/.claude-sync/README.md) does two things each day:

• Every session start: a full sync runs in the background, so the session starts at once. A skill that needs the result waits for it in the background with sync.sh fresh (it returns once a full sync has succeeded today); the reminders skill does that, then notifies what came in and hands it to the session with the user's next message.
• Every morning at a set time (default 09:00): the computer's own scheduler runs sync.sh morning, which syncs and then runs the morning.sh of each installed skill (copied in ~/.claude/skills/ or installed as a plugin). That's how the reminders skill notifies the user even when no session is open.
• At login: the same scheduler syncs once, so a handoff left to run on this computer starts with no session open.

After every sync (these, the session ones and the pane's one-minute poll), the engine runs in the background the on-sync.sh of each installed skill: that's how the handoff skill starts the runs due on this computer and tells the sender when one changed status.

The scheduled run needs the sync engine installed on the computer. It doesn't need Claude Code to be open.

Turn it on, change the time, turn it off

Scripts are in this skill's base directory (~/.claude/skills/daily-sync/ when installed by install.sh; $SK below).

• bash $SK/schedule.sh status: whether the daily run is on, at what time, whether the login sync is on, and the day of the last daily sync.
• bash $SK/schedule.sh on [HH:MM]: every day at that time (24 h, default 09:00), and at login. Running it again replaces the time; on a computer set up before the login sync existed, run it again with the same time to add it.
• bash $SK/schedule.sh off: both.

What it creates:

System	Scheduler	Missed run (computer asleep or off)	At login
macOS	LaunchAgent ~/Library/LaunchAgents/com.claude-sync.morning.plist	runs on wake	LaunchAgent com.claude-sync.login (runs at load)
Linux	a crontab line ending in # claude-sync-morning	skipped; the first session of the day still syncs	an @reboot line ending in # claude-sync-login (at boot)
Windows (Git Bash)	Task Scheduler task claude-sync-morning	runs as soon as the computer is back	task claude-sync-login (at logon)

On Windows a console window opens for a few seconds while the task runs; that's expected.

Before turning it on for the first time on a computer, propose it to the user with the time you'd pick and why, and wait for their yes. Then tell them which time you used.

Check that it works

1. bash ~/.claude-sync/sync.sh morning, then bash ~/.claude-sync/sync.sh status: the last log lines show the sync and each morning: step.
2. bash $SK/schedule.sh status shows the time.
3. If a step failed, the log is ~/.claude-sync/.state/log (and morning.log on macOS).

Add a morning step to another skill

Put a morning.sh at the root of the skill's folder. It runs after the morning sync, with no terminal and no Claude session, so it must be quick, need no input and write nothing to stdout that matters (stdout goes to the sync log).