At ROSCon 2026 in Toronto on September 22, NVIDIA released Isaac ROS 5.0, a version of its GPU-accelerated robotics software stack that introduces AI agent workflows for building robot applications. On the same day, Google’s Intrinsic unit open-sourced the core of its industrial robotics platform under an Apache 2.0 license. The following day, Qualcomm announced an agreement to acquire PickNik Robotics, the company behind MoveIt, the most widely used motion planning framework in ROS. Taken together, these three announcements signal that robotics software is entering a new phase — one where AI agents assist with code, open-source infrastructure replaces proprietary stacks, and the major hardware companies are competing to own the developer ecosystem.

In Brief

  • NVIDIA Isaac ROS 5.0, released September 22, 2026, at ROSCon in Toronto, introduces AI agent-ready skills for robotics development, including automated environment setup, model fine-tuning, and manipulation workflow generation
  • The release adds support for ROS 2 Lyrical and Ubuntu 24.04, with a NVIDIA-contributed CUDA buffer backend that enables zero-copy GPU data transport between ROS 2 nodes
  • FoundationPose, NVIDIA’s object pose estimation model, now runs up to 5.5x faster through an agent-ready inference library; pick-and-place is available as a standalone agent-ready skill
  • Google’s Intrinsic open-sourced Intrinsic Core under Apache 2.0, providing ROS-compatible capabilities including real-time control, motion planning, grasp planning, simulation, and camera calibration
  • Qualcomm announced an agreement to acquire PickNik Robotics, longtime steward of MoveIt, with plans to integrate motion planning with its Dragonwing robotics platform and Arduino hardware
  • The announcements reflect a broader shift: robotics software is becoming open, agent-assisted, and tied to specific hardware ecosystems — changing how builders, educators, and startups approach robot development

What Isaac ROS 5.0 Actually Adds

NVIDIA’s Isaac ROS is not a robotics framework itself. It is a collection of GPU-accelerated packages built on top of ROS, the open-source Robot Operating System maintained by the Open Source Robotics Alliance. ROS provides the messaging, tooling, and libraries that underpin much of modern robotics development. Isaac ROS brings NVIDIA’s GPU computing, AI models, and production-ready perception libraries to ROS users. According to NVIDIA, the ROS ecosystem now includes nearly 1.3 million users.

Version 5.0 introduces three categories of capability:

Agent-ready development skills. NVIDIA has packaged common robotics development tasks into reusable “skills” that AI agents can execute. A setup skill automates environment configuration — installing dependencies, preparing build scripts, and configuring Isaac ROS on a developer’s machine. A manipulation skill provides reusable workflows for pick-and-place, object detection, depth estimation, and pose output. A FoundationStereo fine-tuning skill allows an AI agent to adapt a stereo perception model to a developer’s specific cameras and environment, rather than requiring manual parameter tuning.

According to Katie Washabaugh, NVIDIA’s product marketing manager for robotics simulation, the setup skill targets “low-hanging fruit” that “nobody wants to do,” while the manipulation skill tackles “a greenfield area of robotics development” where “there are so many minuscule parts that you need to get right.”

ROS 2 Lyrical support and CUDA acceleration. Isaac ROS 5.0 adds support for ROS 2 Lyrical (the latest ROS distribution) and Ubuntu 24.04. NVIDIA contributed a standard data-handling interface called rosidl::Buffer to ROS 2 Lyrical through the Open Source Robotics Alliance. This interface allows ROS 2 nodes to exchange GPU-resident data through zero-copy transport when conditions allow, eliminating the CPU-memory serialization and copying that can bottleneck GPU-accelerated robotics workloads. CUDA provides a working example backend, available to the entire ROS community.

A technical blog post published the same day demonstrates how an AI agent can use the migrate-node-to-rosidl-buffer skill to audit a CUDA-accelerated ROS 2 node, trace data movement, plan a minimal refactor, and verify that zero-copy GPU transport is enabled — work that would typically require deep expertise in both ROS internals and CUDA memory management.

Faster perception and standalone pick-and-place. FoundationPose, NVIDIA’s foundation model for 6-DoF object pose estimation and tracking, now provides an agent-ready inference library that runs up to 5.5x faster than the previous version. Pick-and-place — the workflow connecting detection, depth estimation, and pose output — is now available as a standalone skill outside the full Isaac ROS stack, giving developers more flexibility.

Intrinsic Core: Google’s Robotics Platform Goes Open Source

