Assistants

It reads, and changes nothing

In this version an assistant changes nothing: no tool applies an effect, saves a file or edits a rule. It gives you the effect it wrote, and you create it in Candeo's editor, preview it, and apply it yourself.

It never reads the values of signals, the key presses or sound an effect reads, serial numbers or file paths. What it reads goes to the assistant and to the service it uses to answer you, under its own policy; Candeo sends nothing itself.

Turning it on

In Settings › Assistants, turn on Let assistants use Candeo, choose your assistant, and Copy the text shown into its settings — for Claude Desktop, claude_desktop_config.json:

{
  "mcpServers": {
    "candeo": {
      "command": "C:\\Users\\you\\AppData\\Local\\Microsoft\\WindowsApps\\candeo.exe",
      "args": ["--mcp"]
    }
  }
}

Settings writes the path of your own Candeo, one that survives updates. For Claude Code, it is a command to run once:

claude mcp add --transport stdio --scope user candeo -- "C:\Users\you\AppData\Local\Microsoft\WindowsApps\candeo.exe" --mcp

Restart the assistant: Settings lists it, by its name, once it is connected. Turning the setting off disconnects every assistant.

Only your programs

The assistant starts Candeo's own program with --mcp, which starts nothing: it relays to the Candeo already running, through a channel only your account on this computer can open. No network port opens, and there is no token to copy or leak. With Candeo closed, or the setting off, the assistant's log says so.

Further

Every tool and resource, what each returns and what is never handed out, is in docs/api/mcp.md; the reasons behind these choices, and what comes next, in docs/design/mcp-server.md. The rest is in the privacy policy.