Claude Email Responder
repo: ~/Projects/claude-email-responder · 10 commits · 0 in last 24h, 0 in last 7d ·
Skills used
- /npm1
- /npx1
- /homebrew1
- /backup1
- /state1
- /directives1
Creative ideas + design notes
Commits with substantial prose (≥120 chars) — the rationale behind each move.
80a9000 · 2026-05-19 · gitignore: untrack runtime state.json + broaden snapshot/backup patterns
state/state.json is regenerable at boot via loadState() (returns empty
scaffold on missing file) — committing it added ~2.5k lines of volatile
runtime data to every diff. Untrack it and add state/ + logs/ + the
standard *.bak / *.pre-* / *.orig snapshot patterns to .gitignore so
future fleet sweeps catch any accidental snapshot drops.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
a7dfc6e · 2026-05-08 · Reverse channel: directive parser bypasses Claude for 'act on X' / 'status' / 'pause loop' / 'resume loop'
Steve can reply to any watchdog email with one of these verbs and the
directive lands in ~/Projects/_dw-batch/directives/<ts>-<verb>.json.
The next yolo tick reads the queue and acts.
Bypasses askClaude() — deterministic, free, fast. Falls through to
existing Claude-CLI conversational path for non-directive replies.
'status' verb returns ledger-tail directly in the email reply.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
File tree
6 files tracked. Click any to browse the source at HEAD.
rendered in 0ms