Also on September 22, 2026, Intrinsic — the robotics company that joined Google in February 2026 — released Intrinsic Core as an open-source project under the Apache 2.0 license. Available on GitHub, Intrinsic Core provides ROS-compatible capabilities that Intrinsic uses internally for real manufacturing deployments.

What Intrinsic Core includes:

  • Intrinsic Control: A hardware-agnostic real-time control framework that supports sensor-based mid-trajectory adaptation, designed to work with different robot arms, grippers, and sensors without rewriting drivers
  • Pose estimation: Built on NVIDIA FoundationPose, providing 6-DoF pose estimation for 3D parts with built-in integration
  • Motion planning: Auto-generation of collision-free paths, replacing manual joint-by-joint programming
  • Grasp planning: Dynamic gripper adaptation based on real-time sensor feedback
  • Simulation services: Powered by Gazebo, with visualization for debugging and validation
  • Camera calibration: Automated camera alignment and vision system configuration
  • Intrinsic-ROS drivers: Pre-configured drivers for supported robots, grippers, and 3D cameras

Alongside Intrinsic Core, the company released the Open Machine Tending Solution (OMTS), a reference application for CNC machine tending that works with hardware from FANUC and Universal Robots. The OMTS is designed to be customizable: developers can adapt it for different assets and integrate foundation models like NVIDIA FoundationPose.

This is a significant release for industrial robotics. The capabilities Intrinsic has open-sourced — real-time control, motion planning, grasp planning, and pose estimation — are the building blocks that most robotics integrators currently build from scratch or license from proprietary vendors. Making them available under Apache 2.0 lowers the barrier to entry for small teams and startups that cannot afford commercial robotics software platforms.

Qualcomm Acquires PickNik Robotics and MoveIt

On September 23, 2026, Qualcomm Technologies announced an agreement to acquire PickNik Inc., the Boulder-based robotics software company that has been the primary maintainer of MoveIt since 2016. MoveIt is the most widely used motion planning framework in the ROS ecosystem, relied upon by robotics developers for collision-aware path planning, manipulation, and kinematics.

According to Qualcomm’s press release, the acquisition is intended to “advance open robotics, physical AI, and MoveIt integration with Dragonwing robotics platforms and Arduino platforms.” This is notable because Qualcomm acquired Arduino in October 2025 and launched the Ventuno Q edge AI board in August 2026. By bringing MoveIt in-house, Qualcomm is building a vertically integrated robotics stack: Qualcomm silicon running Arduino hardware, with MoveIt providing the motion planning layer.

Qualcomm has stated that MoveIt will remain open-source. For the ROS community, this is the critical question. MoveIt’s open-source status is what made it ubiquitous. If Qualcomm maintains it as a genuinely community-driven project — similar to how NVIDIA contributes rosidl::Buffer upstream to ROS 2 — the acquisition could bring additional resources to MoveIt development. If MoveIt becomes a vehicle for Qualcomm-specific hardware differentiation, the community may fragment.

Why This Matters

These three announcements, occurring within 48 hours of each other, reflect a structural shift in robotics software.

Robotics development is becoming agent-assisted. NVIDIA’s introduction of AI agent skills for robotics development is not a minor feature addition. Robotics has historically been one of the most painful software engineering domains — characterized by complex toolchain setup, hardware-software integration challenges, and long iteration cycles. If AI agents can reliably handle environment setup, model fine-tuning, and routine code migration tasks, the productivity gain for robotics developers could be substantial. The key word is “reliably” — NVIDIA’s skills are early, and their effectiveness in production environments remains to be independently evaluated.

Open source is becoming the default for robotics infrastructure. Intrinsic Core’s release under Apache 2.0 means that the core capabilities for industrial robot manipulation — control, motion planning, grasp planning, pose estimation — are now available without licensing fees. Combined with ROS 2 itself being open-source, this creates a viable path for small teams to build production robotics applications without proprietary software dependencies. For startups and educational institutions, especially in markets where commercial robotics software is prohibitively expensive, this matters.

Hardware companies are competing for the developer ecosystem. NVIDIA, Qualcomm, and Google (through Intrinsic) are all investing in open-source robotics tooling — but each tied to their own hardware or platform interests. NVIDIA’s Isaac ROS is optimized for Jetson. Qualcomm’s acquisition of PickNik points toward Dragonwing and Arduino integration. Intrinsic Core works with ROS but highlights NVIDIA FoundationPose. The competition is healthy for the ecosystem, but developers should understand that the open-source contributions are strategic, not philanthropic.

