Coding Agent Drivers

Centidor manages reusable business identity separately from the tool that executes work:

• Agent stores a name, instructions, model source, Skills, and execution policy;
• Engine selects a Managed Agent or Coding Agent;
• Driver implements a Coding Agent tool and protocol, such as Claude Code, Codex, or Kimi Code;
• Runtime is the execution location: Connected Host, Cloudflare Container, or Managed Worker;
• Session is long-lived context bound to an Agent, Project, and Runtime;
• Run is one input and execution within a Session.

A Coding Agent is therefore not a permanently running CLI process. Each Run starts a controlled child process. Continuity is retained by the Centidor Session, the tool's native provider session, and the pinned workspace.

Choose a Driver and Runtime

When you create a Coding Agent, the Console shows only Drivers reported by the Runtime with a qualified version:

The exact combinations are also constrained by model source, permission mode, and Runtime capabilities. Disabled Console controls are guidance only. Agent Gateway validates the combination again during Agent creation, Session creation, scheduling, and dispatch.

Sessions and Runs

The second Run in a Session must resume the exact native provider session returned by the first Run. Resume failure is explicit and never silently creates fresh context. A Session cannot switch Runtimes after creation, and Connected Host state cannot migrate to a Cloudflare Container or vice versa.

An active Run supports structured events, approvals, and cancellation. Model token and thinking deltas remain local to the Runtime. One terminal result carries the complete assistant output, usage, artifacts, and provider session.

Skills and Credentials

An Agent selects immutable Skill revisions. Session creation pins those revisions, and the Runtime materializes or mounts only that snapshot. A Driver can read only the reviewed relative Skill path in the platform registry.

Connected Host machine-default mode keeps the machine's existing login and configuration; Centidor does not override model or authentication variables. AI Gateway mode is available only for Driver/Runtime combinations that passed credential-isolation qualification. Credentials are injected only into the child process and never enter the browser, workspace, logs, events, or artifacts.

See Connected Hosts and Agent Sessions for Host configuration and diagnostics, or TypeScript Agent SDK to invoke a saved Agent.