Repository navigation
fix(schedule-crons): point example sync-memory cron at workspace script - #732
Merged
Merged
Conversation
`crons.example.json` shipped a sync-memory cron prompt pointing at `~/.sutando-memory-sync/scripts/sync-memory.sh`. That path only exists *after* a successful first-time setup (the workspace script clones the private memory repo there on first run). For any user who copies the example and lands a 30-min cron before running setup — or who never sets `SUTANDO_MEMORY_REPO` at all — every cron firing is just `bash: ...: No such file or directory`. `scripts/sync-memory.sh` (the workspace path) handles both the pre-setup and post-setup case gracefully: - Pre-setup: prints `SUTANDO_MEMORY_REPO not set in .env, skipping sync.` - Post-setup: auto-detects the clone via SUTANDO_MEMORY_SYNC_DIR / script-relative resolution, then runs as before. Point the example at the workspace path so the cron is functional before setup completes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
sonichi
reviewed
May 16, 2026
sonichi
left a comment
sonichi
left a comment
Owner
There was a problem hiding this comment.
LGTM. One-line example-config fix; correct that scripts/sync-memory.sh is the bootstrap, ~/.sutando-memory-sync/... only exists post-clone.
liususan091219
pushed a commit
to liususan091219/sutando-fork
that referenced
this pull request
May 28, 2026
…pt (sonichi#732) `crons.example.json` shipped a sync-memory cron prompt pointing at `~/.sutando-memory-sync/scripts/sync-memory.sh`. That path only exists *after* a successful first-time setup (the workspace script clones the private memory repo there on first run). For any user who copies the example and lands a 30-min cron before running setup — or who never sets `SUTANDO_MEMORY_REPO` at all — every cron firing is just `bash: ...: No such file or directory`. `scripts/sync-memory.sh` (the workspace path) handles both the pre-setup and post-setup case gracefully: - Pre-setup: prints `SUTANDO_MEMORY_REPO not set in .env, skipping sync.` - Post-setup: auto-detects the clone via SUTANDO_MEMORY_SYNC_DIR / script-relative resolution, then runs as before. Point the example at the workspace path so the cron is functional before setup completes. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
`crons.example.json` ships a sync-memory cron prompt pointing at `
/.sutando-memory-sync/scripts/sync-memory.sh`. That path only exists after a successful first-time setup — `scripts/sync-memory.sh` clones the private memory repo to `/.sutando-memory-sync/` on first run.For any user who copies the example and registers the cron before running setup (or never sets `SUTANDO_MEMORY_REPO` at all), every 30-min firing is just `bash: /Users//.sutando-memory-sync/scripts/sync-memory.sh: No such file or directory`.
Hit this today on the primary node: my own `crons.json` had `src/sync-memory.sh` (also wrong — the file lives at `scripts/sync-memory.sh`), corrected locally + on the running cron, then noticed the checked-in template was equivalently broken.
Why the workspace path is the right default
`scripts/sync-memory.sh` handles both the pre-setup and post-setup case gracefully:
The clone-local path doesn't get that fallback — it's just a missing file when setup hasn't happened.
Test plan
🤖 Generated with Claude Code