Загрузка видео...

Не удалось загрузить видео

На главную

Introducing Ego2Web from Google DeepMind and UNC Chapel Hill, accepted to #CVPR2026. AI agents can browse the web. But can they act based on what you see? Existing benchmarks focus only on web interaction while ignoring the real world. Ego2Web bridges egocentric video perception and web execution, enabling agents...

45,924 просмотров • 5 месяцев назад •via X (Twitter)

Комментарии: 8

Фото профиля Shoubin Yu
Shoubin Yu5 месяцев назад

Why do we need Ego2Web? Today’s benchmarks split into two worlds: • Egocentric video → real-world perception & reasoning • Web agents → perception + action, but only in digital environments But real tasks require both seeing something and acting on it. Existing benchmarks miss this connection.

Фото профиля Shoubin Yu
Shoubin Yu5 месяцев назад

What is the Ego2Web task? Given an egocentric video and a natural language instruction. An agent must: 1. Ground visual cues from the video 2. Plan actions 3. Execute steps on real websites Tasks span diverse domains: E-commerce (find/buy items you saw), Media retrieval (find related videos), Knowledge lookup (identify & query entities), Maps/local (locate places from visual cues) Success = completing the web task based on what was seen

Фото профиля Shoubin Yu
Shoubin Yu5 месяцев назад

How do we build and evaluate Ego2Web? We use a hybrid human-model pipeline: • MLLMs → dense video captions → “video profiles” • LLMs → generate grounded web tasks • Humans → verify grounding, feasibility, quality For evaluation, we introduce Ego2WebJudge, an LLM-as-a-Judge that checks if actions align with visual evidence (~84% human agreement).

Фото профиля Shoubin Yu
Shoubin Yu5 месяцев назад

How do current agents perform? We evaluate leading systems (GPT-5.4, Claude, Gemini-based agents, etc.) We find that even the best agent reaches only ~58% success rate, and there is a large gap for improvements, demonstrating that current agents struggle to connect perception and action.

Фото профиля Shoubin Yu
Shoubin Yu5 месяцев назад

What’s hard about Ego2Web? Error analysis reveals key bottlenecks: • 36% object misidentification • 18% temporal misunderstanding • 16% failure to retrieve the correct info • 12% Cross-modal alignment remains fragile Also, we find Raw video >> captions >> no vision, which means perception quality directly drives success. This is still an open problem.

Фото профиля Shoubin Yu
Shoubin Yu5 месяцев назад

Awesome collaboration with @shulindt @AntoineYang2 @Francis_YAO_ Srinivas Sunkara, Maria Wang, @jdchen @mohitban47 @BoqingGo @unc_ai_group @unccs @GoogleDeepMind Check the full paper for more details! ArXiv: Code: Benchmark: Webpage: @huggingface page:

Фото профиля Erika S
Erika S5 месяцев назад

Admittedly I'm not an expert on web agents, but I'm 90% sure this is the missing link. Does it handle German recipe sites with their 47 cookie banners though?

Фото профиля Cross
Cross5 месяцев назад

Connecting egocentric vision with web execution feels like a missing piece. How robust is it in noisy real-world scenarios?

Похожие видео

New Short Course: Building AI Browser Agents! Learn how to build AI agents that interact and take actions on websites in this course, created in partnership with and taught by and @namangarg0, Co-founders of AGI Inc. AI browser agents can log into websites, fill out forms, click through web pages, or even place orders online for you. They use both visual information, like screenshots, and structural data, like the HTML or Document Object Model (DOM) of a web page, to reason and take action. With the complexity of webpages and multiple possible actions at each step, it can be challenging for an AI browser agent to complete an assigned task. Because these agents run long action sequences, a single error—like clicking the wrong button or misreading a field—can lead to unexpected outcomes or errors that compound over time. In this course, you'll understand how autonomous web agents work, their current limitations, and how AgentQ enables them to improve through self-correction. In detail, you'll: - Learn what web agents are, how they automate tasks online, their architecture, key components, limitations, and an overview of their decision-making strategies. - Build a web agent that can scrape website and return course recommendations in a structured output format. - Build an autonomous web agent that can execute multiple tasks, such as finding and summarizing webpages, filling out a form, and signing up for a newsletter. - Explore AgentQ, a framework that enables agents to self-correct by combining Monte Carlo Tree Search (MCTS), a self-critique mechanism for continuous improvement, and Direct Preference Optimization (DPO). - Deep dive into MCTS, learn how it finds an effective path, illustrated by an example of Gridworld animation, and use AgentQ to complete web tasks. - Understand AI agents' current state and future directions—including key factors shaping their evolution, such as hardware, algorithm innovation, and data availability. By the end of this course, you will have hands-on experience building browser agents and a deeper understanding of how to make them more robust and reliable. Please sign up here:

Andrew Ng

186,182 просмотров • 1 год назад

🚨 THIS IS ACTUALLY INSANE Your AI agent can have access to the web. But if it can't reliably read what’s actually on the page, that access is almost useless. We looked at Firecrawl as the web layer for AI agents and the numbers are hard to ignore. The setup is simple: Give it a URL, search query, or website. Firecrawl handles the ugly part — crawling, scraping, rendering, extracting, and turning web content into something an AI model can actually use. The headline numbers: → 173,000+ GitHub stars → Search, scrape and interact with the web at scale → Supports web pages, PDFs, DOCX and other content → Structured data extraction for AI workflows → MCP support for connecting it directly to AI agents The workflow looks like this: Search → Scrape → Crawl → Extract → Feed the agent Three things stand out: 1. Scraping becomes an infrastructure layer Instead of maintaining your own pile of HTTP clients, parsers, browser automation and retry logic, you can treat web access as an API. 2. Agents get more than raw HTML The goal isn't just downloading a webpage. It's turning messy web content into clean context that an LLM can reason over. 3. The same layer works across different agent workflows Research agents. RAG pipelines. AI search. Competitive intelligence. Web-data extraction. The interesting shift: AI agents don't just need better models. They need better access to the information those models are supposed to reason about. Firecrawl is building that layer. Save this repo.

Vikas gupta

18,053 просмотров • 12 дней назад