Skip to content

(Finale) Open Problems and Demo Day: Computer Use, Web Agents, and Pre-Launch Checks | Stanford CS329Z Lecture 19

Sep 10, 20261 min
TL;DRPer the schedule, Lecture 19 closes the course with multimodal agents, web and computer-use agents, science agents, long-running architectures, production and observability (tracing, monitoring, cost management), and open problems in reliability, scalability and interpretability. The additional readings are OSWorld and WebShop; the final Demo Day falls in exam week, Dec 7–11.

Look up & save

Loading dictionary…

🌏 中文版

Video status: Recordings require sign-in or course authorization. Source details

The last lecture (Dec 2, Frontiers & Open Problems) has no assigned main reading. The schedule lays out multimodal agents, web and computer-use agents, science agents, long-running architectures, and production tracing, monitoring and cost management, then closes with open problems in reliability, scalability and interpretability. The final report and system demo fall in exam week, Dec 7–11, with time and place still to be announced; project topics are self-chosen under the current official requirements and tie back to the course's core themes.

The additional readings are Xie et al.'s OSWorld and Yao et al.'s WebShop. This post digests both, followed by a pre-Demo Day checklist and a retrospective of the whole series. As of 2026-10-29 this lecture has no public slides, so this post is a preview built from the official schedule and assigned readings, not a record of what was said in class. Lecture numbers after 11 follow schedule order; the course site currently lists only dates and topics.

Reading 1 | OSWorld

Source: OSWorld

TL;DR

OSWorld supplies reproducible computer tasks and execution-based checking of environmental outcomes rather than only textual answers.

Editorial judgment

DimensionReading judgment
Central questionHow can computer-use agents be evaluated in real operating systems?
Evidence and scopeThe 12.24% result concerns the original paper's best tested model, not today's computer-use ceiling.

Domain background

Computer tasks span application state; final text cannot establish completed files, settings, or workflows.

Intermediate guide

Method. Supply natural-language tasks in resettable OS environments, allow model actions, and check outcomes using executable tests.

Evidence and result. The original study identifies GUI grounding and operational knowledge as bottlenecks; its12.24% result retains model and environment conditions.

Deeper points

  • Intermediate screens in cross-application tasks do not establish a correct final state; inspect actual outcomes.
  • Initialization must be reproducible or previous windows and files alter task difficulty.

Reviewer’s one-line verdict

Verify computer actions against the environment.

Your take-away

Verify GUI tasks from actual files or application state and record the initial environment.

Reading 2 | WebShop

Source: WebShop

TL;DR

WebShop evaluates search and choice from natural-language shopping requests in a simulated store, connecting language to web actions.

Editorial judgment

DimensionReading judgment
Central questionCan conditions in shopping requests be grounded in product selection?
Evidence and scopeThe 29% is the original study's best-model task success; a simulated store is not live commerce or current capability.

Domain background

Shopping requires mapping language constraints to web choices; similar products need not satisfy all constraints.

Intermediate guide

Method. Models search, inspect attributes, and choose products from instructions; the environment checks products against user constraints.

Evidence and result. The original best model's29% success versus 59% for human experts shows a gap in grounding shopping constraints through sequential actions.

Deeper points

  • Search and choice can be learned separately, but final acceptance must check product conditions rather than keywords alone.
  • Simulation fixes some real-web variability, so success does not establish live-transaction reliability.

Reviewer’s one-line verdict

Choosing correctly requires checking each constraint.

Your take-away

Verify product attributes and user constraints instead of equating clicks or fluent text with choosing correctly.

What to do: the Demo Day checklist

What to do: turn tracing fully on and keep one replayable trace per rehearsal. Watch three things in monitoring: error rate, latency, and token spend. Put a hard cap on cost with automatic cutoff past the limit. Keep high-risk tools off by default and enable them by hand only for the live demo. Finally, prepare one failure case — a failure mode from your midway report, told well, persuades better than successes alone.

Series retrospective: one post per lecture

Where it sits in the course

Lecture 19 closes the course: from Lecture 1's compound systems through tools, loops, memory, division of labor, optimization, data, evaluation and safety, back to how far agents get on real computers and websites. The series retrospective below doubles as a map for final review.

Course material for this lecture

  • Official slides: not yet public (as of 2026-10-29)
  • Additional readings: Xie et al., "OSWorld: Benchmarking Multimodal Agents in Real Computer Environments" (digested here); Yao et al., "WebShop" (digested here)
  • Finals: Final Report Due & Final System Demo, Dec 7–11, time TBA
  • Schedule: CS329Z site

Course video sources

The Lecture Recordings section of the official Logistics page (read live on 2026-10-10) says recordings are available only by logging into the course Canvas site. I opened the course Canvas entry (canvas.stanford.edu/courses/233286) and was redirected to the Stanford login page, confirming the sign-in wall. Neither the course site nor a web search turned up a public YouTube or OCW recording, so there is nothing to embed.

Course and recording entries:

Checked: 2026-10-10.

Update log

  • 2026-10-29: The series moved from one post per week to one post per lecture. This post now holds Lecture 19 (Wed Dec 2), previously part of the "Week 11: from waiting for instructions to acting first" guide; earlier entries below predate the split.
  • 2026-10-23: Rebuilt the guide around source status, mechanisms, a worked scenario, and answer criteria; separated detailed assigned readings from lecture preparation.
  • 2026-10-23: Added diagrams and comparison tables where useful for the existing explanation; this visual update does not reverify numerical results, schedules or research claims.
  • 2026-10-10: Added explicit video status and checked recording sources and access notes.
  • 2026-09-12: Made the Week 10 Thanksgiving recess explicit in the series map and course-material checklist so the Week 9-to-11 jump no longer looks like a missing post.
  • 2026-10-10: Rechecked video status. The official Logistics page says recordings require logging into the course Canvas, opening the entry confirmed the sign-in wall, and no public recording was found; the status is now sign-in required.

References