Settings & Languages
There are two places settings live: the desktop agent, for everything about the assistant itself, and the CoPilot Settings application, for what each CAD add-in does. This page says which is which, and covers the interface language.
Where the settings are
The desktop agent's Settings window
This is the one you will use. Open it from the balloon's right-click menu (Settings…), from the tray menu, or from the chat card's Settings and more menu. It has a page per subject:
- Account — the server URL and your sign-in. The session is kept until you sign out; see Sign In & Out.
- Agent — Start with Windows, Start hidden (tray only), the show/hide and talk hotkeys, the balloon's icon and whether it snaps to screen edges, the chat window's docked position, the theme, and the interface language.
- CAD sessions — which version to launch when several are installed, what to do after a crash, and whether to start a CAD on demand.
- Channels — your own Telegram bot and your own WhatsApp number, hosted on this PC, and the list of senders allowed to drive your CAD systems. See Channels & Messaging.
- Coding agents & MCP — the MCP server inside the agent that lets a coding agent drive your CAD sessions, and one-click registration for the coding agents it detects.
- Knowledge — your own knowledge folder, an administrator-managed machine-wide folder, and your documents on the server. Files in a higher layer replace the same path below. See Knowledge Base.
- Voice — speech-to-text and text-to-speech. Keys are stored on this PC, encrypted for your Windows account, never in a settings file.
- Advanced and Support — log level, the diagnostics folder, and your help preference.
The CoPilot Settings application
A separate small application for what the CAD add-ins do. Its CoPilot Settings page can be set globally or overridden per CAD application — the Settings for: box at the top chooses which file you are editing.
- Server URL and Language.
- Chat panel — Show chat panel inside the CAD (legacy). Off by default: the chat lives in the desktop agent, and the CAD's CoPilot button opens it. One value for every CAD, and it takes effect the next time that CAD starts. See The Desktop Agent.
- Unattended — Approve deletes, scripts and other prompts automatically. Leave it off to be asked each time. Everything approved automatically is listed in the chat and in the unattended log. For one conversation only, type
/unattended sessionin the chat instead. - Context compression and the knowledge folders.
Unattended mode — /unattended
The same switch can be typed in the chat, which is how you scope it to one conversation:
/unattendedor/unattended session— this conversation only. Never written to disk; it ends when the conversation does./unattended always— every conversation on this computer until you turn it off. This is the same thing as the Unattended checkbox above./unattended off— back to asking, and forgets the session scope. It applies to your very next message./unattended status— what is in force right now.
Every automatic approval is recorded — written into the chat as it happens and appended to %AppData%\CADCoPilot\logs\unattended.log, naming the operation and its arguments. An automatic approval is never remembered: nothing joins a permanent allow-list because a machine was left running.
It covers destructive CAD operations (deletes, close-without-saving, undo, revert), running a script or a DLL, an HTTP host / database / listener target, the agent's own sensitive settings and knowledge removals, and the approval cards including the coding agent's permission card. It does not cover, and these will still stop an unattended run:
- A CAD dialog nobody has a rule for. An unrecognised modal is left alone on purpose — clicking one blind is how an unattended run loses work. Give the dialog a rule first, and it is handled.
- Signing in. Browser sign-in cannot be approved automatically; a person has to sign in.
- Hard refusals and organization policy. Unattended mode answers questions; it does not grant permissions the account does not have.
- The coding agent's own risk review. When the chat is backed by a coding agent, that agent has its own safety reviewer outside CAD CoPilot. Measured on 2026-09-20 with unattended on, Codex CLI still refused to overwrite an existing
.prtfile with “This action was rejected due to unacceptable risk”. No CAD CoPilot setting turns that off — write to a new filename, or use a different backend.
If you do not want a blanket switch, a CAD-operation approval card also offers “Always allow <operation> this session”, which grants just that operation on just that CAD until the desktop agent restarts.
Its other pages are CAD Applications (the launch shortcut for each CAD system, used when a message arrives and the application is not running), Messaging Platforms, Service Control and About.
Language
The interface is available in 12 languages: English, Deutsch, Français, Español, Italiano, Português, Nederlands, Polski, Norsk, Svenska, Dansk and Suomi.
Switching the language applies immediately — no restart needed. The AI also answers in your language automatically: with the UI set to Deutsch, replies and progress messages arrive in German.
Prompt in your language
You can write prompts in your language too — the same operations run either way, and the answer comes back in your language:
With the UI language set to English, CoPilot replies in English.
The same request in German — CoPilot creates the plate and replies in German.
In French — CoPilot creates the part with the 8 mm centre hole and replies in French.
See also
- The Desktop Agent — the balloon, the tray and the chat card.
- Sign In & Out · Channels & Messaging
- Organization Portal — My AI Key and your usage.
- Troubleshooting & FAQ