Migrate to ADK 2.0

[Ivan2125]

What is your feature suggestion?

Description

With the release of ADK 2.0 (introducing the graph-based Workflow API, nodes, edges, etc.), we would like to inquire about the roadmap for agents-cli to fully adopt ADK 2.0.0+ as a first-class, stable citizen.

Currently, agents-cli treats ADK 2.0 as an experimental, opt-in feature documented in references/adk-2.0.md. However, the toolchain's internal templates and lockfiles actively restrict google-adk to <2.0.0.

Current Limitations & Obstacles

1. Scaffolding and Lockfile Restrictions:
   Analyzing the internal files of agents-cli (v0.2.0), the templates and uv lockfiles restrict google-adk strictly to 1.x:

   • scaffold/base_templates/python/pyproject.toml defines "google-adk[eval]>=1.15.0,<2.0.0".
   • Pre-generated lockfiles (uv-adk-agent_runtime.lock, uv-agentic_rag-cloud_run.lock, etc.) have google-adk pinned to <2.0.0.
   • Running agents-cli scaffold create always defaults to an ADK 1.x architecture.

2. Upgrade & Synchronization Conflicts:
   If a developer manually updates their local pyproject.toml to use google-adk>=2.0.0,<3.0.0, commands like agents-cli scaffold upgrade or running background environment syncs risk reverting or causing conflicts with the CLI's internal lockfiles and assumptions.

3. Workflow Support in Local Tooling:
   Commands like agents-cli playground and agents-cli run expect root_agent to behave like a standard ADK 1.x agent. There is no native path/scaffolding option for deploying or evaluating graph-based Workflow objects cleanly without manual scaffolding adjustments (like handling google.adk.workflow).

Proposed Enhancements

We would love to know if the following are planned:

• First-Class Scaffolding Option: Support a workflow flag or a specific template during creation, e.g., agents-cli scaffold create --template workflow or agents-cli scaffold create --adk-version 2.0.
• Updated Dependency Boundaries: Update base templates and lockfiles to support google-adk>=2.0.0 natively as the default or through a stable CLI release flag.
• Better Integration for Workflows: Ensure agents-cli playground, agents-cli run, agents-cli eval run, and agents-cli deploy fully support and auto-detect a Workflow object assigned to root_agent.

What will this enable you to do?

This will enable developers to:

1. Scaffold and build complex graph-based agents (using the new ADK 2.0 Workflow API with nodes, edges, parallel fan-out/fan-in, and human-in-the-loop steps) out-of-the-box using standard agents-cli scaffold create commands.
2. Develop, test, and deploy ADK 2.0 applications seamlessly using the CLI’s core developer experience tools (agents-cli run, agents-cli playground, agents-cli eval run, and agents-cli deploy) without having to manually patch pyproject.toml dependency boundaries or bypass version-locked uv.lock environments.
3. Safely upgrade and maintain projects using agents-cli scaffold upgrade without causing dependency resolution errors due to conflicting internal <2.0.0 templates.

Additional context

Additional Context

• CLI Version: 0.2.0
• Local Python Version: >=3.11

[sushicw]

Thanks for writing! ADK 2.0 support (and making it the default) is something we are actively working on.