Google debuts Code as Policies, a tool that uses AI models to generate code for robots to perform a variety of tasks, under an open-source license on GitHub
Google LLC today debuted an internally developed software tool that can reduce the amount of effort involved in training a robot to perform new tasks.
Context & Ripple Effects
Code as Policies extends a habit Google established years ago when DeepMind released its entire AI training platform on GitHub: ship frontier AI tooling as open source to seed an ecosystem around it. The difference here is the output — instead of giving researchers a training platform, Google is handing developers a generator that turns model outputs into executable robot behavior.
The move also reads as an early marker in Google's broader shift toward AI-written code. The company has since reported that 75% of new code created inside Google is generated by AI and reviewed by human engineers, up from half the prior fall, while shipping agent tooling like Jules, the autonomous bug-fixing assistant built on Gemini 2.0. Code as Policies applies that same 'model writes the program' idea to physical machines.
First-order effects
- Robotics developers get a free, inspectable alternative to hand-writing task-specific control code, lowering the effort of teaching robots new tasks — and every improvement lands on GitHub rather than inside a proprietary stack.
- Google positions itself as the default starting point for language-model-driven robot programming, the same ecosystem-seeding role its DeepMind platform played for researchers.
Second-order effects
- Rivals building robot software stacks face pressure to match an open-source baseline: charging for basic natural-language-to-behavior generation gets harder when Google gives it away.
- GitHub gains another high-profile repository that funnels robotics work through its platform, reinforcing its pull as the distribution layer for Google's AI tooling alongside its own Copilot agent features.
Third-order effects
- If the pattern holds, robot programming migrates from specialist engineers writing control code toward operators specifying tasks in natural language and letting models emit the policy — collapsing a labor category into prompt-and-review work, mirroring what Google reports happening to its own internal codebase.
- Open-source release shifts the battleground from who owns the generator to who controls the surrounding stack — simulation, safety validation, and fleet management become where vendors differentiate once the core code-generation layer is commoditized.
The trend: Google is moving from open-sourcing AI research platforms to open-sourcing tools that let AI models write operational code directly — for software agents first, and now for robots.