openEuler

An open source OS run by the OpenAtom Foundation, bolstered by diverse computing, and committed to a sustainable future.

[openEuler @openEuler]

WE WANT YOU. ON STAGE. 🎤
2026.04.25 | Changsha, China
#openEuler Developer Day 2026
We're looking for the boldest technical speeches, posters, and demos to feature live at our annual gathering.
✨ If you're ready to participate in person, DM us to get involved.

[openEuler @openEuler]

Learn more: https://t.co/4AxQbSh19x

[openEuler @openEuler]

Deployment knowledge shouldn't live in scattered documents and scripts.
oeDeploy turns deployment intent into executable workflows through reusable plugins, MCP services, and LLM-powered automation.
Build once. Share everywhere. Deploy consistently.
#openEuler #openEulerBasics

[openEuler @openEuler]

Environment ready? Workflow mastered?
Now it's time to teach your AI agents how IB-Robot works.
In this tutorial, you'll learn how to enable IB-Robot's built-in AI agent skills, helping AI tools understand your project structure and development workflow.
Dive in 👇

[openEuler @openEuler]

PatchFlow Agent is already handling real vulnerability maintenance in openEuler.
✅Finding patches.
✅Analyzing branches.
✅Backporting changes.
✅Creating PRs.
The next step?
Bringing AI agents closer to developers.
PolyMind. Next generation. Coming this June.

[openEuler @openEuler]

For more about IB-Robot: https://t.co/Fp02eKe4iy

[openEuler @openEuler]

Environment ready? Time to start building.
In this IB-Robot tutorial, we walk through the daily development workflow: load → configure → build.
Follow the tutorial and get ready for the next step in the IB-Robot journey.

[openEuler @openEuler]

Can't wait for the next IB-Robot tutorials? 👀
Jump into the repo and explore more here: https://t.co/Fp02eKe4iy

[openEuler @openEuler]

Cloned IB-Robot… now what?
Get started with our first-time setup guide — just one script and you're ready for simulation, training, and real robots.
Dive in and start your IB-Robot journey here 👇

[openEuler @openEuler]

AI policies can output actions.
Real robots still need a runtime.

IB-Robot on openEuler Embedded connects AI workflows with ROS 2 runtime paths: contracts, robot_config, action_dispatch, simulation, and real hardware demos.

Watch the 59s walkthrough ↓

[openEuler @openEuler]

robot_config bridges sim ↔ real.
Define joints, controller modes, and sensor extrinsics in a single YAML configuration,
with one-click switching between simulation and real-world deployment.

[openEuler @openEuler]

OpenClaw gives robots an AI-native interface.
IB-Robot turns that interface into real-world execution.
From natural language interaction
to ROS 2 actions, VLA inference, and physical robot motion.
👉https://t.co/2ZClHibcDl

[openEuler @openEuler]

Action Dispatch bridges policy ↔ motion.
High-level embodied policies connect directly into ACT execution flows and MoveIt 2 motion planning pipelines.
Reasoning becomes executable robot behavior.

[openEuler @openEuler]

6/ That's the practical point:
less one-off glue code, more reusable runtime structure.
From policy output to robot runtime.
#openEulerforOT

[openEuler @openEuler]

1/ Your policy runs.
Your robot still doesn’t.
Between a trained robot policy and a working ROS 2 system, there’s a lot of runtime glue: data formats, timing, control paths, deployment structure.
That's the gap IB-Robot is trying to reduce.

[openEuler @openEuler]

5/ Fourth gap: deployment.
A Python script can prove the idea.
But a robot system needs ROS 2 nodes, launch files, configs, and runtime structure.
IB-Robot maps:
scripts → ROS 2 nodes
through robot_config.