Get help

Start with the troubleshooting steps for the part of Embedder that’s failing. If they don’t fix it, send your logs and contact support.

Find the troubleshooting steps

The problem is with	See
Setup that stops partway	Quickstart: If setup stops
Installing, signing in, or starting the chat in VS Code	VS Code extension: Customize and troubleshoot and Settings: Troubleshoot
Installing or starting Embedder in a terminal	Use Embedder in the terminal: Troubleshoot
A command that’s missing from the `/` menu	Slash commands: When a command is missing
A probe, serial port, or instrument	The Troubleshoot section at the end of that tool’s guide. Find the guide in Monitor and debug.
A board or part that isn’t listed	If your hardware isn’t listed
A remote bridge on another machine	Remote hardware bridge
GitHub, Slack, or the daemon	Operate the daemon, GitHub, and Slack
An MCP server or a static analyzer	MCP servers and LSP and static analyzers
Running out of credits Startup	Startup plan

Send logs before you contact support, so the team can see what happened. Each way gives you a report ID to quote.

Where you are	What to do
A VS Code error screen	Select Send logs…, add a note under What happened?, and select Send logs. The screen then shows a Report ID. If the logs can’t be sent, select Open log folder and share the files.
The terminal UI	Run `/bug` followed by what happened and the steps to reproduce it.
A shell, for example on a daemon host	Run `embedder logs submit`. See Send logs to support.

To look at the logs yourself, run /logs to open the log folder, or Embedder: Open CLI Logs in VS Code.

Email help@embedder.com and include:

The report ID from the logs you sent.
Your Embedder version. Run /build-info, or Embedder: Show Build Info in VS Code.
What you did, what you expected, and what happened instead.
For hardware problems, the exact board, probe or instrument, and operating system.

Last modified on November 13, 2026