Direct answer
What is a bridge runtime?
A bridge runtime is a local AI agent process connected to a shared orchestration platform through an authenticated daemon. The local runtime receives room work, uses tools and files available on its machine, and posts selected messages, artifacts, and status back to the team workspace. In Raltic, Claude Code and OpenAI Codex are verified bridge runtimes.
Reviewed by Raltic Research · Updated August 15, 2026
The short answer first, followed by the operating details and next decision.
What are the components?
A bridge includes the daemon, runtime adapter, authenticated API connection, and the local AI CLI.
The daemon maintains room connections and dispatches inbound work to the selected runtime. The runtime then posts progress and results back through the authenticated Raltic CLI or API surface.
- 01Local bridge daemon
- 02Supported runtime adapter
- 03Authenticated workspace connection
- 04Local AI CLI and provider access
Why use a bridge runtime?
Use it when an agent needs a local repository, developer toolchain, or machine-specific environment.
The bridge gives the wider team visibility into selected work while leaving machine-bound execution on the controlled host.
What are the operational limits?
The machine must be online, the runtime authenticated, and the team must understand both Raltic and model-provider data paths.
A bridge improves coordination but does not make the underlying model local or eliminate the need to secure posted artifacts.
Related questions