store: Issue Dispatcher: Separate systemd timer and service (not runner.sh template)

graph/configurations/issue-dispatcher-separate-systemd-timer-and-service-not-runn-1df35c.md

@@ -0,0 +1,28 @@
+---
+id: 1df35c2c-3749-4777-af9f-c6e2e5111979
+type: configuration
+title: "Issue Dispatcher: Separate systemd timer and service (not runner.sh template)"
+tags: [claude-scheduled, systemd, timer, issue-dispatcher, configuration]
+importance: 0.6
+confidence: 0.8
+created: "2026-03-02T20:04:46.168718+00:00"
+updated: "2026-03-02T20:04:46.168718+00:00"
+---
+
+# Issue Dispatcher Systemd Setup
+
+## Why Separate Units
+The issue-dispatcher is its own script, not a task run by runner.sh, so it has dedicated systemd units rather than using the `claude-scheduled@.service` template.
+
+## Files
+- `~/.config/systemd/user/claude-issue-dispatcher.service`
+  - `TimeoutStartSec=1800` (30 min for up to 3 issues)
+- `~/.config/systemd/user/claude-issue-dispatcher.timer`
+  - Runs Mon-Fri at 09:45:00
+
+## Key Config
+```ini
+[Service]
+TimeoutStartSec=1800
+ExecStart=%h/.config/claude-scheduled/issue-dispatcher.sh
+```