Loading video...

Video Failed to Load

Go Home

How do always-on, proactive agents like @Bot work? Watch my lecture at Stanford CS146S: 2:35 How we got here 6:13 What changed in the models 10:06 Inside an always-on agent 18:07 The harness 27:26 Context engineering 34:26 Where this is going

578,966 views • 4 days ago •via X (Twitter)

29 Comments

eric zakariasson's profile picture
eric zakariasson4 days ago

@bot huge

Pratham's profile picture
Pratham4 days ago

@bot Fire fit @leerob.

Ben Dicken's profile picture
Ben Dicken4 days ago

@bot Excellent talk.

serx · fireply.ai's profile picture
serx · fireply.ai4 days ago

@bot what changed in the models is mostly tool calling not breaking every third step

Pratham's profile picture
Pratham4 days ago

@bot DAMN! The goat has dropped.

Josh Larson's profile picture
Josh Larson4 days ago

@bot Stanford Lecturer!!! How cool

Alexander Abelt's profile picture
Alexander Abelt4 days ago

@bot Is it somewhere on YouTube?

El aprendiz's profile picture
El aprendiz4 days ago

@poteto @bot @bot requiero la transcripción de esta conferencia

glitchedge's profile picture
glitchedge4 days ago

@bot always-on is the easy part. knowing when not to ping you is the actual hard part

shub's profile picture
shub4 days ago

@bot let's go!!

Nishkarsh's profile picture
Nishkarsh4 days ago

@bot saving context engineering part for tonight

Abdullah 's profile picture
Abdullah 4 days ago

@bot Been following your content for a long time Watched the whole thing the always-on agent setup (server + VM, sub-agents, and keeping the main context sparse) is clear and practical The context engineering section at 27 min is the one I’ll rewatch

Simon Lin's profile picture
Simon Lin4 days ago

@bot I'm turning this lecture into a breakdown site: chapters, diagrams, the key ideas from the harness and context engineering parts. Will drop the link right here and post it once it's live. Also, hope we get to see you give this talk at Columbia someday 🙌

Lúcia Mees's profile picture
Lúcia Mees4 days ago

@bot @bot watch this for me and give me the summary

Rafael Ibayev's profile picture
Rafael Ibayev4 days ago

@bot proactive is the hard part. knowing when not to interrupt seems harder than doing the task itself

Kristian Phoenix's profile picture
Kristian Phoenix4 days ago

@bot 💡

Jide Lambo's profile picture
Jide Lambo4 days ago

@bot A lot to learn here. As mentioned, @bot harness returns errors like “the computer is asleep. wake it with the shell. then retry.” Our system returned a bare not_found, which is how it failed sometimes. Every tool should return a next step instead and not just fail.

Theodore Rogers's profile picture
Theodore Rogers4 days ago

@bot Yea, will definitely watch this later. x

Blum's profile picture
Blum4 days ago

@bot Thanks for the timestamps, convenient to pull out just the segments of the video that are interesting

Yin Lai's profile picture
Yin Lai4 days ago

@parkersmith @bot @bot save this

Dominik's profile picture
Dominik4 days ago

@bot always-on agents die on what they keep between wakes, not on the model call. the harness chapter is the one worth stealing.

Ryan Rong's profile picture
Ryan Rong4 days ago

@bot 🔥

Rajat Kapoor's profile picture
Rajat Kapoor4 days ago

@bot skipping straight to 18:07 lol

Khushal's profile picture
Khushal4 days ago

@bot 45 minutes on always-on agents and mine can't stay on through lunch

Arthur Alston MD MBA's profile picture
Arthur Alston MD MBA4 days ago

@poteto @bot @bot make a note to watch this

Alain's profile picture
Alain4 days ago

@bot Bookmarked for a quiet hour! Looking forward to learn a thing or two 🚀

Fightlook's profile picture
Fightlook4 days ago

@parkersmith @bot Bless us with a Cursor and Grok Bot reset pls sir.

enrico's profile picture
enrico4 days ago

@bot Looking forward to watching this over a coffee

anish's profile picture
anish4 days ago

@bot saving this one for later. the context engineering part at 27 minutes is what i'll watch first

Related Videos

