devtools.fm: Developer Tools, Open Source, Software Development · Hands-On Engineering Podcasts · November 2026
Asked whether his browser-based agents can run scripts like coding agents, Hobson says no, on purpose, because his product is for non-developers. This is his case for why running the agent in the browser simplifies permissions.
…storage for you. However, authentication is almost always going to require a server. But I think other than that, it's fundamentally the same thing. It's agents calling tools that talk to other agents and handoff and all that same passing forward and back. It just happens to run in your browser.
…a tiny scripting system into the agent, like in a sandbox way with only access to certain tools. But it feels like something that's kind of like needed if you're doing anything that's like super complex. Does your guys' methodology have that at all? Can it write tiny scripts? Does that work at all?
So that doesn't work. I think there's a slight difference between how we as developers see how AI harnesses work and what you actually need in an end user product. We often think, oh, yeah, which terminal, it's great. It's got access. Off it goes. We trust, you know, we can verify, we'll make sure it's in Git. We can secure it into its little area so it can't do anything too bad. But in a product, deterministic output is kind of useful, even if it's not like as good. So you have to try and capture the AI and be like, well, look, you've got, you can be non-deterministic within this space. And, you know, if we did give it, you know, the ability to just eval some code on the user's computer, we don't know what's going to happen there. Like, let's not do that. So the boundary there, I think, is actually a very good one. So rather than, you know, let's say you were building this from scratch inside a company, you were just like, right, we need a dashboarding tool. You'd probably build it all on the server and you'd probably just give the AI access to what it has.…
That's an interesting point. I think permissions and understanding differences between what you can do and what an agent can do on your behalf is something that's very confusing, especially for folks who are potentially less technical. So I think from that perspective, it makes sense, the approach…
Yeah, so I mean, it is basically the standard sort of sub-agent approach. So we have a lead agent. So our team, as we call it, like the team of agents that we supply by default, you have a lead agent. You'll have a data analyst, a sort of page and layout manager. And each widget also gets its own…
So I want to switch gears here a little bit. You guys have published a bit about WebMCP. WebMCP is a topic I have completely avoided. I know it an MCP server. I don't know what web adds to it. Like I thought my MCPs were already on web and already servers. But can you tell me what WebMCP is before…