Treating Robots as Code: Why We Built a Programmable IR for ROS 2

How LinkForge v1.4.0 moves beyond static XML (URDF/SRDF) to bring modern software engineering ergonomics to robotics simulation.

. That was a massive step forward for visual design. But as robots become increasingly modular, and as Embodied AI demands headless, parallel training loops, visual design is no longer enough.

Robotics needs modern software engineering ergonomics.

Today, we are releasing LinkForge v1.4.0, an architectural shift that treats robot descriptions not as static XML files, but as a programmable, physically-validated Intermediate Representation (IR).

Here is why we built it, and how it changes the workflow.

The Problem with "Robots as XML"

URDFs and SRDFs are essentially compiled executables for simulators. They were never meant to be source code.

When you attach a robotic arm to a mobile base by hand, you are manually merging two complex, highly sensitive state machines. You have to:

1. Resolve joint name collisions.


2. Manually shift geometric origins.


3. Merge MoveIt 2 planning groups.


4. Pray you didn't accidentally type a mass of 0.0, which will silently crash Gazebo on launch.

This workflow is brittle, error-prone, and entirely disconnected from modern CI/CD practices.

The Paradigm Shift: Validated Composition

With LinkForge v1.4.0, we introduced a fluent Python API that acts as an Intermediate Representation (IR). You define your parameters once, compose modules programmatically, and compile headlessly to URDF, SRDF, or your chosen simulation target.

Look at the difference between guessing your physics in XML, versus strictly validating them in Python:

📦 Download on PyPI:

https://pypi.org/project/linkforge-core/

Or try it out immediately:

pip install linkforge-core

I would love to hear your thoughts on this architecture! How are you currently managing your URDF/SRDF pipelines, and what pain points do you face when migrating from CAD to Simulation? Let's chat in the comments!