Agent-net Open Sources Webagent: A Go Harness That Turns Any Website into a Guarded AI Agent
Agent-net open-sourced Webagent, a Go harness turning websites into AI agents with code-enforced guardrails wrapping every tool call.
Agent-net released Webagent under Apache 2.0, a Go framework where a business fills in a declarative JSON spec, picks one provider for each of nine pluggable slots (retrieval, memory, guardrail, channel, secrets, presenter, model, action, observability), and runs webagent serve. Every tool the agent holds is wrapped by action.Guard so the chosen guardrail executes before any action runs and the model cannot bypass it. Live capabilities include OpenRouter/gateway LLM brains, MCP tools over Streamable HTTP, and Slack, WhatsApp, and HTTP channels; browser actions, OAuth-gated MCP, OTel export, and AgentNet identity/billing are not yet built. The project is v0 with a deferred-hardening list and cites arXiv 2511.19477 on an 85% versus 50% task-success gap attributed to architecture over model capability.
The VMs Powering Mobile Agents (Instinct, Claude Code)
A teardown reveals Claude Code runs in Firecracker microVMs with a Rust PID 1 and MITM'd egress, while Instinct rents E2B sandboxes with git-based memory.
The author inspects the virtual machines hosting cloud agents: Claude Code runs in a Firecracker microVM with a custom Rust init (process_api) as PID 1, a 324 MB Bun harness on a read-only disk, and 443-only MITM'd SSE egress to api.anthropic.com with host-rotated OAuth tokens and no inbound access. Instinct rents E2B sandbox-as-a-service Firecracker microVMs (Ubuntu 22.04, 2 vCPU, 1.9 GB RAM) where agent memory is a git repo of Markdown committed by the agent and pushed to S3 as a single bundle, using short-lived STS credentials. Both platforms rely on Firecracker, differing mainly in fleet operator and guest boot configuration.
ToolHive: The open-source way to run any MCP server securely
Stacklok's open-source ToolHive runs Model Context Protocol servers in isolated containers with per-request identity enforcement, audit logging and a signed registry.
ToolHive, shipped under Apache 2.0, containersizes MCP servers locally via Docker or Podman or in clusters through a Kubernetes operator, applying permissions, network filtering, and secrets management. The platform includes a Registry Server implementing the official MCP Registry API with signing and provenance verification, a Virtual MCP Server gateway with OIDC/OAuth single sign-on and OpenTelemetry traces, and a desktop Portal for one-click installs. The browser-based cloud UI is retired, so the desktop app and CLI are the supported rollout paths.