What if your IDE actually understood the robot you're building?
I described one in plain language and watched it get engineered, in front of me, in a single window.
@pyroscli isn't autocomplete for robotics. It's an IDE that runs the entire robotics engineering pipeline.
It designs the morphology / generates the geometry and inertias / solves and validates the kinematics / sizes the actuators / shows live torque budgets per joint / plans a feasible motion / tunes the controller and simulates.
Every dimension / torque / mass and trajectory comes from deterministic engineering tools with traceable sources not language-model guesses.
In this tour, you'll watch a plain-language spec become a moving robot / the 3D model / the math and the simulation updating together as the pipeline runs.
The goal isn't another URDF that looks correct.
The goal is a robot that's mechanically consistent, mathematically verified, and ready to build without leaving your editor.
Natural language in. Verified robot out.
What if building a robot was as simple as describing it?
I typed a single sentence: "Build a quadruped robot that walks a figure 8."
Everything else was engineered automatically.
@pyroscli doesn't just generate robot code. It executes the entire robotics engineering pipeline.
It designs the robot's morphology / generates the geometry and inertias / solves and validates the kinematics / sizes the actuators / plans a dynamically feasible gait / tunes the controller and runs the simulation.
Every dimension / torque / mass and trajectory comes from deterministic engineering tools with traceable sources not language-model guesses.
In this demo, you'll watch the robot assemble in real time as the engineering pipeline executes, then immediately begin walking a smooth figure-8 trajectory.
The goal isn't to produce another URDF that looks correct.
The goal is to produce a robot that is mechanically consistent, mathematically verified, and ready to build.
Natural language in. Verified robot out.
Pyros retweeted
Day 1 of what's happening at (@pyroscli ) .
So we are building pyros for 2 months now : One interface / You talk / Your robot gets built.
Already had 500 + downloads of our npm package that we have given access only to closed private groups . And the response we are getting is amazing !!
So what pyros actually does ?
It is built around ROS 2, simulation tools like Gazebo and MuJoCo, workspace diagnostics, robot generation, code editing, migration, and debugging.
It can be used from multiple entry points:
- CLI using pyros
- Interactive TUI
- MCP server using pyros-mcp
- FastAPI HTTP API using pyros serve
- CI pipeline using pyros ci
- Autonomous workflow using pyros run
What we have implemented today is just crazy :
Today, we integrated the optional LLM layer into Pyros.
This means Pyros can now use models like OpenAI or Anthropic to understand
user goals / explain logs / generate robot specs / summarize reports and assist with debugging.
This is the important part:
The LLM is not replacing the robotics logic. Pyros still relies on structured, deterministic robotics engines underneath. The LLM simply helps make the workflow more natural / faster / easier to use.
If you wanna use it , drop a message / dm . And hit up a follow , so that when we do something crazy at pyros , you should hear it first .
And join the waitlist : (getpyros.com) 馃
Pyros retweeted
Just deployed @pyroscli on @eigencloud 's TEE infrastructure
Hardware-isolated execution with cryptographic attestation to your robotics AI agent, now verifiably secure
Thanks to @zeeshan_utd for getting us onboarded
The wait is finally over.
We鈥檙e opening early access for @pyroscli , an AI agent that lets you control and build robots from the terminal.
V1 drops next week | Early users get free access
If you're into robotics or automation , this is for you.
Join the waitlist : getpyros.com
Pyros retweeted
well well @pyroscli . Big update coming soon 馃嚠馃嚦