What This Means for Educators and Makers

For STEAM educators and robotics programs, Isaac ROS 5.0 and Intrinsic Core change the practical landscape in several ways.

First, the barrier to teaching real robotics software is lower. ROS 2 has always been free, but setting up a working ROS environment with perception, motion planning, and simulation has been a semester-long exercise in configuration. NVIDIA’s agent-ready setup skills and Intrinsic Core’s pre-configured capabilities reduce this friction. A course that previously spent weeks on environment setup can spend that time on robotics concepts.

Second, the gap between educational robotics and production robotics is narrowing. Platforms like the open-source Microduck biped robot and the Arduino Ventuno Q already bring real robotics capabilities to educational price points. With Intrinsic Core providing production-grade motion planning and grasp planning as open-source libraries, students can now work with the same tools used in industrial deployments — not simplified educational substitutes.

Third, for programs building on NVIDIA Jetson (as many university robotics labs do), Isaac ROS 5.0’s support for scalable compute from Jetson Orin Nano to Jetson Thor means a single software stack can serve both introductory courses and advanced research projects. Students can start on affordable Orin Nano hardware and move to Thor for thesis-level work without rewriting their code.

Product Builder’s Perspective

For product teams building robotics applications, the ROSCon 2026 announcements warrant three strategic considerations.

Evaluate your hardware-software coupling. Isaac ROS 5.0 is free and open-source, but it is optimized for NVIDIA Jetson. Intrinsic Core is hardware-agnostic in principle, but its FoundationPose integration assumes NVIDIA GPUs. Qualcomm’s MoveIt acquisition signals intent to optimize for Dragonwing. If your product roadmap involves multiple hardware platforms, maintain a clear separation between hardware-agnostic ROS components and hardware-specific acceleration layers. The rosidl::Buffer abstraction is a good model — it provides a standard interface with CUDA as one backend, but the interface itself is hardware-neutral.

Experiment with agent-assisted development now. The productivity gains from AI-assisted robotics development are currently concentrated in setup and configuration tasks. These are exactly the tasks that consume disproportionate time in small teams. Testing NVIDIA’s setup skills or the migrate-node-to-rosidl-buffer skill on a real project will give your team a concrete sense of where agent assistance works and where it falls short. The tools are free and open-source — the cost of experimentation is time.

Watch the Qualcomm-MoveIt integration closely. If you are building on ROS 2 with MoveIt for motion planning, Qualcomm’s acquisition creates both opportunity and risk. Opportunity: MoveIt may receive more engineering resources and tighter integration with affordable hardware (Arduino boards with Qualcomm silicon). Risk: development priorities may shift toward Qualcomm-specific features. If MoveIt is critical to your product, contributing upstream — or at minimum tracking the project’s governance closely — is prudent.

What to Watch Next

  • ROS 2 Lyrical adoption: Isaac ROS 5.0’s support for ROS 2 Lyrical provides a migration path, but the ROS community’s transition from Iron/Jazzy to Lyrical will take time. Watch for adoption patterns and compatibility issues in the coming months.
  • Intrinsic Core community growth: The success of Intrinsic Core depends on community adoption. Watch the GitHub repository for contributor counts, issue activity, and ecosystem integrations beyond the initial launch partners.
  • MoveIt governance post-acquisition: Qualcomm has committed to keeping MoveIt open-source. Watch for any changes to the project’s governance model, contribution process, or technical roadmap after the acquisition closes.
  • Agent skill maturity: NVIDIA’s agent skills are first-generation. Watch for independent evaluations, community-built skills, and benchmarks comparing agent-assisted development to manual workflows.
  • NVIDIA GTC Berlin (October 20-22, 2026): NVIDIA has announced that registration is open for GTC Berlin, where additional robotics announcements are likely.

Conclusion

ROSCon 2026 may mark the point where robotics software development began to look fundamentally different. AI agents are now part of the robotics development workflow — not as a novelty, but as packaged skills for setup, perception tuning, and code migration. The core infrastructure for industrial robotics manipulation is now open-source under permissive licenses. And the hardware companies that shape the ecosystem are competing through open-source contributions rather than proprietary lock-in.

For builders, educators, and startups — especially in markets like Pakistan where access to commercial robotics software has been a barrier — these changes create real opportunities. The tools are free. The documentation is improving. The question is whether the community will adopt and extend them fast enough to realize the potential.

What robotics development tasks would you most want an AI agent to handle? The answer to that question will shape which of these tools succeeds.

Sources