Use the terminal UI for interactive work over SSH or when you prefer a terminal. Use the VS Code extension for the full Monitor and schematic viewer.
Install
macOS and Linux
Windows
npm
Open a project
Follow sign-in, choose the team and project, and select the hardware context. Run /init to record the project’s commands and rules in EMBEDDER.md.
Work in the terminal
You can plan, edit, build, test, flash, debug, use external tools, and resume conversations. Use the serial sidebar for UART or RTT output. Instrument captures and reports can be summarized in chat or opened later in VS Code.
The terminal does not provide the Monitor’s graphical Plot, Logic, Power, Oscilloscope, Trace, Coverage, or Bluetooth tabs. Use embedder dashboard to preview a dashboard’s layout and static content in a browser. Live dashboard data and device controls require the VS Code Monitor.
Useful controls
Shift+Tab: cycle available modes./: open command suggestions.@: select a file or directory.Ctrl+C or Escape: remove the latest queued prompt, or stop the active turn when the queue is empty./history: resume a conversation./background: inspect background tasks./theme and /keybindings: customize terminal appearance and navigation./exit: close the terminal UI.
The ! prefix enters direct shell mode; ~ enters serial-send mode. These run your input directly. Use an ordinary prompt when you want Embedder to choose an action and interpret its result.
See Keyboard shortcuts and Slash commands.
Run a saved hardware check
The file belongs in .embedder/hardware/. See Hardware scripts for setup and profiles.
Automate repository work
Use embedder start daemon for GitHub and Slack tasks, and embedder monitor to follow them. For equipment attached to another host, use a remote hardware bridge.
See the CLI reference for command options.
Use a self-hosted instance
Run embedder connect <url> to connect to your organization’s instance, or embedder disconnect to return to the hosted service. See instance setup. Last modified on September 18, 2026
