Autosync Guide

Autosync keeps your entries fresh without manual sync runs.

What autosync does

• Runs workrail sync on a fixed interval
• Continues across reboots once enabled
• Uses your OS scheduler:
  • macOS: launchd
  • Linux: systemd user timer

Enable autosync

workrail autosync enable --interval 30

If you omit --interval, Workrail uses the default interval.

Confirm it is active

workrail autosync status --verbose

What to check:

• Autosync shows enabled
• Last run timestamp exists
• Next run estimate exists
• Last result indicates a successful sync or "Nothing new to sync"

Check autosync state

workrail autosync status

Verify after restart

After reboot/login, run:

workrail autosync status --verbose

If autosync is correctly installed, it should still report enabled and scheduled.

Common commands

# enable every 10 minutes
workrail autosync enable --interval 10

# check status and logs
workrail autosync status --verbose

# disable
workrail autosync disable

Troubleshooting

Linux: systemd warning

If you see a systemd-related warning, confirm your machine has user-level systemd:

systemctl --user status

If that command fails, autosync cannot run on that machine until systemd user services are available.

No recent runs

Try:

workrail autosync disable
workrail autosync enable --interval 30
workrail autosync status --verbose

Linked repo issues

Autosync can only sync linked repositories. Ensure linking is complete:

workrail status
workrail link

Disable autosync

workrail autosync disable

Best practices

• Use autosync on your primary development machine only
• Pair autosync with a weekly review habit
• Keep commit messages clear to improve grouping quality