Paul Klein IV@pk_ivJune 18, 2025
I've been spending time experimenting with Director, from @browserbasehq. Director is an interface for automating web tasks via natural language instructions.
But that description doesn't do Director justice. Director is a new thing, and an interesting thing, and to understand this kind of new thing you have to experiment. (Or at least I do.)
One way to think about Director is that it's a text box for the web that goes beyond the text boxes for the web that we've had so far:
1) search ->
2) big LLM (blurry jpeg of the web) ->
3) big LLM + search ->
4) Director
Several things combine to make Director powerful. It's interactive. The chat UI is a good way to build and refine an action. Director is good at navigation and domain-specific actions in a way that I really respect, having some experience building scaffolding for open-ended generative AI tools! Also, Director isn't *just* a chat interface. It produces code that I can further modify and use programmatically.
Here's an example Director prompt:
"Look at all the github issues here: https://t.co/RITm4V8yWv. Group the issues into broad categories. Summarize the categories. Describe how many issues are in each category. Pay more attention to recent issues."
Could I have written the code to do this using the Github APIs and LLM inference calls? Yes! Have I been meaning to do that? Yes! Did I actually do it, before Director wrote the code for me? (No.)
Congratulations to @pk_iv and the Browserbase team on really awesome work. This deserves the highest compliment of the current era: Director is genuinely useful, and it's the worst it will ever be.
Paul Klein IV@pk_ivDevelopers automated the web.
Now everyone can.
Announcing Director and our $40M Series 🅱️
