Default runtime
The ADK runtime is the default and needs no extra configuration:Switch the execution backend
Useruntime to select the inner-loop execution backend:
Install the Codex Python SDK before selecting the Codex runtime:
Skills and tools in the Codex runtime
VeADK 1.0.1 makes skills loaded through ADKSkillToolset or the legacy skills entry point available to the Codex runtime. The runtime can also call an agent’s function and MCP tools:
Codex backend requests
Enable web search
Web search is disabled by default when the Codex runtime calls models through Volcengine Ark. SetCODEX_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 torun_processor, for example to enforce login
via identity authentication:
AuthRequestProcessor as a ready-made implementation for identity authentication.
Custom processors
Every processor subclasses the abstract baseBaseRunProcessor 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.