Skip to main content

Daemons FAQ

A daemon is a repo-defined operating role for recurring work. It is not a long-running OS process.
Each daemon is defined in a file at:.agents/daemons/<daemon-id>/DAEMON.md
watch wakes a daemon from matching events.schedule wakes a daemon on a cron timetable.A daemon can use either one or both.
Daemons can wake from configured watch signals and/or schedule triggers, depending on the daemon definition and connected surfaces.
Cron schedules are evaluated in UTC.
Yes. Activations are bounded runs with explicit start/end, tool limits, and normal permission constraints.
Daemons can use prior activation history as context, but they do not run as a permanently active process.
Use only the canonical fields:id, purpose, watch, routines, deny, and schedule.Do not invent alternate top-level schema keys for activation mode.

General FAQ

Charlie is strongest in TypeScript and supports many common languages/frameworks used in modern repositories.
Small and medium PRs are typically reviewed in minutes. Complex PRs can take longer when deeper validation is needed.
Check installation scope, invocation method, and permissions first. Then use the Troubleshooting checklist.
Yes. Charlie is useful for both human-authored and agent-authored pull requests.
Charlie can analyze images attached in supported surfaces and use them as task context.