Skip to main content
Core concepts explain how Embedder works with your project. Start with the common workflow, then learn how modes, approvals, and session context affect each turn.

​
Understand the operating model

Embedder combines four controls during a task:
  1. Project context supplies source files, EMBEDDER.md, hardware selections, schematics, documents, skills, and saved memory.
  2. The agent mode determines whether the session plans, implements, or uses debugging tools.
  3. The approval policy determines which available tool calls wait for confirmation.
  4. The session keeps the conversation, queued prompts, checkpoints, and compressed context.
Modes and approvals are separate. For example, Act mode can edit files, but an edit still waits when the active approval policy requires confirmation.

Embedded development workflows

Set up a project, plan changes, build, test, flash, observe, and debug.

Agent modes

Choose Act, Plan, or Debug based on the work and evidence you need.

Sessions and context

Manage chat tabs, history, queued prompts, checkpoints, forks, and sharing.

Tool approvals

Control confirmations and configure persistent command and path rules.

​
Make work reliable and reusable

Use these concepts after you understand the basic operating model:

Get reliable results

Write bounded prompts, attach precise context, and require observable evidence.

Skills

Load reusable instructions and install compatible skill packages.

Project memory

Save durable project knowledge and recall it in later sessions.

Subagents and agent teams

Delegate isolated research or parallelize work with explicit boundaries.

Goals and bounded loops

Continue toward an objective or run reviewed work on a fixed cadence.
If this is your first project, complete the Quickstart before reading the concept pages in detail.
Last modified on August 24, 2026