Released on GitHub on October 29, 2026, Autoware 2.0 adds AI planning alongside the rule based stack; users can choose a planner at launch, but the proposed trajectory selector does not yet run in version 2.0.0. The release also introduces versioned AI model distribution, the Autoware Index and a Reference Design fr...
Published byEdited with GPT-6 LunaImages generated with GPT Image 2
Research answer

Create a landscape editorial hero image for this Studio Global article: What does Autoware 2.0, released on GitHub on October 29, 2026, introduce to the Autoware Foundation’s open-source autonomous-driving softwa. Article summary: Autoware 2.0’s central change is to add learned AI planning alongside—not replace—the existing rule-based autonomous-driving stack, using a generator–selector trajectory architecture. The available evidence supports that. Topic tags: general, general web, user generated, documentation. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks,
Autoware 2.0 is an architectural step toward AI-enabled autonomous driving, not a wholesale replacement of the project’s existing rule-based software. Its GitHub release on October 29, 2026 adds AI planning and tools for managing models and assembling systems, while the rule-based stack remains the default in version 2.0.0.
The release introduces a generator–selector architecture. Generators produce candidate vehicle trajectories; a selector is designed to assess those candidates and choose one. The approach is intended to make room for different kinds of planners, including learned ones, alongside conventional rule-based planning.
There is an important distinction between the design and what runs in this release. In Autoware 2.0.0, developers choose a generator at launch: the rule-based planner is the default, and the Diffusion Planner can be selected instead. The documentation says the selector itself does not yet run, so the release should not be described as actively comparing and arbitrating between multiple planners at once.
Autoware 2.0 also changes how AI models are distributed. The Foundation hosts models on Hugging Face, with model versions identified by tags; the release downloads trained models rather than including their training code.
The GitHub release also introduces the Autoware Index and Autoware Reference Design. The Index is presented as a way to discover community packages, while the Reference Design is part of the release’s system-composition tooling. The available release excerpts do not establish every detail of package testing or how deployment profiles map to reproducible software stacks, so those capabilities should not be overstated.
Autoware’s roadmap describes a move from a traditional robotics-based driving stack toward a data-centric, AI-based architecture with end-to-end driving capabilities. That is the direction behind adding learned planning while retaining conventional modules—not evidence that end-to-end autonomy is already complete. 17
The project’s recent release cadence provides context: Autoware 1.8.0 arrived in May 2026, 1.9.0 in July, and 2.0.0 in October. After the GitHub release, the Autoware Foundation published its broader announcement on November 2. TIER IV said it would advance Autoware 2.0 with the Foundation and open-source community; reporting also describes adoption work involving Arm, AWS and Red Hat. 2
Autoware 2.0 makes AI planning an option within an open-source stack that still defaults to rule-based planning. Its architecture and new ecosystem tools create a path for integrating learned models, but the selector’s inactive status in version 2.0.0 matters: this release does not yet demonstrate the proposed multi-generator selection working as a complete system.
Nor does the architecture alone establish safety validation or production deployment. The release marks a shift in design and tooling; evidence of validated behavior and named production programs would be needed to support stronger claims about real-world readiness.
Studio Global AI
This page includes a source-backed answer you can continue inside Studio Global.
Released on GitHub on October 29, 2026, Autoware 2.0 adds AI planning alongside the rule based stack; users can choose a planner at launch, but the proposed trajectory selector does not yet run in version 2.0.0.
Released on GitHub on October 29, 2026, Autoware 2.0 adds AI planning alongside the rule based stack; users can choose a planner at launch, but the proposed trajectory selector does not yet run in version 2.0.0. The release also introduces versioned AI model distribution, the Autoware Index and a Reference Design framework.
Released on GitHub on October 29, 2026, Autoware 2.0 adds AI planning alongside the rule based stack; users can choose a planner at launch, but the proposed trajectory selector does not yet run in version 2.0.0. The release also introduces versioned AI model distribution, the Autoware Index and a Reference Design fr...
Published byEdited with GPT-6 LunaImages generated with GPT Image 2
Research answer

Create a landscape editorial hero image for this Studio Global article: What does Autoware 2.0, released on GitHub on October 29, 2026, introduce to the Autoware Foundation’s open-source autonomous-driving softwa. Article summary: Autoware 2.0’s central change is to add learned AI planning alongside—not replace—the existing rule-based autonomous-driving stack, using a generator–selector trajectory architecture. The available evidence supports that. Topic tags: general, general web, user generated, documentation. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks,
Autoware 2.0 is an architectural step toward AI-enabled autonomous driving, not a wholesale replacement of the project’s existing rule-based software. Its GitHub release on October 29, 2026 adds AI planning and tools for managing models and assembling systems, while the rule-based stack remains the default in version 2.0.0.
The release introduces a generator–selector architecture. Generators produce candidate vehicle trajectories; a selector is designed to assess those candidates and choose one. The approach is intended to make room for different kinds of planners, including learned ones, alongside conventional rule-based planning.
There is an important distinction between the design and what runs in this release. In Autoware 2.0.0, developers choose a generator at launch: the rule-based planner is the default, and the Diffusion Planner can be selected instead. The documentation says the selector itself does not yet run, so the release should not be described as actively comparing and arbitrating between multiple planners at once.
Autoware 2.0 also changes how AI models are distributed. The Foundation hosts models on Hugging Face, with model versions identified by tags; the release downloads trained models rather than including their training code.
The GitHub release also introduces the Autoware Index and Autoware Reference Design. The Index is presented as a way to discover community packages, while the Reference Design is part of the release’s system-composition tooling. The available release excerpts do not establish every detail of package testing or how deployment profiles map to reproducible software stacks, so those capabilities should not be overstated.
Autoware’s roadmap describes a move from a traditional robotics-based driving stack toward a data-centric, AI-based architecture with end-to-end driving capabilities. That is the direction behind adding learned planning while retaining conventional modules—not evidence that end-to-end autonomy is already complete. 17
The project’s recent release cadence provides context: Autoware 1.8.0 arrived in May 2026, 1.9.0 in July, and 2.0.0 in October. After the GitHub release, the Autoware Foundation published its broader announcement on November 2. TIER IV said it would advance Autoware 2.0 with the Foundation and open-source community; reporting also describes adoption work involving Arm, AWS and Red Hat. 2
Autoware 2.0 makes AI planning an option within an open-source stack that still defaults to rule-based planning. Its architecture and new ecosystem tools create a path for integrating learned models, but the selector’s inactive status in version 2.0.0 matters: this release does not yet demonstrate the proposed multi-generator selection working as a complete system.
Nor does the architecture alone establish safety validation or production deployment. The release marks a shift in design and tooling; evidence of validated behavior and named production programs would be needed to support stronger claims about real-world readiness.
Studio Global AI
This page includes a source-backed answer you can continue inside Studio Global.
Released on GitHub on October 29, 2026, Autoware 2.0 adds AI planning alongside the rule based stack; users can choose a planner at launch, but the proposed trajectory selector does not yet run in version 2.0.0.
Released on GitHub on October 29, 2026, Autoware 2.0 adds AI planning alongside the rule based stack; users can choose a planner at launch, but the proposed trajectory selector does not yet run in version 2.0.0. The release also introduces versioned AI model distribution, the Autoware Index and a Reference Design framework.