Skip to main content
Use automation to hand Embedder repository work without keeping a chat open. You ask in GitHub or Slack, and a daemon on a machine you choose does the work with that machine’s toolchain and connected hardware.

​
Set up automation

  1. Connect a GitHub repository and map it to an Embedder project. You need an owner or admin role in the Embedder organization. Slack requests use the same repository mappings.
  2. Install Embedder on the machine that will build and test the project, and sign in.
  3. On that machine, run embedder start daemon.
  4. Run embedder monitor and check that the daemon shows as connected.
  5. Comment @embedder with a request in the repository, or connect Slack and mention @Embedder there.
A request waits until a daemon picks it up. If no daemon is running, nothing starts. In Slack, Embedder posts Waiting for daemon when no daemon has picked up a request after about a minute.

​
Write a complete request

State these in each request:
  • The repository or pull request, if it isn’t clear from where you ask.
  • The change you expect.
  • Constraints, such as APIs or message formats to keep.
  • How to verify the result, such as tests or builds to run.
  • For hardware work, the target board and any power or flashing limits.
Record the project’s build, test and flash commands in EMBEDDER.md so every run can find them.

​
Review what Embedder publishes

Coding requests publish by default. Embedder commits, pushes and opens or updates a pull request during the run:
  • For a request on a pull request, or a Slack request that names one, Embedder pushes to that pull request’s branch.
  • For other requests, Embedder creates a branch named embedder/work/<work-item-id> from the default branch and opens a pull request.
Ask for local-only work if you don’t want a push or pull request. Embedder never merges without a separate request. Review the changes and the verification results first. If Embedder needs a decision, it asks in the same GitHub conversation or Slack thread. Answer there to continue the run.
Daemon runs approve their own actions automatically. They can edit files, run commands and use any hardware the host can reach. Run the daemon under an account that can reach only the repositories, tools and hardware meant for this work, and state hardware limits in each request.

​
Choose a guide

GitHub work

Connect a repository, request changes, and set up pull request reviews.

Slack work

Start and continue repository work in a Slack thread.

Operate the daemon

Start, monitor, scope, and stop the machine that runs the work.

Remote hardware

Use a board attached to another machine.
Last modified on October 13, 2026