Skip to content
CodeBook

External worker runtimes

Run a station through MCP pull, signed webhooks, GitHub Actions, Devin, or a dedicated adapter for GitLab CI/CD, CircleCI, Buildkite, Cursor, Jules or Copilot.

An external runtime executes work outside CodeBook while CodeBook tracks the run and routes its result. Runtime kinds include generic MCP pull, signed webhook, GitHub Actions and Devin, plus dedicated adapters for GitLab CI/CD, CircleCI, Buildkite, Cursor, Jules and GitHub Copilot, each written against the vendor's own API.

Connect and assign

Add the runtime in the factory’s runtime settings, supply the credentials and configuration required by its kind, then assign it to a station or eligible routing candidate. Factory and station permissions must allow external execution.

The remote worker receives a brief and reports progress or completion using the supported runtime contract. CodeBook tracks external references and deadlines. Follow the run trail when a provider is slow, rejects a request or never reports a result.

Return evidence

Report pass, fail or blocked with an explanation and the artifacts the station requires. A successful HTTP dispatch is not a completed task. Do not retry blindly after a timeout: first determine whether the remote worker created a branch, changed a file or performed another external action.

MCP and SDKs

Connect a worker using the workflow MCP server when the runtime can claim CodeBook work and return the result. The app repository includes first-party TypeScript and Python SDKs with exclusive claims, progress, scoped context, artifacts, token usage and human handoff. Station execution on an outside runtime can be held when a work order’s chosen limits cannot be enforced. Workflow MCP server · Worker SDKs · Work order limits