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:
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