Skip to main content
Use Slack to ask Embedder for a repository change, check progress, and answer follow-up questions. A connected daemon runs the work on your chosen machine.

​
Connect Slack

An owner or admin of the Embedder organization must connect the workspace. A team-only admin role does not grant this permission. You also need permission in Slack to install the app or have its installation approved.
  1. Connect the GitHub repository and map it to an Embedder project.
  2. In the Embedder app, select a team in the intended organization and choose Slack in the sidebar.
  3. Choose Add to Slack, select the intended Slack workspace, and approve the requested permissions. Return to Embedder and confirm Slack is connected with the correct workspace name; use Refresh if needed.
  4. Add the Embedder Slack app to the channel where you want to request work.
  5. Start the execution host with embedder start daemon and check it with embedder monitor.
The connection applies to the Embedder organization, not just the team selected when you install it. Choose the organization whose linked repositories should be available from that workspace. Install into an individual Slack workspace; organization-wide Enterprise Grid installation is not supported.

​
Start a task

Name the full repository when the channel has access to several projects:
For an existing pull request, include its link. State whether the task should change files or only investigate. If Embedder replies with an account-connection link, open that link from Slack, sign in to the intended Embedder account, and choose Connect Slack. Complete authorization with the same Slack workspace and user that sent the request, then return to the thread. Starting from the supplied link preserves the workspace selection.

​
Continue in the thread

Keep follow-ups in the same thread. Embedder can post progress and ask for missing information there. Messages sent during a run may wait until the active turn finishes. Review the result before starting dependent work. A research task can finish with an answer and no code changes; an implementation task should identify its branch or pull request and verification results.

​
Review changes

The coding agent commits, pushes, and opens or updates the PR during the run. Existing PR work uses its branch; default-branch work creates embedder/work/<work-item-id> and a PR. Ask for local-only work to opt out of publishing. If the target branch changes during the task, request a new run against its current state. Embedder posts the completion summary in the Slack thread. Successful Slack runs retain their checkout for follow-ups; stale state is cleaned up after seven days. Review changes and verification before requesting a merge.

​
Troubleshoot

  • Add to Slack is missing: check that you are an owner or admin of the Embedder organization. If Slack is not configured appears, ask your Embedder administrator to enable the integration for your environment.
  • Workspace is linked elsewhere: disconnect it from the other Embedder organization before connecting it here.
  • Installation was canceled or expired: start Add to Slack again from the intended organization’s Slack page.
  • Account connection fails: reopen the link from the Slack request and use the same Slack workspace and user with the intended Embedder account.
  • The request waits: check the daemon connection and repository-to-project mapping.
  • Another task is using the board: inspect embedder monitor and wait for the active hardware operation.
  • The repository is ambiguous: give its full owner/repository name.
  • A follow-up cannot resume: start a new thread request with the repository, current branch, and remaining work.
See Operate the daemon for execution-host setup.
Last modified on September 12, 2026