Intrinsic open-sources Intrinsic Core, a ROS-compatible stack for manufacturing workcells
The Apache-2.0 release bundles a real-time control framework, motion and grasp planning, pose estimation and a digital twin, plus an open CNC machine-tending reference design. It targets ROS 2 Lyrical Luth.
Intrinsic has open-sourced Intrinsic Core under the Apache-2.0 licence. Tully Foote announced it on ROS Discourse on 2 November 2026 and wrote that the code had gone public at ROSCon about two weeks earlier. Intrinsic says these are capabilities it already uses in real manufacturing deployments.
The repository README lists the parts. ICON is a real-time control framework with a hardware abstraction layer, meant to let you swap arms and grippers without rewriting drivers, and it can change controllers within one control cycle. A motion planner handles Cartesian and joint-space moves with path blending. A perception module wraps NVIDIA FoundationPose for 6-DoF pose estimation, and an inference service runs models locally. There is also grasp planning, a digital twin and an SDK. The runtime is packaged as a k3s container environment and builds with Bazel and C++.
Intrinsic Core works with ROS through standard workspaces, messages and tools. The README targets ROS 2 Lyrical Luth (LTS, May 2026) on Ubuntu 24.04 or 26.04, with 22.04 also supported. A separate repository holds the Open Machine Tending Solution (OMTS), a reference workcell for loading CNC machines. According to the post, community members have already adapted it to pick and insert car wheels with a custom gripper on a larger robot. Related repositories include a MoveIt 2 integration and a library that catches heap allocations in real-time threads.
Why it matters
For a ROS team building a workcell, this is real-time control, planning and perception that Intrinsic says it runs in production, under a permissive licence. OMTS gives you a complete workcell to study rather than isolated packages. Check the hardware list against your arms before planning around it, and note the Bazel and k3s build, which differs from a standard colcon workspace. Contributions need a signed Google contributor licence agreement.