When Mudith Jayasekara and I met Gabe Pereyra, we were expecting just another vanilla intro call and instead had the best yarn about research, the state of LLMs, and where intelligence is actually heading. It's rare to meet a founder this deep in the weeds who's also building for one of the most important verticals in this new age of intelligence So it was awesome to sit down with Gabe for an extended discussion on what it take to build agents that can reliably complete work over hours, days, or even longer? We talked about why agents today struggle with search and long context windows and how techniques like KV-cache compaction, synthetic data, and continual learning could help. 0:00 Introduction 0:36 Getting legal agents to review the whole data room 2:08 Data rooms larger than any context window 5:28 How far open-source models can go 7:58 Where specialist models fit in legal AI 10:59 Training legal models when client data is off-limits 13:06 Teaching a model how a law firm works 13:59 What belongs in context vs. model weights 15:36 From firm-wide AI to a model for every lawyer 18:37 What training adds beyond retrieving the right cases 20:26 Why context windows have plateaued 24:01 How models could learn continuously on the job 26:12 Can AI recursively improve AI research? 27:07 Research agents can run experiments but not choose them 30:00 Why open-ended research is hard to train 33:47 Why deployment, not intelligence, is the bottleneck 35:08 The cost of frontier intelligence 36:59 Different neolabs, different paths to intelligence 39:26 Using open datasets to compare research methods 41:13 Conclusion

Charlie O'Neill

93,546 views • 2 months ago

Harnesses often get dismissed as just scaffolding, just prompt engineering, and not real research. But that couldn't be farther from the truth. The same model weights that score 30% on ARC-AGI score 95% with a better harness. So we gathered a group of researchers and founders working at the frontier to do a deep dive into the state of harnesses. We cover how we got to this point, the case for making your harness as expressive as possible, and what YC learned building an agent for every employee in the company. 00:00 - Francois Chaubard: Why harnesses matter 04:27 - Building an auto-researcher by accident 07:13 - A five minute history of harnesses 13:56 - Self-improving harnesses 18:35 - Seth Karten: Prime Agent, a self-improving RLM harness 21:50 - Context as an L1, L2, L3 cache 24:51 - From Turing machine to von Neumann computer 28:33 - Messaging between agents 30:04 - ARC-AGI results 33:09 - Emulator Bench and GPU kernels 37:30 - Jon Saad-Falcon: OpenJarvis, personal AI on personal devices 38:26 - How far behind are local models 39:21 - The five primitives of a personal AI stack 42:47 - Letting cloud models optimize your local stack 43:53 - 800x cheaper than the cloud 45:58 - Josh France and Regan Bell: QM, YC's agent harness for work 47:29 - A history of YC's internal agents 49:24 - OpenClaw and a fleet of 50 agents 51:04 - Pulling the brain out of the sandbox 54:43 - Letting the agent choose its own sandbox and model 57:16 - The grind tool: budgets on goals 58:50 - Agents don't understand social context

Y Combinator

495,816 views • 1 month ago

We use OpenClaws to do all of our work at Every 📧. We have 25 full-time employees, so we’re one of the few companies in the world that has seen how work changes when everyone has their own personal agent in the company Slack. I chatted with Every 📧 COO Brandon (Brandon Gell) and Every 📧 head of platform Willie (Willie) to share what we’ve learned. We get into: - Why agents become mirrors of their owners, and how that influences how other people on the team interact with them - How a parallel AI org chart forms on its own. People have stopped tagging me on Slack with questions about Proof, the document editor I vibe coded, because they knew my agent R2-C2 can step in - The etiquette for human-agent collaboration is being invented in real time. Brandon's rule is that if there's an established process or documented answer, always ask the agent, not their human - Why everyone is a manager now, and why even experienced managers carry limiting beliefs about what their agents can do - This is a must-watch for anyone trying to understand how AI workers change daily operations, not just in theory, but inside a company that’s half-agent Watch below! Timestamps Introduction: How Brandon built Zosia, an AI agent to run his household: Brandon’s “aha” moment: What happened when everyone on the team got their own agent: How agents take on their owners' personalities, and why that matters inside an org: Why it’s important for agents to work in public: What we’re still figuring out when it comes to agent behavior, including memory gaps, group chat etiquette, and the "ant death spiral" problem: How we built Plus One, our hosted OpenClaw product: The cultural shift required to make agents work at scale:

Dan Shipper 📧

67,958 views • 6 months ago