Skip to main content
veadk web wraps Google ADK’s adk web to launch a visual debugging UI: chat with your agent and observe its execution in the browser, with zero frontend code. Compared with running adk web directly, it adds automatic integration of VeADK memory, warnings for workflow agents, an optional VeIdentity SSO login, and it disables the OpenAPI documentation routes and trims noisy logging by default. It is intended for local development and troubleshooting. veadk web passes the adk web options straight through, so the adk web usage applies here as well. This page documents only the behavior and options that VeADK adds on top of it.

​
Launch

Run the command from the parent folder of your agent directories. Each subdirectory that contains an agent.py exposing a root_agent becomes a selectable app in the UI.
Open the address printed by the command to use it.

​
Common passthrough options

The options below are provided by the underlying adk web and passed through by veadk web unchanged.
The complete set of passthrough options is defined by adk web --help. The table lists the ones most commonly used with this UI.

​
VeADK-specific OAuth2 options

veadk web adds three options for VeIdentity single sign-on. The login middleware is enabled only when both the user pool and client names are supplied.
Enabling SSO requires the process to have access to Volcengine credentials. In this mode the cookie Secure flag is not forced, so it works over plain HTTP for local serving.

​
Automatic memory integration

This is the core enhancement veadk web provides over plain adk web. The command hooks into the ADK web server’s runner acquisition: before a runner is created for an app, it loads the corresponding agent and inspects its memory configuration:
  • If the agent has short-term memory configured, its session service is wired in as the app’s session service.
  • If the agent has long-term memory configured, it is wired in as the app’s memory service, and the long-term memory backend is logged.
As a result, memory configured on the agent works in the UI directly — you do not need to specify a session or memory service on the launch command.
When a workflow agent (Sequential, Loop, Parallel) is detected, the short-term and long-term memory configured on each of its sub-agents individually has no effect, and the command emits a warning in the logs. Configure memory on the workflow agent itself.

​
Disabled OpenAPI and default log level

At startup veadk web makes two adjustments to the ADK web server:
  • Disables the OpenAPI documentation routes. It removes the /openapi.json, /docs, and /redoc routes from the server to simplify the UI and reduce the exposed surface.
  • Trims the default log level. If --log_level is not passed explicitly, the level defaults to ERROR to suppress noisy output from Google ADK and LiteLLM; when --log_level is passed, the provided value is respected.

​
Agent build graph serialization

At startup veadk web adjusts how the ADK dev server serializes the agent build graph. This endpoint powers the agent topology and configuration view in the debugging UI; the original serialization rendered the VeADK agent’s model field as a complex structure containing runtime client objects, which the UI could not parse correctly. After the adjustment, the model field in the build graph JSON is rendered as a provider/model-name string, runtime client objects are removed from the output, and the entire agent tree — including nested sub-agents — serializes correctly.
Last modified on September 19, 2026