TL;DR for operators An embodied assistant may already have seen a room and still fail when asked to place something “to the left of the chair” from a person’s point of view. Supplying more information about where that person is helps less than many teams might expect, because identifying the observer is only one part of the reference-frame problem. ...
TL;DR for operators A familiar robotics design question is where to draw the boundary between understanding and control: should one learned system interpret the scene, choose where to go next, and explain that choice, or should those functions remain distributed across separate perception and planning modules? VISOR1 tests a middle position. Its 3B model combines language understanding, visual-spatial reasoning, target recognition, and high-level destination selection, while a conventional planner handles the low-level movement. It is not the strongest navigator on the leaderboard, but on OVON its post-trained model records a 21.70% success rate on Val Seen and 22.00% on Val Unseen, an unusually small seen-to-unseen change even though stronger baselines achieve much higher absolute success rates. ...
TL;DR for operators The most revealing moment in this study is not that GPT-5.1 moved a robot toward a plush penguin. After the robot struck the target, the model reversed to regain visual perspective, saw that the penguin was still upright, commanded another strike, then reversed again to verify the result. That sequence suggests something more operationally relevant than one-shot visual command generation: the controller retained a task state across several actions, interpreted the likely consequence of a collision, gathered new evidence, and corrected its plan. ...
TL;DR for operators When a historical place name is missing from a gazetteer, the usual workflow treats it as a lookup failure. This paper shows another option: use multiple records that mention the same place from already known coordinates, convert descriptions such as “1 km east of X” into constraints on where X must be, and aggregate those clues. ...
TL;DR for operators A manipulation agent can reach the requested final state and still have executed the task unsafely. That creates a measurement problem for teams using task-completion rates to decide whether an embodied model, prompt, or policy update is ready for deployment. SafeRelBench tests this gap directly. Across seven evaluated VLM-driven agents, the spatial-relation cases produced task Success Rates (SR) of 0.52–0.73 but Safety Success Rates (SSR) of only 0.16–0.40. In matched non-spatial settings, SR rose to 0.83–0.94 and SSR reached as high as 0.91.1 The benchmark therefore measures something final-state success can miss: whether the agent satisfied the relevant safety prerequisite before taking the risky action. ...
Agents are supposed to act. That is the promise hiding behind most enterprise AI demos: the model will not merely answer a question, but inspect a system, choose the next step, correct itself, and reach a useful outcome. The interface changes from chat box to workflow loop, and suddenly everyone starts using the word “agent” with the confidence of a person who has never watched a model get lost in a four-by-four grid. ...
Wall. That is not the grand philosophical frontier AI companies usually place in their product decks. The frontier is supposed to be reasoning, planning, tool use, autonomy, maybe a tasteful diagram with arrows and a glowing robot hand. But in a visually rich 3D world, a surprisingly large part of “autonomy” still reduces to something less glamorous: can the agent notice that it is stuck against a wall, step back, change angle, and continue? ...
Coffee is simple. Parking is annoying. Charging an electric vehicle while also finding a useful nearby stop is where the apparently simple request turns into a small urban planning problem wearing a chatbot costume. A user does not ask for a theorem. They ask something like: “I need to charge my car and grab coffee nearby. Where should I go?” ...
Grid. It looks like the friendliest possible structure. Rows, columns, symbols, rules. No blurry photos, no social nuance, no awkward customer email written at 1:13 a.m. Just a small board and a set of constraints. Naturally, this is where modern reasoning models still manage to embarrass themselves. The paper introducing TopoBench studies a deceptively simple question: can frontier large language models solve topology-heavy grid puzzles where the answer depends on connectivity, loop closure, symmetry, visibility, and state consistency?1 The answer is not “never.” That would be too easy. The answer is more annoying: models often understand enough to start correctly, reason long enough to sound competent, and then lose the structure that makes the solution valid. ...
Geometry looks clean. A cube has edges. A projection has rules. A missing view should follow from the views already shown. This is not the messy world of occluded street scenes, motion blur, shadows, or a warehouse camera pointed at the wrong shelf. It is the kind of visual reasoning many students learn before they are trusted with anything more dangerous than a compass, a ruler, and mild boredom. ...