Agent-net Open Sources Webagent: A Go Harness That Turns Any Website into a Guarded AI Agent
MarkTechPost Michal Sutter
Agent-net open sourced Webagent, a Go harness that turns a website into a guarded AI agent. It already runs Slack, WhatsApp and HTTP agents, but browser actions and billing aren’t built yet.
Based on reporting by MarkTechPost, Michal Sutter — read the original for the full story.
Summary, retelling and take written by AI under human oversight; images are AI-generated illustrations. How we work · Report an error
Agent-net has released Webagent, an open source Go harness for standing up public-facing business agents. The pitch is blunt: point it at a website, fill in a JSON spec, choose providers for the slots it needs, and let it serve. No orchestration code. No hand-built glue for every new setup.
The system is built around a single Brain plus nine pluggable slots in core/. Those slots cover things like retrieval, memory, guardrails, channels, secrets, presentation, model access, action handling and observability. Businesses can just pick from the menu. They can also register their own provider, or ship an adapter as a partner. The project’s own line is that nobody needs to fork the core, and every provider has to pass a slot conformance suite before it can be treated as certified.
The hard line in the architecture is action.Guard. Every tool the agent can reach, whether it comes from the action provider or gets injected by the host, is wrapped so the selected guardrail runs before execution. The model does not get to sidestep that. The design document even ties the project to a research result claiming architecture matters more than model capability, with the same models showing an 85% versus 50% task-success gap.
Webagent is already usable in a few places. The default echo brain needs no credentials, so webagent validate and webagent serve work on the two example specs, zomato.json and bakery.json. Real models can be wired through openrouter or gateway, both OpenAI-compatible clients with a tool-calling loop. Existing MCP servers can also be exposed as acting agents, and Slack and WhatsApp adapters are live with webhook signature checks, immediate acknowledgements, platform replies, self-message filtering and retry de-duplication.
But this is still v0, and the unfinished list is not small. Browser actions, OAuth-gated MCP, OTel export, and the AgentNet identity and billing layer are all marked not yet built. The repo is Apache 2.0, the builds are green, and the live pieces are real. Just don’t confuse that with finished.
My take — AI-written commentary, not fact-checked reporting
This is the right kind of ugly: guardrails enforced in code, not waved at the model like a lucky charm. The industry keeps selling “agent platforms” that are really prompt wrappers with a nicer logo; Webagent at least looks like someone remembered software has to survive contact with reality. Open source wins again by making the sharp edges visible before the bill arrives.
Read more about this at: MarkTechPost
