Open VS Code Settings and search for Embedder. Most changes can be made there without editing a file.
Customize the interface
- Show Serial (
embedder.showSerial): show the Embedder Monitor. Enabled by default.
- Show Reasoning Summaries (
embedder.showReasoningSummaries): show the summaries displayed during and after a response. Enabled by default.
- Close Agent Chat On Activation (
embedder.closeAgentChatOnActivation): close VS Code’s built-in agent chat on Embedder’s first activation in a workspace. Enabled by default.
- Move Chat To Secondary Sidebar On Activation (
embedder.moveChatToSecondarySidebarOnActivation): reveal Embedder chat in the secondary side bar on first activation. Enabled by default.
For example, to hide reasoning summaries:
The two activation settings affect the initial workspace layout. Use Embedder: Arrange Layout (Chat → Secondary Side Bar) to arrange an existing workspace.
Choose the CLI installation
The extension normally finds or offers to install a compatible Embedder CLI.
embedder.cliPath: an absolute path to your preferred executable. Leave it empty for automatic selection.
embedder.autoInstallCli: offer installation when a compatible executable is missing. Enabled by default.
embedder.startupTimeoutSeconds: how long to wait without startup progress before restarting. The default is 300 seconds; allowed values are 30–900. Increase it if antivirus scanning makes the first launch unusually slow.
Run Embedder: Restart CLI Server after changing the executable or startup timeout. The timeout setting is machine-overridable, so you can configure it separately for remote hosts.
Change project behavior
Use these controls for settings that belong to the workflow:
/model to choose a model; /connect to manage additional model providers.
/approvals to control which commands need confirmation.
/static-analyzer to enable and configure code diagnostics.
/mcp to connect external tools.
/init to create or refresh EMBEDDER.md.
In the terminal UI, use /theme for colors and /keybindings for navigation preferences.
Use .embedder/xmos.json for project-specific artifact, target, adapter, and simulator settings. Environment overrides are useful for machine-specific installations:
EMBEDDER_XTC_PATH: XTC Tools installation root.
EMBEDDER_XRUN_PATH: xrun executable.
EMBEDDER_XMOS_XE: application artifact when the project file does not select one.
EMBEDDER_XMOS_SIM: true for simulation or false for hardware when the project file does not select a target.
EMBEDDER_XMOS_ADAPTER_ID: adapter when the project file does not select one.
EMBEDDER_XMOS_SIM_ARGS: additional simulator arguments.
EMBEDDER_XSCOPE_CLIENT_COMMAND: custom host decoder command.
Set overrides in the environment that launches Embedder and restart it after changes.
Troubleshoot
If chat fails to start, check the configured executable and run Embedder: Show Build Info to identify the installed versions. Restart the CLI after correcting the path.
For an issue that persists, run Embedder: Open CLI Logs or use /bug with the steps to reproduce it. Support may ask you to change embedder.logLevel to trace, reload VS Code, and reproduce the issue once. Restore the previous level afterward. Last modified on September 18, 2026