BusDK Update
Local Codex workers: autonomous dev workers on your own machine
BusDK now has an early MVP for running Codex-powered development workers locally. The worker loop runs through a direct Codex runtime, receives work through unicast event delivery, and keeps the execution path on your own machine.
The value is straightforward: agentic development that you host yourself. It is still an MVP, so expect an experimental local foundation while hosted workflow coverage remains intentionally limited.
May 31, 2026bus-integration-workerbus-agentlocal Codex workers
The local worker MVP makes the development-agent loop machine-local. A worker can receive a directed event, start a Codex-backed runtime directly, and execute the assigned development turn without requiring a cloud worker service in the middle.
That matters for teams and individual developers who want to keep source checkout access, worker execution, and operational control close to the machine they already use for development. The design keeps the worker lane explicit: delivery is unicast to the intended worker, and the runtime path is built around a direct Codex process with no remote worker dependency in that path.
The maturity is intentionally early. The MVP proves the core local loop while hosted workflow coverage and production deployment concerns remain outside this early scope. The useful result is that BusDK can host the Codex-powered worker loop locally enough to exercise real development tasks and continue hardening the runtime around local control.
The implementation line is split across the worker and agent modules. bus-integration-worker carries the local worker delivery/runtime work, including unicast delivery and the direct Codex worker runtime. bus-agent supplies the Codex runner and app-server client pieces that make a local Codex-backed execution path practical.
See docs.busdk.com for BusDK module documentation.
