Repository navigation
Fast Skylight sync for groceries and chores, without Claude (D212) - #28
Merged
Merged
Conversation
The owner approved a small non-Claude sync that keeps chores and the grocery list within a couple of minutes of Skylight, both ways. A LaunchAgent runs engine/tools/skylight_sync.py every 2 minutes. It talks to skylight-mcp 1.7.0 over stdio, with its own token file, and reads the login from the Keychain. A change on one side is copied; done beats not-done; the newer rename wins when both sides have times, otherwise both are kept and listed; deletions never cross, and a delete's survivor isn't re-created. Chores match by the reminder's due date, and only chore-map links sync. Nothing is created, dated or rescheduled on a chore. Off until config says "skylight_sync": "tool". Also ek add-list. Tested: 42 tests for the rules and the stdio client against a stand-in MCP server, the CI checks, and ek add-list refusing an existing name. Not tested: a real Skylight account or Reminders writes, which wait on the Keychain login and the owner's go to switch it on. Co-Authored-By: Claude Opus 5.5 <[email protected]>
So the owner can read what it would change before switching it on, and the Claude syncs keep handling groceries until then. A dry run only reads. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Typing it at security's own prompt keeps it out of shell variables and the process list. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
D212: the owner approved ("Yes, build it (Recommended)", Simon chat, 2026-11-15) a small non-Claude sync that keeps chores and groceries within 1 to 2 minutes of Skylight, both ways. Designed with Head of Communications.
What it is
engine/tools/skylight_sync.py, run every 120 s by a LaunchAgent (installprints the command; nothing is installed by this PR). Its own log,logs/skylight-sync.log, one line per pass; every write goes todata/log.md.data/.skylight-tokens.json), separate from Claude Code's connector.Theseus Skylight), passed only in skylight-mcp's environment, never written or logged. An expired login stops the sync and leaves an alert until someone runsresume.config.jsonhas"skylight_sync": "tool". When it's on, RULES §3.6 tells the Claude syncs to leave groceries and chores to it and show its alerts.ek add-list --title T.Rules (all tested)
grocery_store_sections); no section goes to the first store and gets that section; first match by normalized title and store, ignoring quantities and curly quotes.Tested: 42 tests in
tests/test_skylight_sync.py(now inscripts/ci-checks.sh): matching, done and rename conflicts, deletions, store moves, chores by date, the stdio client and its error handling against a stand-in MCP server, the off switch, and no credentials in the LaunchAgent.ek add-listrefuses an existing name.Not tested: a real Skylight account or real Reminders writes. Both wait on the Keychain login (N207) and the owner's go. Also unverified: the exact shape of skylight_list_chores rows for recurring occurrences, and whether Skylight list items carry an update time. The first
run --dry-runagainst the real account checks both before anything is switched on.Needs the owner: adding the Keychain item, a dry run he reads, turning on
skylight_sync, and the LaunchAgent install.🤖 Generated with Claude Code