Skip to main content
Early pricing is live. Start free for up to 3 AI systems — no card, no time limit.Early pricing is live. Free for up to 3 AI systems.
All docs
How-to guide

Run the collector on a schedule

Have oabo-collector push once a day with launchd, Task Scheduler, cron or a systemd timer.

10 minFor: Engineer

What to schedule

One command, once a day: oabo-collector push. Each run sends only what changed since the last, keeps its own state in state.json, and is safe to repeat because the server replaces a day's rows rather than adding to them. There is no daemon and no background agent; the collector runs, pushes, and exits.

The installer wrote since_days = 30 into config.toml, so each run looks back 30 days and a missed day is picked up by the next run. Pick a time the machine is usually on; end of the working day works.

Note

The collector has no operating-system-specific code: the same Python command runs on macOS, Windows and Linux. Only the scheduler differs.

Schedule it

Use a launchd user agent. Save this as ~/Library/LaunchAgents/com.oabo.collector.push.plist, replacing YOUR_USER with your short user name (launchd does not expand ~).

~/Library/LaunchAgents/com.oabo.collector.push.plist
<?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.oabo.collector.push</string>
  <key>ProgramArguments</key>
  <array>
    <string>/Users/YOUR_USER/.oabo-collector/venv/bin/oabo-collector</string>
    <string>push</string>
  </array>
  <key>StartCalendarInterval</key>
  <dict>
    <key>Hour</key>
    <integer>18</integer>
    <key>Minute</key>
    <integer>30</integer>
  </dict>
  <key>StandardOutPath</key>
  <string>/Users/YOUR_USER/.oabo-collector/push.log</string>
  <key>StandardErrorPath</key>
  <string>/Users/YOUR_USER/.oabo-collector/push.log</string>
</dict>
</plist>

Load it and run it once now:

Terminal
launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/com.oabo.collector.push.plist
launchctl kickstart -k gui/$(id -u)/com.oabo.collector.push

A laptop asleep at 18:30 runs the job when it next wakes; launchd runs missed calendar jobs on wake.

Check it ran

  • On the machine: oabo-collector status prints the state file path, files tracked and day-keys pushed. The count grows after a successful push.
  • In Oabo: Settings, Connections shows the source with its last event time and event count. A source that never received anything has no last event time.
  • Exit code: 0 when every fingerprint group pushed cleanly, 1 when one was left unmarked for retry, 2 when the config has no credential. Task Scheduler and systemd both record it.

Expected result

The day after scheduling, Connections shows a last event time from the scheduled run and status shows more day-keys pushed.

Change the window

Set since_days in config.toml, or pass --since N after the verb (push --since 60). The option goes after push, not before it. A wider window costs a little more scanning and nothing on the server. See Options.

Previous

Connect Claude, ChatGPT, Claude Code or Codex

Last documented 2026-11-18 against master fb17e1c5. Live release 0.3.1.