Runtime

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:

from veadk import Agent

agent = Agent(name="assistant")  # uses the ADK runtime by default

Switch the execution backend

Use runtime to select the inner-loop execution backend: Install the Codex Python SDK before selecting the Codex runtime:

pip install openai-codex

The Codex runtime may execute commands and access files according to the Codex SDK policy. Run trusted tasks in an isolated environment and restrict the credentials and data available to the process. VeADK 1.0.0 does not override the SDK defaults for sandboxing, network access, or review.

agent = Agent(name="assistant", runtime="codex")

Value	Description
`adk` (default)	Google ADK’s built-in execution flow; suitable for most cases.
`codex`	Runs the agent’s inner loop with the Codex SDK; requires `openai-codex`.

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:

from veadk import Agent
from veadk.integrations.ve_identity import AuthRequestProcessor

agent = Agent(name="assistant", run_processor=AuthRequestProcessor())

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.

from veadk.processors.base_run_processor import BaseRunProcessor

class LoggingProcessor(BaseRunProcessor):
    def process_run(self, runner, message, **kwargs):
        def decorator(event_generator):
            async def wrapper():
                # Before: record start, validate, ...
                async for event in event_generator():
                    yield event  # intercept or rewrite events here
                # After: summarize, report, ...
            return wrapper
        return decorator

Overview

Get started

Core components

Observability

Extensions

Frontend

Security

Default runtime

Switch the execution backend

Request processing

Custom processors

​Default runtime

​Switch the execution backend

​Request processing

​Custom processors

Default runtime

Switch the execution backend

Request processing

Custom processors