KingNews.online — magazine de tecnología y juego
← Back to cover

Physical intelligence · Agriculture · Industrial robotics

Polybot teaches a robot to harvest tomatoes by watching humans work

2026-09-25 · 9 min read

By Álvaro AbrilCEO de Geniales.co · Director de KingNews.online

Machine translation from Spanish.
Polybot teaches a robot to harvest tomatoes by watching humans work
El brazo robótico de Polybot se aproxima a un racimo dentro de un invernadero. La máquina aprende el proceso a partir de demostraciones humanas, no de una lista exhaustiva de reglas.

The German startup replaces thousands of hand-written instructions with human demonstrations: its robot observes the cut, learns which signals matter, and applies that knowledge across entire greenhouse rows. The commercial goal points to 2027, but the decisive test will be maintaining precision, speed, and care of the fruit throughout real work shifts.

ShareXWhatsAppLinkedInFacebookTelegram

The tomato is not programmed: the work is demonstrated

A greenhouse is not a perfectly repeatable assembly line. Two clusters can have different shapes; leaves hide the cut point; light shifts; the fruit moves when the tool touches it. Resolving every exception with a new rule consumes engineering time and can produce a fragile system.

Polybot is testing another approach. An operator carries out the harvest, and the system records the relationship between what the robot sees and the action performed. According to co-founder Martin Kiefel, the machine receives demonstrations of the movement, but no one needs to explicitly describe what a tomato is. With enough examples, the model learns regularities: the red color, the geometry of the cluster, and the right moment to cut.

This does not mean the robot understands the tomato like a human does. It means it learns an action policy from visual and motor data, rather than relying solely on hand-written conditions. The difference is significant: teaching new examples can be faster than reprogramming an extensive collection of individual cases.

Polybot aprende de demostraciones humanas para cosechar tomates en un invernadero

From a Tomato to Full Rows in Seven Months

The timeline reported by Polybot illustrates the speed of development. Laboratory work began in January 2025. In May, the machine autonomously picked its first tomato in a real greenhouse. By December, the company claimed it could reliably navigate and harvest full rows.

The next planned step is a fully integrated pilot with growers during the summer of 2026. The company aims to deliver the first commercial systems in early 2027. These last two dates are corporate targets, not completed milestones, and will depend on sustained performance outside of a controlled demonstration.

FechaHitoEstado
Enero de 2025Inicio del desarrollo en laboratorioReportado por Polybot
Mayo de 2025Primer tomate recogido autónomamenteDemostración de la empresa
Diciembre de 2025Cosecha de filas completasResultado comunicado por la empresa
Verano de 2026Piloto integrado con productoresObjetivo anunciado
Principios de 2027Primeros sistemas comercialesMeta, todavía por verificar

From the laboratories of Tübingen to the greenhouse

Polybot emerged from the environment of the ELLIS Institute Tübingen and the Max Planck Institute for Intelligent Systems, with support from the Tübingen AI Center and the Cyber Valley network. The initial idea is linked to researcher Wieland Brendel; the founding team includes Martin Kiefel, Claudio Michaelis, Maike Kaufman, and Sebastian Blaes. Georg Martius and Brendel serve as advisors.

In 2025, SPRIND—the German Federal Agency for Disruptive Innovation—awarded the project a seven-month validation contract for approximately 220,000 euros to facilitate the transition from research to business. Upon incorporating as a spin-off in December, the project announced an additional one million euros in support from SPRIND.

Public funding allows for the testing of a technology that combines computer vision, imitation learning, a robotic arm, and a platform that runs on the cart rails already installed in many greenhouses. Leveraging this infrastructure removes a practical barrier: growers would not have to completely overhaul their operations to introduce the machine.

The Tomato Is a Particularly Demanding Industrial Test

Harvesting is not just about locating something red. The machine must approach without knocking into other fruits, identify the correct stem, position the tool, cut, and deposit the cluster without damaging it. It must also distinguish ripeness, operate amid occlusions, and repeat the cycle for hours with an economically acceptable error rate.

Polybot claims to have reached an approximately human speed and aims to increase it by a factor of 1.5. It also envisions related tasks such as plant de-leafing, winding, and tying. There are still not enough public metrics on fruits per hour, percentage of correct cuts, damage caused, human interventions, energy consumption, or availability over a full workday.

The absence of these figures does not invalidate the visible progress, but it does limit what can be concluded. The video shows a concrete capability; a commercial operation will have to demonstrate repeatability, safety, easy maintenance, and an overall cost that is lower than or competitive with manual labor.

Teaching trades could change the economics of automation

Polybot's interest goes beyond tomatoes as a crop. Many tasks were never automated because their volume did not justify months of programming or because the environment changed too much. If an experienced worker can generate data by teaching the process, the cost of adapting a robot to local variations could drop substantially.

The same logic is relevant to short-run manufacturing, logistics sorting, visual inspection, order picking, and warehouse operations. However, these extensions are an interpretation of the potential of learning by demonstration: Polybot has only presented public evidence in agriculture and has not announced commercial deployments in those other sectors.

ÁreaTrabajo candidatoDesafío antes de automatizar
AgriculturaCosecha, poda, deshojado y control de malezasVariabilidad biológica y manipulación delicada
ManufacturaEnsamblajes variables y lotes pequeñosTolerancias, seguridad y control de calidad
LogísticaClasificación y preparación de pedidosObjetos desconocidos y ritmos de operación
InspecciónRecorridos y detección visual de anomalíasFalsos negativos y trazabilidad
AlmacenesManipulación y reposiciónConvivencia segura con personas

Worker knowledge must not disappear inside the model

Learning by observation makes the practical experience of those who know the crop valuable. It also raises questions: who decides which demonstrations are correct, how that knowledge is compensated, what happens when poor practices enter the data, and who is accountable when the system fails.

From Geniales.co and KingNews.online, we see a shift in the interface between humans and machines here. For decades, automating meant translating a trade into formal instructions. Physical intelligence offers another possibility: having the expert demonstrate the work and letting the system extract a strategy. The programmer does not disappear; their role shifts toward data, objectives, validation, boundaries, and safety.

The real leap will not be a robot cutting a bunch in front of a camera. It will be growers without a large robotics team being able to teach it new varieties, greenhouses, and tasks without starting every project from scratch.

What Polybot Would Have to Prove Before 2027

The company has built a compelling narrative and a visible demonstration: learning from humans, rapid progression, and the use of existing agricultural infrastructure. To turn it into a product, it will need to publish or allow verification of data on productivity, damage, error recovery, maintenance, safety, return on investment, and performance across varieties and seasons.

If it passes that test, its greatest contribution may not be a tomato harvester. It could be a method for automation to reach complex tasks where writing out every step was always too slow and costly. In that scenario, the most useful language for programming an industrial robot would simply be showing it how the work is done.

Enlaces

ShareXWhatsAppLinkedInFacebookTelegram

Get KingNews in your inbox

Tech and gaming digest, no noise. Unsubscribe anytime.

Want to send us a news story?

Tell us your story. Our editorial team reviews it and gets back to you.

Would you like to advertise with us?

Write to us and we'll send you ad options and audience data.

More stories