When it doesn't work
Before concluding that a tool is broken, the agent must look at the state of the machine: several faults produce no error.
What you ask
"Daimon doesn't seem to do anything: find out why."
What the agent does
It calls daimon_doctor, first. A single call returns the state of each organ, without ever opening a dialog. What it reads:
| Key | What it tells |
|---|---|
permissions | Which system permission is missing |
consequences | What that absence concretely does to each tool |
ceiling | The active ceiling |
exclusions | The state of your exclusions file |
overlay | Whether the process that draws the markers is alive |
cannot_detect | What the diagnostic cannot see: an absence of problem there is not proof |
next | The suggested next steps |
The most common symptoms
| Symptom | Probable cause |
|---|---|
An action answers done with no effect | Accessibilité (Accessibility) permission missing |
| An action waits 30 seconds | Accessibilité permission missing, or confirmation pending |
| Captures fail | Enregistrement de l'écran (Screen Recording) permission missing |
An action is refused | Above the ceiling, or confirmation not obtained |
| A capture is refused or blacked out | An application or area in your exclusions |
| The markers do not appear | Présence à l'écran (On-screen presence) turned off |
| The agent sees no Daimon tool | Daimon not registered in this agent, or agent not restarted |
What you get
A named cause and the steps to follow. For causes that depend on your settings, the Troubleshooting page gives the user-side detail.
Reporting a problem
If daimon_doctor does not explain it, open an issue with its output.