Benji Barash (@BBarash) header
Benji Barash (@BBarash) profile picture

Founder and CEO @roboto_ai šŸ¤–šŸ’« Previously made robots @amazon @allen_ai

Seattle, WA
Joined July 2008
Photo by Benji Barash (@BBarash)Photo by Benji Barash (@BBarash)Photo by Benji Barash (@BBarash)Photo by Benji Barash (@BBarash)Photo by Benji Barash (@BBarash)Photo by Benji Barash (@BBarash)Photo by Benji Barash (@BBarash)Photo by Benji Barash (@BBarash)Photo by Benji Barash (@BBarash)Photo by Benji Barash (@BBarash)
There's incredible progress in Physical AI right now - almost weekly, a company (read: research lab) announces general capabilities across a wide range of tasks. A few are already testing in meaningful-scale deployments, but most are still in controlled lab environments. Forgiving use cases (the kind that won't kill someone or break something) get to learn in public. The hope is these models generalize to complex scenarios in the wild; the reality is the long tail. Even LLMs still make mistakes, let alone models that have learned physics - or some approximation of it. If you talk to robotics engineers, less determinism isn't usually on their wish list - and it's already hard enough to reproduce failures on existing robotic systems. As the black boxes get bigger, so does the need to see inside them. The teams taking this seriously will be the ones that scale.
2
4
106
So cool to see how our users are leveraging AI Chat to analyze their robot logs. Here are a few prompts from last week: - ā€œTake a look at some recent successful missions and tell me if they contain a mid-flight error or warningā€ - ā€œI'm looking for issues with USB host controller resets - especially when they happen relative to software version or hours of continuous operationā€ - ā€œIs there a collision involving the robot arms in this dataset?ā€ - ā€œShow me fault occurrences at customer sites over timeā€ - ā€œA customer reports that over long distances the robot makes a sharp rotation before correcting itself. Do you see any issues that would explain this?ā€ A few months ago, each of these questions could have meant hours or even days of digging through multimodal logs. Now they're often answered in minutes. Hearing from users about how much time they're saving (and customers they’re helping) has been one of the most rewarding parts of building @roboto_ai. If robotics teams can finally iterate at this kind of speed, I think we'll see a huge improvement in reliability and uptime across the industry - and hopefully much larger fleets.
2
7
150
šŸ” Today we're launching root cause analysis in @roboto_ai Roboto Agents now debug across your robot data and your codebase, tracing a failure from your logs to the exact code that caused it - and even drafting a fix. A triage label tells you what failed. Root cause analysis figures out why. That's always been the hard part. Knowing a run hit a localization failure is just the starting point. The explanation is buried somewhere across the telemetry, source code, configuration, and engineering context. That's why debugging often takes days and pulls in multiple people. An agent that only reads your robot logs can tell you what happened. To explain why it happened, it needs the same context your engineers do. Now it has both. Roboto Agents follow the evidence from your robot data into your codebase, test hypotheses against real runs, and come back with the most likely cause, the evidence behind it, and even a proposed fix to review. Instead of spending days bouncing between logs, plots, source code, and teammates, you can get straight to understanding what changed.
5
4
1
27
4,066
Ask a question about a robot run, and watch the agent build the answer and pull up the data for you. That's live in @roboto_ai today. The agent can drive the visualizer now, too. Debugging a robot log in a visualizer used to mean driving it yourself. Hunt for the right topics, plot them one at a time, scrub the video, then start over on the next analysis. Now you can just ask: "Look at the IMU and the front camera and show me any unusual movements." The agent analyzes both the time-series and video, then takes you straight to the moment that matters. The best part is that it's still the same visualizer underneath. You're not locked into a chat response or a static report. Ask a follow-up. Add another topic. Keep exploring. When interacting with robot data becomes this easy, engineers naturally ask more questions. You check the hunch you would've ignored. You compare runs you wouldn't have had time to compare before. And it's not limited to a single run. Point the same conversation at your robot's entire history and ask whether you're looking at one-off behavior or a fleet-wide pattern. This morning we launched Agentic Triage - the first pass over every robot run. This is what happens when you want to go deeper. Part 2 of Day 2 at Agent Week is live now. @OpenRoboticsOrg @PX4Autopilot #Robotics #PhysicalAI #Agents #Analysis
7
3
11
919
šŸš€ Today we're launching agentic triage in @roboto_ai. Roboto Agents can now review every robot log the moment it arrives and open labeled issues in #Jira, #Linear or #GitLab with supporting evidence attached. It’s the first line of defense that every #robotics team needs. Failure modes and anomalies are detected automatically. The runs that warrant escalation get surfaced. You can spend more time improving your system instead of debugging the same issue for the fifth time. Robotics teams often underestimate how high the support burden will be once they start putting robots into the field. A robot that's 99% reliable sounds great until you deploy 100 of them. Suddenly you're dealing with failures every day. The statistics catch up quickly. Tomorrow’s issues are already sitting in today’s logs - but nobody has time to review them. So you wait for a customer to complain instead. That’s a huge business risk. Agentic triage gives you the tools to find issues before your customers do. We’ve been testing this with select engineering and field support teams collecting #ROS bags, #MCAP and #PX4 ULG files over the past few months. They think it rocks, and they’ve discovered and fixed some surprising issues before anyone noticed. Today is day 2 of #AgentWeek, and it's live now. If you want to try agentic triage on your own data, reach out or check out our blog post below. #PhysicalAI #Triage #Agents @OpenRoboticsOrg @PX4Autopilot @NVIDIARobotics
3
7
1
20
1,290
Today we're launching Roboto Agents - AI that turns every robot run into a faster learning loop. Since late last year, our team has been working on a new way for robotics teams to analyze the massive amounts of data their robots generate. Every robotics team hits the same wall: you generate far more data than you can analyze. Most of it goes ignored, and the lessons buried in those runs never make it back into the robot. That's the problem we built Roboto Agents to solve. Instead of analyzing runs one at a time in a visualizer, you can just describe what you want to accomplish: "Review these logs for any anomalous behavior." "Investigate why this vehicle stopped during takeoff." "Which software and hardware versions have this issue across the fleet?" "Highlight all grasping failures and put them in a collection." Agents do the work and show you the evidence behind their findings. The faster you learn from every run, the faster your robots get reliable. That's the learning loop that separates the teams that successfully scale Physical AI. The best part: this isn't just a vision for the future. Robotics teams have been using Roboto Agents in production for months to investigate issues, find patterns, and build better datasets. A huge thank you to the teams who trusted us early, and to everyone at Roboto who made this launch possible. This week we'll share how Agents accelerate triage, root cause analysis, and data curation. #Robotics #PhysicalAI #Data #Agents
10
6
1
17
2,057
An important lesson from my time at Amazon Robotics: a single log tells you what happened. But the real value comes from the corpus of historical logs you build over time. We had years of robotics data. But when a robot failed, we still struggled to answer the question every engineer asks: have we seen this before? This is why I'm so excited about AI agents in robotics. Not because they replace infrastructure, but because they finally unlock it. An agent can take the anomaly you're investigating today and get you to answers: Have we seen this before? What changed beforehand? Which robots are affected? But an agent is only as good as the tools and infrastructure available to it. The better your robotics data is organized, indexed, and made searchable, the more effective the agent becomes. Agents don't replace the foundation - they leverage it. Agent Week at @roboto_ai is almost here šŸ‘€ #Robotics #Data #Agents #PhysicalAI
2
1
1
2
295
šŸŽ‰ Boom: @roboto_ai has been named one of the Most Innovative Robotics Companies for the second year in a row! This year’s recognition highlights the work we’ve been doing to automate robotics data analysis with AI agents - helping teams automatically triage, curate, investigate, and understand robotics logs. We've been amazed by the results our customers are already seeing. Special thanks to @therobotreport for spotlighting the innovation happening across the industry right now. We’re honored to be included alongside companies like @amazon, @ChefRobotics, @createme, @GoogleDeepMind, @huggingface, @NVIDIARobotics, @physical_int, @Waymo and others pushing the frontier of Physical AI. Can’t wait to pick up our award at the Robotics Summit & Expo in 2 weeks. Let me know if you're going! #RBR50 #Robotics #PhysicalAI #Data #Agents
1
2
6
301
Our team at @roboto_ai is super excited to be in the Physical AI Fellowship so we can automate data analysis at every robotics company! šŸ¤–šŸ¦¾
Meet the next wave of robotics startups. šŸ¤– The AWS x @MassRobotics Fellowship cohort is advancing real-world robotics across agriculture, manufacturing, humanoids and beyond. From autonomous farming to AI-driven automation, #NVIDIAInception members @burro_ai, @config_inc, Deltia, @HaplyRobotics, Luminous Robotics, @roboto_ai, Telexistence, Terra Robotics, and WiRobotics are shaping the future of physical AI. šŸ“– nvda.ws/3O2SBSL #NationalRoboticsWeek
1
1
2
229
We’re entering a new era of robotics data analysis. This agent in @roboto_ai is working through bimanual manipulation (grasping) data - automatically pulling out the moments that matter. #PhysicalAI #Robotics
1
4
173
AI agents can now debug robotics data for you. In October at #ROSCon and November at #PX4 Dev Summit, I demoed an AI agent debugging a robot log end-to-end for the first time. I got a healthy mixture of excitement and skepticism from the audiences. Back then, ā€œagentsā€ was still a term mostly being used by AI investors, but internally the results had surprised us enough to start testing with customers. Since then, foundation models have gone through another step change in capability. For several decades in robotics, the debugging loop has been the same. A robot fails, you pull the logs, replay sensor data, and spend hours trying to figure out what happened. While you’re doing that, another robot fails for a different reason. This has quietly been one of the biggest bottlenecks holding the industry back. If your robots are constantly failing and it takes hours to investigate each issue, you can’t scale up your deployments. At @roboto_ai, we've been building the foundation to change this. Instead of manually digging through logs, you can ask what happened and have the system investigate, explain, and pull up the relevant data. I recorded a short video of me debugging a PX4 Autopilot drone flight using our new AI Chat interface. Customers are already using this to automate review and integrate with their internal systems. We think this will finally let robotics teams scale the way software teams do. #robotics #data #agents #ros #px4
2
1
9
351
Robotics is absolutely having a moment, but flashy demos don’t automatically turn into fleets that scale. I was on @NYSE Live with @KristenScholer last week, and we dug into this as part of their #CES coverage. One of the toughest challenges in robotics today is going from a few robots to a large fleet. You might have never noticed a problem that shows up once in a thousand missions. But as soon as you have a fleet of 100 robots, it might start happening multiple times a day. The long tail of bugs and edge cases quickly adds up, and finding them is painful and expensive. If the industry can’t figure this out, #robotics will continue to struggle. This is why we’re building @roboto_ai We’re helping teams automate analysis of their robotics data so they can catch issues before their customers do, and scale up their fleets with confidence. Let's make 2026 the year of real fleets!
3
6
4,015
Just wrapped up my talk at #ROSCon in Singapore! šŸ‡øšŸ‡¬ Robotics teams are drowning in logs - the real challenge is finding the important events hidden inside! #Robotics #ROS #AI #RoboticsData
1
1
1
4
636
I showed tools we're building at @roboto_ai to help: 1ļøāƒ£ Signal similarity search for pattern detection 2ļøāƒ£ Vision-language models for event annotation 3ļøāƒ£ AI summarization for faster triage And a sneak peek of an AI agent that debugs robot logs on its own šŸ¤– @OpenRoboticsOrg
1
3
237
Replying to @IlirAliu_
@IlirAliu_ hit the nail on the head here, recommended reading for anyone in robotics🧵
Every robot you see is a data firehose generating terabytes of chaos. This hidden crisis is the #1 reason robots fail, and it's costing the industry billions. You see hardware, but not the data swamp drowning engineers. In 2025, a quiet revolution is fixing it. Here’s how. 🧵
1
1
7
1,362
I can always tell when someone sends me #ChatGPT text because of how many em dashes there are—every sentence—one after another—like it’s afraid of periods. I don’t even know how to type one myself…
1
1
2
183
Super cool presentation on visual anagrams from @dangengdg at #CVPR2024 - see examples: dangeng.github.io/visual_ana…
1
14
86
8,971
Exciting to see @scale_AI getting into the FM scene with AFM-1. Curation is a great use case, but note the disclaimer re: not trusting black boxes: ā€œAFM-1 is not built for direct consumption of inferences for safety critical applications in autonomous vehicles.ā€
Scale is excited to launch our Automotive Foundation Model, AFM-1: a state-of-the-art, language-grounded, perception model to accelerate the development of autonomous vehicles! 🧵 scl.ai/afm-blog
1
1
449
Feature request for @github — automatically suggest fixes for open issues and PR comments #Copilot #GPT
1
141
I had a blast presenting at #ROSCon in New Orleans! My talk focused on how robotics teams can survive the flood of sensor data and what we're building to help. Check it out: lnkd.in/geCcRUGt @roboto_ai @rosorg #ros #ros2 #robotics
2
1
10
1,039
Thanks to our incredible investors @Unusual_VC for partnering with us on this journey!
Amazing things are happening with AI + robotics. And @roboto_ai is at the center of it all. Learn about the insights and experience from Co-Founders @BBarash and Yves Albers-Schoenberg that led to this startup, and why we led their Seed. bit.ly/40Z0tFO
3
1
14
922