{"version":"2.1.119","anchor":"daemon-configuration-daemon-json","canonical_anchor":"daemon-configuration-daemon-json","heading":"Daemon Configuration ( daemon.json )","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.119\/e\/daemon-configuration-daemon-json","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.119","markdown":"### Daemon Configuration (`daemon.json`)\n\n**What**\n\nA new JSON configuration file at `~\/.claude\/daemon.json` that defines persistent background workers.\n\n**Usage**\n\n`{ \"scheduled\": [{ \"tasks\": [{ \"id\": \"my-task\", \"cron\": \"*\/30 * * * *\", \"prompt\": \"Check for new issues\", \"directory\": \"\/path\/to\/project\", \"permissionMode\": \"dontAsk\" }], \"maxConcurrent\": 1 }], \"remoteControl\": [{ \"dir\": \"\/path\/to\/project\", \"spawnMode\": \"worktree\", \"capacity\": 32 }] }` **Details** - Worker kinds: `scheduled` (cron tasks), `remoteControl` (bridge to claude.ai), `heartbeat` (health monitoring) - Configuration changes are hot-reloaded \u2014 the daemon diffs old vs new config and starts\/stops\/restarts only changed workers - Unknown config keys are reported but don't block startup - Interactive management via the `\/daemon` slash command with tabbed UI for Scheduled Tasks, Remote Control, and Assistants - Each tab supports add, edit, remove, enable\/disable operations with inline forms **Evidence** Daemon configuration system (search for `\"daemon.json\"`, `\"config validation failed\"`, `\"config reload failed\"`)"}