Skip to main content
Mention Embedder in a connected GitHub repository to request a change. Work runs on your daemon machine, using the Embedder project mapped to that repository.

​
Connect a repository

You need an Embedder project in the intended team, an owner or admin role in that team or its organization, and permission to install the Embedder GitHub App on the repository. Create the project in Embedder first if it does not exist.
  1. Open the Embedder app, select the intended team, and choose GitHub in the sidebar.
  2. Choose Connect GitHub, complete the GitHub installation flow, and grant the app access to the intended repository.
  3. Return to the GitHub page and choose Refresh. If the installation is waiting to be linked, use Finish linking when offered. If that action requires the original installer, ask that person to finish the link.
  4. Find the repository under the linked installation, using Show repositories if the list is collapsed and Search repositories to filter it. In the project selector beside it, choose your Embedder project. Wait for Repository connected and confirm the project name remains selected. A project already linked to another repository cannot be selected here.
  5. On the execution machine, run embedder start daemon. Run embedder monitor and confirm the daemon is connected to the intended team and project.
The installation flow requires a GitHub identity connected to your Embedder account. If you need to sign in with GitHub, use Continue with GitHub on the sign-in screen and confirm that the intended Embedder team is available before continuing. If GitHub or the connection controls are unavailable, ask your administrator to check feature access and your role. The host needs the project’s toolchain and any hardware required by the task. Record setup and verification commands in EMBEDDER.md.

​
Request a change

The coding agent commits and pushes its changes, then opens or updates the pull request. For an existing PR, it uses that PR’s branch. For work starting from the default branch, it creates embedder/work/<work-item-id> and opens a PR. The result identifies the PR, branch, and commit. Coding requests authorize publishing by default. Ask for local-only work if you do not want a push or PR. Merging requires a separate request; review the diff and verification results first. If the PR branch changes while Embedder is working, a push can fail. Request a new run against the current branch instead of overwriting someone else’s work.

​
Answer a question

Reply in the same GitHub conversation when Embedder needs input. Include the missing decision or corrected setup. If the work can no longer resume, start a new request with the relevant context. A paused task can resume after the agent has committed or pushed. Failed and local-only worktrees remain available for inspection until cleanup.

​
Use pull request reviews

On the team’s GitHub page, expand the linked installation and turn on Review beside the mapped repository. Keep a daemon online for that repository’s team and project. The switch is unavailable when the repository is not mapped, you lack permission to manage the integration, or automatic reviews have been stopped for the installation. Under Automatic pull request review, Review new repositories by default controls repositories without their own setting. A repository’s explicit setting takes precedence. Use Stop all reviews to disable automatic reviews and autofix for the installation, and Resume auto review to allow them again. The review itself inspects the diff and reports findings on changed lines without editing files or running build commands. Leave Autofix off if you only want findings. Turning it on requests a separate fix run when a review finds issues; that run can change the PR branch. Check both Review and Autofix on the repository rather than assuming the installation defaults apply. Add .embedder/REVIEW.md to the repository for project-specific review guidance, such as generated-code boundaries and error-handling requirements. A review may be skipped for an empty or very large diff. Split large changes into focused pull requests so findings are easier to assess. A clean review does not replace the project’s tests.

​
Troubleshoot

  • No work starts: check the repository mapping, daemon connection, and selected project scope.
  • Repository is missing: confirm the GitHub App has access to it, finish any pending installation link, and choose Refresh.
  • Review is unavailable: map the repository, check your role, and check whether Resume auto review is shown.
  • No automatic review appears: check that Review is on and a daemon is online for the mapped project. Check the installation’s Automatic reviews per month setting if your team has limited automatic runs.
  • Publishing tools are unavailable: install GitHub CLI on an offline host and set EMBEDDER_GH_PATH to its absolute path. Managed runs use scoped credentials and do not require a persistent gh login.
  • Coding work is rejected after an upgrade: use compatible CLI and server versions; update them together for self-hosted installations.
  • Build tools are missing: install or configure them on the daemon host, then retry.
  • The push fails: check whether the PR branch changed during the run.
  • Work waits for hardware: use embedder monitor to find the active task and let it finish or stop it deliberately.
See Daemon configuration for authentication and host controls.
Last modified on September 12, 2026