Registering Daimon in your AI clients

Daimon registers itself as an MCP server named daimon in the clients it detects on your computer. Your client then launches it over stdio, with the serve argument.

Three ways to register it

1. The setup walkthrough (panel › Relancer l'installation… (Re-run setup…)).
2. The panel, with one switch per client.
3. A terminal.

From a terminal

macOS:

/Applications/Daimon.app/Contents/MacOS/Daimon status      # what is detected, what is registered
/Applications/Daimon.app/Contents/MacOS/Daimon install     # register in every detected client
/Applications/Daimon.app/Contents/MacOS/Daimon uninstall   # remove itself

Windows (PowerShell): pipe the output to Out-Host so the prompt waits for the answer.

& "$env:LOCALAPPDATA\Daimon\Daimon.exe" status | Out-Host

After registering, restart your AI client.

Known clients

Daimon knows the configuration of: Claude Code, Claude Desktop, Codex, Gemini CLI, Antigravity, Cursor (editor and CLI), Windsurf, VS Code with Copilot, GitHub Copilot CLI, Zed, JetBrains Junie, Cline, Roo Code, Continue, Amazon Q Developer CLI, opencode, Crush, Mistral Vibe, Qwen Code, Droid, Grok CLI, Goose, LM Studio, 5ire, Witsy, AnythingLLM Desktop, OpenDesign and Trae.

Not all of them have been proven end to end. If one misbehaves, open an issue.

Another MCP client

Declare a stdio server whose command is:

Platform	Command	Argument
macOS	/Applications/Daimon.app/Contents/MacOS/Daimon	serve
Windows	%LOCALAPPDATA%\Daimon\Daimon.exe	serve

The only argument is serve. The server name Daimon itself uses is daimon.

Verify

Ask your AI to call daimon_doctor, then main_ceiling to learn the active ceiling.