Skip to main content
Start with the Embedder VS Code extension to work with chat, source code, schematics, and hardware measurements in one workspace.

​
Install and sign in

  1. Open VS Code Extensions with Cmd+Shift+X on macOS or Ctrl+Shift+X on Windows and Linux.
  2. Search for Embedder and install the extension.
  3. Run Embedder: Open Embedder Chat from the Command Palette.
  4. Follow the sign-in prompts and choose your team.
If prompted, install the compatible Embedder CLI. You do not need to set up the terminal interface separately.

​
Connect a firmware project

Open your repository in VS Code, then choose an existing Embedder project or create one. During setup, select your board or MCU from the hardware catalog and add the peripherals fitted to your board, such as sensors, displays, or radios. These selections give Embedder the hardware context for your project, including associated documentation and matching skills for board setup and firmware workflows. Choose the specific board when available and check the exact part numbers. See Hardware catalog for how these references support your work and how to add custom hardware. Use /peripheral to manage parts. If the design should define the hardware context, upload its schematics. Review detected components against the board revision.

​
Record the project commands

Run:
Embedder inspects the repository and asks you to verify the target, build and test commands, debug setup, bench equipment, and project rules. Correct uncertain values before it writes EMBEDDER.md. See Configure EMBEDDER.md for maintaining the guide.

​
Ask a focused question

Use @ to select a file or directory:
Start in Plan mode if you want a reviewed approach before implementation. Use Act mode for a small, well-specified change.

​
Make and verify a change

Review requested actions and file changes. The default Manually approve setting allows ordinary reads and asks before unapproved commands or edits. A successful build is the first check. If hardware is connected, ask for the runtime result too:

​
Observe the board

Run Embedder: Open Embedder Monitor. Add a Serial tab, select the port or transport, enter the connection settings, and connect. Ask Embedder to inspect the output or collect a bounded measurement. For example:
Use /debug for an investigation requiring GDB or target-state inspection. If the board has faulted, request attachment without programming or reset and review the debugger connection precautions before connecting.

​
Continue

Common workflows

Plan, build, test, flash, and verify a change.

Monitor and debug

Choose serial, debugger, or instrument evidence.

Tool approvals

Control when actions need confirmation.

Use the CLI

Work from a terminal or SSH session.
Last modified on September 19, 2026