Skip to main content
The runtime determines how an agent’s inner loop runs — how each turn calls the model, interprets intent, and invokes tools. The default runtime is built on Google ADK’s execution flow and works out of the box; you can also switch the execution backend or inject shared processing logic into the flow, without changing the agent itself.

Default runtime

The ADK runtime is the default and needs no extra configuration:

Switch the execution backend

Use runtime to select the inner-loop execution backend: Install the Codex Python SDK before selecting the Codex runtime:
The Codex runtime in VeADK 1.0.1 allows command execution, host file access, and network access by default, without interactive approval. Run trusted tasks in an isolated environment and restrict the credentials and data available to the process.

Skills and tools in the Codex runtime

VeADK 1.0.1 makes skills loaded through ADK SkillToolset or the legacy skills entry point available to the Codex runtime. The runtime can also call an agent’s function and MCP tools:
The MCP server process and its tools receive the permissions allowed by the current environment. Connect only trusted servers and restrict their access to files, networks, and credentials.

Codex backend requests

Web search is disabled by default when the Codex runtime calls models through Volcengine Ark. Set CODEX_SHIM_MAX_TOOL_ITERS to an integer greater than 0 to let the runtime call VeADK’s web_search and web_fetch tools and return their results to the model for a bounded number of rounds:
Web search requires outbound network access and any credentials required by the selected tools. See Web search for configuration. Web content comes from external sources; validate it in production and do not execute search results as trusted instructions.

Request processing

Without touching business logic, you can inject shared cross-cutting processing into each run. Pass a processor to run_processor, for example to enforce login via identity authentication:
When unset, the default processor is used and behavior is unchanged. VeADK ships AuthRequestProcessor as a ready-made implementation for identity authentication.

Custom processors

Every processor subclasses the abstract base BaseRunProcessor and implements its process_run(runner, message) method. That method returns a decorator wrapping the run’s event stream, letting you:
  • inject logic before and after the whole run (auth, logging, monitoring);
  • intercept, rewrite, or inject events produced during the run;
  • build control logic such as retries on top of that.
Last modified on September 19, 2026