> ## Documentation Index
> Fetch the complete documentation index at: https://docs.embedder.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get help

> Find the troubleshooting steps for a problem, send your logs to Embedder support, and reach the team.

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](https://docs.embedder.com/quickstart.md#if-setup-stops) |
| Installing, signing in, or starting the chat in VS Code | [VS Code extension: Customize and troubleshoot](https://docs.embedder.com/integrations/vscode-extension.md#customize-and-troubleshoot) and [Settings: Troubleshoot](https://docs.embedder.com/core-concepts/settings.md#troubleshoot) |
| Installing or starting Embedder in a terminal | [Use Embedder in the terminal: Troubleshoot](https://docs.embedder.com/cli/overview.md#troubleshoot) |
| A command that's missing from the `/` menu | [Slash commands: When a command is missing](https://docs.embedder.com/core-concepts/slash-commands-reference.md#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](https://docs.embedder.com/debug-mode/overview.md). |
| A board or part that isn't listed | [If your hardware isn't listed](https://docs.embedder.com/supported-hardware/overview.md#if-your-hardware-isn%E2%80%99t-listed) |
| A remote bridge on another machine | [Remote hardware bridge](https://docs.embedder.com/integrations/remote-bridge.md) |
| GitHub, Slack, or the daemon | [Operate the daemon](https://docs.embedder.com/headless/daemon.md), [GitHub](https://docs.embedder.com/headless/github.md), and [Slack](https://docs.embedder.com/headless/slack.md) |
| An MCP server or a static analyzer | [MCP servers](https://docs.embedder.com/integrations/mcp-servers.md) and [LSP and static analyzers](https://docs.embedder.com/core-concepts/static-analyzers.md) |
| Running out of credits Startup | [Startup plan](https://docs.embedder.com/core-concepts/startup-plan.md) |

## Send your logs

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](https://docs.embedder.com/headless/cli-reference.md#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.

## Contact support

Email [help@embedder.com](mailto: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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.