1.0.10
VeADK 1.0.10 was released on August 4, 2026. The following table lists its public user-facing changes. See the GitHub Release for the complete commit history.| Module | Change details | Link |
|---|---|---|
| Studio agent directory | The agent directory now switches by agent-type tabs and supports filtering by name. It loads the signed-in user’s runtimes across all regions and automatically loads the next page while scrolling; agent cards are simplified to name and creation time, the connected agent is pinned to the top, and a reload option is available when loading fails. | Studio agent workbench |
| Studio deployment | Build logs are streamed in real time in the deployment progress card during the build stage, with expand, collapse, and copy support; logs are redacted and length-bounded on the server, and build failures append the failure detail. | Studio agent workbench |
| Studio sandbox sessions | When creating a Session or looking up the Tool for built-in agents or Skill creation, Studio first uses the region set by AGENTKIT_SANDBOX_REGION (default cn-beijing); if that region reports the resource as not found, it automatically falls back to the other supported region (Beijing ↔ Shanghai). Other errors do not trigger fallback. | Studio agent workbench |
| Studio deployment | When deploying to AgentKit, the root agent description is automatically normalized to a Runtime-compliant single-line description (at most 255 bytes, with line breaks, control characters, and unsafe symbols removed); the full description is kept in the project. If the normalized description is rejected by Runtime, creation is retried without the description. | Studio agent workbench |
| Studio deployment & debugging | When a build or deployment stage fails, the workspace shows the complete error message returned by the service, expanded by default and copyable. Build errors now render in the same expandable error panel as deployment errors. | Studio agent workbench |
| Studio role-based access | The Manage Agents view and the agent selector now uniformly limit Runtime visibility by the signed-in account role. Administrators see all Runtimes; developers and regular users see only their own. When an administrator browses all Runtimes, the ones they created are marked “Created by me.” | Studio agent workbench |
| Studio test-run MCP endpoints | Test runs now normalize HTTP MCP tool endpoints on generated agents: a URL not ending in /mcp is appended automatically, tool discovery is validated over Streamable HTTP, and a failure returns an error prompting the user to confirm the URL and token; the original URL saved on the canvas is not modified. | Studio agent workbench |
| Studio integration methods | The agent detail page adds an “Integration methods” tab that probes the Runtime for exposed API Server and A2A protocol endpoints, shows the authentication type and API Key (masked by default, revealed on demand), and provides a Python request example for each protocol. | Studio agent workbench |
| Studio drafts | Unpublished agent drafts from custom creation are saved in the current browser and isolated by signed-in user. Drafts show draft and deploying badges in the management list and can be edited or deleted. MCP auth tokens and deployment environment values are not persisted and must be re-entered after a reload. | Studio agent workbench |
| Studio deployment | veadk studio deploy supports STS temporary credentials via the --volcengine-session-token option; the session token is resolved from the option, the VOLCENGINE_SESSION_TOKEN / VOLC_SESSIONTOKEN environment variables, and the session_token field of the [default] profile in ~/.volc/credentials. | Studio agent workbench |
| Knowledge base | The OpenViking knowledge base default resource URI now uses viking://user/<openviking_user_id>/resources/<index>/; a new openviking_user_id parameter and DATABASE_OPENVIKING_USER_ID environment variable isolate resources per application, and KnowledgeBase gains a close() method to release the backend client. | Store knowledge in OpenViking |
| Long-term memory | OpenViking long-term memory adds openviking_user_id as the owner/context (distinct from Runner.user_id, the peer ID), plus a memory_policy parameter and DATABASE_OPENVIKING_MEMORY_POLICY environment variable to override the default memory extraction policy. | Store memory in OpenViking |
| Studio Codex session | The built-in Codex agent conversation adds dedicated session controls: slash commands, model switching, Skill invocation, workspace selection, Codex permissions, action approvals, terminal and browser tools, plus per-turn token usage and conversation history restore. | Studio agent workbench |
| Studio deployment | Creating a new Runtime supports configuring minimum and maximum instance counts; defaults to 1–1 with a prompt to switch to persistent storage when using in-memory short-term memory. A non-default range adds an “Update instance configuration” stage to the deployment progress. | Studio agent workbench |
| Studio sessions | Session listings skip sessions that no longer exist instead of failing the entire list. | Studio agent workbench |
| Studio sandbox sessions | The “Created by” field in sandbox session listings now shows the creator display name (OAuth email or local username) instead of an internal user identifier; it falls back to the internal identifier when no display name is available. | Studio agent workbench |
| Studio error guidance | run_sse failures now distinguish between a missing session and an incompatible Runtime version, offering respective guidance to switch to persistent storage or check the Runtime version. | Studio agent workbench |
| Studio cloud provider | veadk studio and veadk frontend add a --provider option for selecting volcengine (default) or byteplus; selecting BytePlus uses BYTEPLUS_ACCESS_KEY, BYTEPLUS_SECRET_KEY, and the optional BYTEPLUS_SESSION_TOKEN for credentials, with runtime listings defaulting to the region in BYTEPLUS_REGION or ap-southeast-1. | Studio agent workbench · VeADK Frontend |
| Studio smart generation | Generated drafts no longer configure memory, knowledge base, or tracing; these capabilities stay disabled with default backends and can be enabled manually on the canvas after generation. The web_scraper, text_to_speech, and vesearch built-in tools are removed from the selectable set. | Studio agent workbench |
| Studio smart generation | Smart generation now prefers an LLM agent as the root agent instead of always using a sequential orchestrator; an orchestrator is used as the root only when strict workflow control is essential. | Studio agent workbench |
| Studio agent selection | In cloud mode Studio no longer auto-selects the first available agent; users must connect a Runtime before starting a new chat, and starting without a selection prompts them to choose one and opens the management page. | Studio agent workbench |
| Studio agent deletion | A confirmation dialog listing the items to be removed appears before deletion; deleted agents are temporarily hidden from the list, and if the active agent is deleted the selection is cleared and the management page opens. | Studio agent workbench |
| Studio message feedback | Feedback is associated with the Runtime’s actual app name and falls back to the alternate region when the primary region query fails; a “View evaluation cases” button next to the like/dislike controls previews the evaluation sample for the current message. | VeADK Frontend |
| AgentKit integration | The dynamic A2A run endpoint now creates a session automatically when it does not exist, instead of returning 404. | Deploy to AgentKit |
| AgentKit integration | create_agentkit_app adds an optional identity parameter; when supplied, AgentKit verifies and binds the inbound user identity before VeADK Agent or Tool code runs. The /ping health-check endpoint is excluded from identity binding. Using this parameter requires agentkit-sdk-python>=0.8.2. | Deploy to AgentKit |
| Studio new-chat experience | The new-chat mode selector is available to all users, the agent picker moves to the top navigation, temporary session is renamed to built-in agent with Codex selection, and empty inputs show starter prompts. | Studio agent workbench |
| Dev server | The --vite mode of veadk studio and veadk frontend allows http://localhost:5174 as a fallback to port 5173. | Studio agent workbench · VeADK Frontend |
| Studio code-package deployment | Adds an “Add and deploy from a code package” flow for uploading, inspecting, and editing a ZIP project with a root app.py before deployment to AgentKit. Archives are limited to 50 MB and 800 files and undergo path-safety checks. | Studio agent workbench |
| VeADK Frontend | When an SSO session expires during use, users can sign in again in a separate window while preserving edits, and the original action is retried automatically. | VeADK Frontend |
| Studio chat | Replies from a sub-agent are displayed in a dedicated Agent handoff card when the root agent delegates a task. | Studio agent workbench |
| Studio skills | SkillSpace browsing uses server-side Studio credentials, local imports perform lightweight safety validation, full cloud skill packages include scripts, references, and assets when available, and the fixed per-agent skill limit is removed. | Studio agent workbench |
| Codex runtime | Adds the codex optional dependency group and CodexRuntimeConfig; defaults use session-isolated workspaces, the workspace_write sandbox, disabled network access, and denied escalation, while tool, state, authentication, and token-usage events are emitted as standard ADK Events. | Runtime |
| Studio deployment | The VeFaaS Application now uses the selected deployment region together with the Function, API Gateway, and AgentKit resources. | Studio agent workbench |
| Studio agent workspace | Adds a canvas-based multi-agent workspace with Runtime versions and deployment states. Deployed agents can be edited and published as incremented versions on the same Runtime, and cancelling an update leaves the existing Runtime intact. | Studio agent workbench |
| Studio smart generation | Generates a validated recursive agent-configuration draft from a natural-language goal and lists resources the user must supply. Generation replaces the current canvas and consumes tokens. | Studio agent workbench |
| Studio Runtimes | Read-only readiness probes retry while a Runtime starts, private-Runtime failures provide VPC guidance, and Studio connects after deployment while preserving tasks for retry when the Runtime is temporarily unreachable. | Studio agent workbench |
| Studio debugging | Agent details and versions refresh after Runtime creation or update. Generated-agent test processes are limited to 3 per user, and processes left by page refreshes are reclaimed automatically. | Studio agent workbench |
| Studio test runs | A single temporary test run accepts up to 300 project files. | Studio agent workbench |
| Models | The minimum google-adk version required for the Responses API is now 1.34.0. | Models |
| APMPlus tracing | Reasoning content in model output is labeled with the reasoning type to distinguish it from regular text, making it easier to inspect the reasoning process separately in APMPlus. | APMPlus |
| APMPlus tracing | When OpentelemetryTracer initialization detects an existing global TracerProvider, it reuses that provider instead of overriding it and automatically removes APMPlusExporter; a new read-only property apmplus_managed_externally is available to query this state. | Observability overview · APMPlus |
1.0.9
VeADK 1.0.9 was released on July 26, 2026. The following table lists its public user-facing changes. See the GitHub Release for the complete commit history.| Module | Change details | Link |
|---|---|---|
| Long-term memory | Added the TOS ContextBucket backend for managed memory inference and retrieval with per-user_id isolation. | Store memory in TOS ContextBucket |
| Studio knowledge bases | Agent creation now defaults to VikingDB Knowledge, removes the local vector-store option, and can select an existing knowledge-base collection visible to the current account in the Beijing-region default project. | Studio agent workbench |
| Studio remote agents | Remote-agent configuration can select and refresh AgentKit agent centers by region. Remote agents remain available only as sub-agents. | Studio agent workbench |
| Studio message feedback | AgentKit Runtime answers can be rated with like/dislike controls and written idempotently to per-agent evaluation sets. A deterministic fallback is used when the standard set name is reserved but hidden. | VeADK Frontend |
| Studio release and self-update | veadk studio deploy uses the veadk-studio TOS bucket in the deployment region as its release channel by default. Administrators can update the frontend and backend in Studio, and the account menu shows the current system version. | Studio agent workbench |
| Session capability overlays | AgentKit applications can add or remove built-in tools and remote skills for one session without changing the deployed agent. | Deploy to AgentKit · Studio agent workbench |
| Studio agent information | The conversation view adds an agent information rail for the current agent’s description, model, tools, skills, and collaboration topology. | VeADK Frontend |
| Studio creation workbench | Custom creation adds code-execution configuration and resource-picker search, including AGENTKIT_TOOL_ID and AGENTKIT_TOOL_REGION. | Studio agent workbench · Code sandbox |
1.0.8
VeADK 1.0.8 was released on July 23, 2026. The following table lists its public user-facing changes. See the GitHub Release for the complete commit history.| Module | Change details | Link |
|---|---|---|
| Studio remote agents | Custom creation supports remote-agent child nodes configured with an AgentKit agent-center ID, recall count, region, and OpenAPI endpoint. Matching capabilities are discovered for each turn, and a remote agent cannot be the root agent. | Studio agent workbench |
| Studio Runtimes | Runtime connection failures distinguish access denied, Agent Server unreachable, and authentication failure, with corresponding troubleshooting guidance. | Studio agent workbench |
| Studio sessions | Preserves conversation history when sending follow-up messages. Temporary-session and Skill-creation provisioning failures display credential-safe diagnostics for Tool, region, or model-credential problems. | Studio agent workbench |
| Studio deployment credentials | veadk studio deploy resolves credentials from command options, VOLCENGINE_ACCESS_KEY / VOLCENGINE_SECRET_KEY, then the [default] profile in ~/.volc/credentials. | Studio agent workbench |
| Studio deployment resources | Shanghai deployments keep the Function, API Gateway, AgentKit CodeEnv Tools, and sessions in consistent regions. Temporary-session and Skill-creation model credentials are configured on their Tools, while the VeFaaS Function receives only Tool IDs. | Studio agent workbench |
1.0.7
VeADK 1.0.7 was released on July 23, 2026. The following table lists its public user-facing changes. See the GitHub Release for the complete commit history.| Module | Change details | Link |
|---|---|---|
| Code sandbox | run_code adds bash language support to run shell scripts in the AgentKit sandbox, with exec_dir, env, hard_timeout, and max_output_length parameters that control the working directory, environment variables, hard timeout, and maximum output length. | Code sandbox |
| Studio creation modes | Adds Skill creation across two independent AgentKit CodeEnv sessions; candidates can be compared, downloaded as a ZIP, or published to AgentKit, and the mode is available to developers and admins only. Also adds temporary conversations that are deleted on exit and are not written to normal Studio history. | Studio agent workbench |
| Studio smart search | Adds agent-aware smart search over conversation history, the mounted web-search tool, knowledge base, and long-term memory. Agent metadata advertises mounted sources, and Studio disables unavailable sources. | Studio agent workbench |
| Studio roles and access | Adds --admin and --developer to veadk studio, veadk frontend, and veadk studio deploy. The UI displays the signed-in user’s email, role badge, and OAuth profile picture. | Studio agent workbench |
| Studio update command | Adds veadk studio update --vefaas-app-name <name>, which rebuilds Studio from a local VeADK checkout while preserving the existing URL, SSO, IAM role, gateway, environment variables, title, and logo. When --region and --project are omitted, it searches Beijing and Shanghai across all visible projects. | Studio agent workbench |
| Studio deployment | veadk studio deploy automatically creates the two AgentKit CodeEnv Tools used by temporary chats and Skill creation; existing Tool IDs can be supplied with --sandbox-chat-codex-tool-id and --sandbox-skill-creator-tool-id. After deployment, client sign-in skips repeated OAuth consent. | Studio agent workbench |
| Feishu channel | FeishuChannelExtension can fetch thread history and quoted messages through the Feishu OpenAPI, using include_parent_message, include_thread_history, and thread_history_limit, and prepends the quoted or thread content to the inbound message. | Feishu channel |
| Studio workbench | Refines the custom-creation workbench: local Skills accept folders or ZIP files with automatic format detection; AgentKit Skill Spaces and their Skills can be browsed by region and project; the deployment page shows the agent topology and supports configuration export and source download. It also improves runtime management and responsive layout, new-chat startup, the agent runtime selector, video rendering, and tool-call status display. | Studio agent workbench |
| Dependencies | Relaxes the psycopg2-binary version constraint to >=2.9.10; requires the AgentKit SDK to provide default CORS configuration. | Installation |
1.0.6
VeADK 1.0.6 was released on July 20, 2026. The following table lists its public user-facing changes. See the GitHub Release for the complete commit history.| Module | Change details | Link |
|---|---|---|
| Studio branding | veadk studio and veadk frontend add --site-title (at most 6 characters) and --site-logo (local image or HTTP(S) URL, at most 5 MB; PNG, JPEG, GIF, WebP, AVIF, ICO supported) to set the system name and logo. The logo is used in the sidebar, login page, and browser favicon; the system name also becomes the browser page title. Omitting --site-title keeps the default VeADK Studio. The equivalent environment variables are VEADK_SITE_TITLE and VEADK_SITE_LOGO. Cloud deployment accepts the same options; remote images are downloaded during deployment and bundled into VeFaaS. | Studio agent workbench |
| Studio deployment | veadk studio deploy supports --region to select the deployment region (cn-beijing by default, cn-shanghai); VeFaaS, API Gateway, and other resources are created in the selected region. A new --project selects the VeFaaS function project and defaults to default. Deployment automatically locates the VeIdentity user pool and client across Beijing and Shanghai, emitting a warning and continuing when matched cross-region. | Studio agent workbench |
| Studio deployment IAM | veadk studio deploy checks ServerlessApplicationRole before deployment and creates the role with the vefaas_full_access custom policy and required system policies when it is missing. This check runs even when --iam-role is provided. | Studio agent workbench |
| Studio authoring and debugging | System prompts now support a WYSIWYG Markdown editor with heading and list shortcuts. Initialization, session, and conversation failures show credential-redacted error details and Runner logs that can be expanded and copied. Agent names are validated against Google ADK rules: they must start with an ASCII letter or underscore, contain only ASCII letters, digits, and underscores, cannot use the reserved name user, and must be unique within the Agent tree. | Studio agent workbench |
| AgentKit deployment | Feishu, knowledge-base, short-/long-term memory, and observability settings appear in their respective feature sections; their values are converted to runtime environment variables only during deployment. Selecting an observability exporter also enables the corresponding ENABLE_* flag. These values are not written to generated source or exported YAML; the deployment page mirrors them for review. Multi-instance deployments should use a database-backed short-term memory store; when run_sse returns 404, the UI suggests checking whether an in-memory or SQLite session landed on a different instance. When deploying from the bundled Web UI, cloud image build failures include a credential-safe build-log excerpt so dependency or Dockerfile errors can be diagnosed directly. | Deploy to AgentKit |
| Studio runtime management | Improved the runtime management view and responsive layout. | Studio agent workbench |
| Feishu channel | Toggling the Feishu channel on the deployment page regenerates the project so that app.py, the extensions dependency, and runtime environment variables stay aligned before deployment. | Studio agent workbench |
1.0.5
VeADK 1.0.5 was released on July 19, 2026. The following table lists its public user-facing changes. See the GitHub Release for the complete commit history.| Module | Change details | Link |
|---|---|---|
| Studio and Frontend | Studio now enables the same complete UI as Frontend and opens on the chat view by default. Added cloud Runtime selection, Skill Hub/local upload/AgentKit SkillSpace sources, multimodal conversations, and structured skill and sub-agent invocation. The custom creation flow was redesigned; intelligent, template, and workflow entries are currently marked as coming soon. Also improved deployment regions, environment variables, task status, retry behavior, and OAuth token forwarding. | VeADK Frontend · Studio agent workbench |
| Models | Changed the default inference model to doubao-seed-2-1-pro-260628; Responses API now supports fallback models and Ark context management. | Models |
| Runtime | Added piagent to Agent.runtime, including bridges for function tools, MCP tools, and skills; the package no longer vendors the PiAgent binary. | Runtime |
| Studio testing | Generated agent projects can run in a restricted temporary server-side test process. The process is retained for 1,800 seconds by default and can be adjusted with a command option. | Studio agent workbench |
| Studio deployment | When Studio is deployed with its default IAM role, the command adds the system policies needed to access model, logging, tracing, knowledge, memory, and identity resources. An explicitly supplied custom role is not modified. | Studio agent workbench |
| AgentKit integration | Studio-generated applications now use the public create_agentkit_app function to provide AgentKit endpoints, health checks, topology, the built-in Web UI, and short-term memory defaults. | Deploy to AgentKit |
| Feishu channel | Improved extraction of text, card, and merged-forward messages and added compatibility with the synchronous Channel SDK lifecycle. | Feishu channel |
1.0.4
VeADK 1.0.4 was released on July 14, 2026. The following table lists its public user-facing changes.| Module | Change details | Link |
|---|---|---|
| Studio | Added veadk studio, a focused workbench for agent creation and management. It supports intelligent, custom, and template creation; the workflow entry is marked as coming soon. AgentKit deployment progress is reported by stage. | Studio agent workbench |
| Agent management | Added an AgentKit runtime management view to Frontend and Studio. It lists workbench deployments for the current user, shows Runtime and primary-agent details, and can delete runtimes. | Studio agent workbench |
| VeFaaS deployment | Added veadk studio deploy to deploy Studio to VeFaaS with VeIdentity login and create or reuse a Serverless API Gateway and IAM role. | Studio deployment |
| VeADK Frontend | Added agent topology and transfer-path visualization. Project deployment now reports live build-image, deploy, and publish stages. | VeADK Frontend |
| Harness skills | Harness skills accepts space:<skill-space-id> to load an entire AgentKit skills-center space alongside Skill Hub names or slugs. | Skills |
| Frontend security | Removed the action that directly executed browser-submitted code; restricted the AgentKit proxy protocol, host, and credential requirements; and confined deployment and static-file paths. | VeADK Frontend |
| Logging | Migrated logging to Python’s standard logging package while retaining trace-ID correlation. Non-interactive output no longer contains color escapes, and streaming reasoning is no longer logged token by token. | Application logging |
| Storage configuration | Expanded Milvus and OpenViking environment and configuration examples. Version 1.0.4 continues to provide the Milvus knowledge, OpenViking knowledge, and OpenViking long-term memory backends introduced in 1.0.3. | Milvus · OpenViking knowledge · OpenViking memory |
1.0.3
VeADK 1.0.3 contains the following public user-facing changes.| Module | Change details | Link |
|---|---|---|
| Knowledge base | Added the milvus backend with Milvus service and Milvus Lite URIs, token or username/password authentication, database selection, initialization overwrite, timeout, and additional output fields. | Store knowledge in Milvus |
| Knowledge base | Added the openviking backend for importing files, directories, and text into OpenViking and retrieving and hydrating results by resource URI. | Store knowledge in OpenViking |
| Long-term memory | Added the openviking backend to store per-user entity, event, and preference memory while retaining user isolation across sessions. | Store memory in OpenViking |
| A2A | Calls to downstream agents in the AgentKit A2A Registry can propagate inbound X-Ve-TIP-Token and bearer JWT credentials. If a downstream call made with the inbound JWT returns 401, VeADK can fall back to M2M OAuth2 and retry once. | Inbound authentication |
| Dependencies | Consolidated duplicate dependency declarations, added the OpenViking SDK to the base dependencies, and added Milvus integrations to extensions. | Installation |
1.0.2
VeADK 1.0.2 contains the following public user-facing changes.| Module | Change details | Link |
|---|---|---|
| Models | Added MODEL_AGENT_API_KEY_NAME and Agent.model_api_key_name to resolve an Ark API key by name. An explicit key value still has higher precedence. | Model configuration |
| Short-term memory | Added PostgreSQL schema configuration to isolate session tables for separate deployments in one database. VeADK creates a missing schema and pins the connection’s search_path. | Store sessions in PostgreSQL |
| MCP | After an MCP Server session expires, the service restarts, or the connection drops, VeADK discards the stale session, reconnects, and retries tool discovery or execution once. | Custom MCP Server |
| Frontend | Added a tool OAuth authorization card to VeADK Frontend: it opens the identity provider, accepts the callback, submits the credential, and resumes the original tool call. Also refined the account entry, login page, session list, empty-response notice, and default agent selection. | VeADK Frontend |
| Network requests | VeSearch and web-fetch requests use a 30-second timeout so an unresponsive service does not block indefinitely. | Volcengine search · Web fetch |
| Security | Web fetch verifies TLS certificates, and content-safety debug logs do not record API-key values. | Web fetch · Content-safety guardrail |
1.0.1
VeADK 1.0.1 was released on July 7, 2026. It adds Harness, A2A registration, and ADK skill integration, with updates to the Codex runtime and VeADK Frontend.| Module | Change details | Link |
|---|---|---|
| Codex runtime | Ships sandbox, network, and review defaults that allow full host and network access without interactive approval. | Runtime safety |
| Harness | Adds the VeADK Harness extension to prepare context for each turn, compact large tool results, and verify final answers; Harness initialization also applies the agent description. | Harness plugins |
| A2A | Adds Harness A2A registration and corrects its registration behavior. | Remote-agent discovery |
| A2A | Adds OAuth authentication to A2A calls. | A2A authentication |
| Codex runtime | Adds configurable retries for transient backend errors and restores web search through the Responses shim. | Codex backend requests |
| Skills | Adds VeSkillRegistry for using SkillHub and Skill Space sources with Google ADK SkillToolset; local skills should migrate to ADK SkillToolset, while the legacy Agent(skills=..., skills_mode="local") entry point remains compatible but is deprecated. | Cloud skills |
| VeADK Frontend | Adds gateway authentication mode and a missing-Volcengine-credentials notice during agent creation. | Frontend authentication |
| Codex runtime | Passes agent skills through to the Codex runtime. | Codex skills and tools |
| Codex runtime | Executes an agent’s MCP and function tools through the Codex runtime. | Codex skills and tools |
| Examples | Adds a Codex-runtime example that combines a local skill with an MCP tool. | Codex skills and tools |
1.0.0
VeADK 1.0.0 was released on June 22, 2026. The table follows the public release notes; the published change from 0.5.40 is limited to the documentation entry-point wording.| Module | Change details | Link |
|---|---|---|
| Documentation | Aligned the Chinese quickstart card with the English card so it explicitly says users can build and run their first agent. | Quickstart |