Mike Swanson
2a1ccfac73
memory-dream: read-only memory lint/consolidation analyzer (index, backlinks, stale refs, dup clusters, profile drift); additive-only --apply-safe, all merges/deletes are proposals. sync-memory.sh: additive repo<->harness-profile union (no delete/overwrite, conflicts surfaced), wired to a SessionStart hook. Migrates the useful profile-only memories into the synced repo store. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.5 KiB
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| feedback_scheduling_via_coord_todo | Defer/schedule future work as a coord todo for a later session to pick up - NOT remote CCR routines or local scheduled tasks |
|
When something needs to happen later ("check this tomorrow", "verify in 24-48h", "follow up next week"), create a coord todo (POST /api/coord/todos) assigned to the right user/project. A future ClaudeTools session picks it up at session-start. Do NOT use the /schedule skill (remote anthropic_cloud CCR agents) or local OS scheduled tasks.
Why: Mike's directive 2026-06-01. Remote cloud routines have NO access to the local SOPS vault, the age key, B2/Discord/API creds, or identity.json - so any credentialed task fails there. Local scheduled tasks need the box powered on and run blind. The coord API is the team's shared source of truth and every session already reads pending todos on startup, so a todo is the reliable, credential-available, multi-machine handoff.
How to apply: POST http://172.16.3.30:8001/api/coord/todos. REQUIRED fields the CLAUDE.md doc omits: text (the todo body - NOT title/description), created_by_user, created_by_machine (read user+machine from .claude/identity.json). Optional: project_key, assigned_to_user, auto_created, source_context, parent_id. Put enough context in text (commands, exact targets, the when) that a cold session can act without re-deriving. See reference_coord_messages_api_shape.