Skip to main content
Give Embedder a clear task, the relevant project context, and a way to check the result. These guides explain the controls you use along the way.

Start a task

  1. Open the repository and select the hardware you are working with.
  2. Run /init to document the project’s build, test, and hardware workflows in EMBEDDER.md.
  3. Describe the change or problem, including the expected behavior.
  4. Choose a mode and review the proposed actions.
  5. Check the diff and the build, test, or hardware evidence before accepting the result.
If you have not installed Embedder yet, start with the Quickstart.

Development workflows

Build, test, flash, observe, and debug a firmware change.

Agent modes

Use Act to implement, Plan to review an approach, and Debug to investigate target state.

Approvals

Choose which actions need your confirmation.

Sessions

Continue a conversation, queue follow-up work, or return to an earlier change.

Give Embedder useful context

The hardware catalog connects your platform and peripherals to relevant documentation and skills. Project instructions describe how to work in your repository, and schematics explain the board’s connections.

Project instructions

Record build commands, board constraints, and verification steps in EMBEDDER.md.

Peripherals

Add the parts and datasheets used by your project.

Schematics

Ask questions about components, nets, and board connections.

Skills

Reuse instructions for board setup, debugging, and project workflows.

Continue larger projects

  • Use project memory for confirmed facts you want to reuse in later sessions.
  • Ask for subagents when independent parts of a task can proceed in parallel.
  • Set a goal or bounded loop when work needs repeated attempts or checks.
  • Follow best practices to make requests specific and results easy to verify.
Last modified on September 18, 2026