Skip to main content
Start with the VS Code extension. It provides Embedder chat, project setup, schematics, conversation history, and the Monitor for serial data and lab instruments. The extension installs or connects to the compatible local Embedder runtime.

​
Install the extension

Install Embedder from the VS Code Marketplace. You can also open Extensions with Cmd+Shift+X on macOS or Ctrl+Shift+X on Windows and Linux, search for Embedder, and select Install.
When the extension cannot find a compatible Embedder binary, it prompts you to install one. You do not need to install the terminal UI separately for normal VS Code use.

​
Open Embedder and sign in

1

Open chat

Open the Command Palette and run Embedder: Open Embedder Chat.
2

Complete sign-in

Follow the browser sign-in flow. If the browser does not open, use the link shown in the chat panel.
3

Choose a team and project

Select the team and project for the workspace. Create a project when this repository has not been connected to Embedder before.
The chat can remain in the secondary side bar or open in an editor tab. See VS Code extension for the available views and commands.

​
Select the hardware context

Choose the platform that matches the firmware target, then add the peripherals populated on the board. Embedder uses the selected parts to load the relevant datasheets, reference manuals, and errata. Use the project setup flow to:
  1. Select a catalog platform.
  2. Add catalog or custom peripherals.
  3. Upload schematics when the board design should define the hardware context.
  4. Review detected components before accepting them.
If the board is absent from the catalog, use custom platforms and schematics.

​
Initialize the repository

Run /init in chat:
Embedder inspects the repository for build, test, debug, flash, and observation workflows. It then asks you to verify the detected setup before it writes EMBEDDER.md. Correct an uncertain command or target at the question step. The finished file gives later sessions the same project-specific instructions without repeating setup in every prompt. See Configure EMBEDDER.md for the generated sections and safe manual edits.

​
Open the Monitor

Run Embedder: Open Embedder Monitor from the Command Palette. The Monitor can host:
  • Serial connections through UART, RTT, ITM, xSCOPE, or CAN
  • Live plots and calculated channels
  • GDB state, logic captures, power measurements, and oscilloscope traces
  • Instruction trace and coverage reports
  • Bluetooth tools and project dashboards
For a first serial connection:
  1. Add a Serial tab.
  2. Select the connected port or probe transport.
  3. Set the connection parameters.
  4. Connect and confirm that expected output appears.
The agent can read Monitor history and send device commands from the same chat session.

​
Ask about the project

Start with a bounded question that confirms the selected context:
Use @ to cite a file or directory:
Use @sch: when a parsed schematic contains the component or net:
Embedder reads source files and indexed hardware documents as needed.

​
Make and verify a change

Ask for one change with an observable result:
In Manual approval mode, Embedder runs allowed reads without interruption and asks before unapproved commands or writes. Review each file diff and tool request before accepting it. If a board is connected, include the runtime check:
Switch to Debug mode when the task needs GDB, coverage, instruction trace, or a hardware script:
Then state what the investigation must preserve:
Read Monitor and debug for probe and instrument setup.

​
Use the terminal UI instead

The terminal UI is optional. Use it for SSH sessions, terminal-only environments, or direct command-line administration. It runs the same agent but does not include the full Monitor, schematic editor, tutorials, or editor tabs. See Use Embedder from the CLI for installation, shared capabilities, and UI differences.

​
Continue from here

VS Code extension

Use chat tabs, the Monitor, schematics, tutorials, and editor commands.

Core concepts

Plan, build, test, flash, and inspect firmware.

Tool approvals

Choose when Embedder asks before running a tool.

Supported hardware

Check platforms, peripherals, probes, and instruments.
Last modified on August 24, 2026