30
30
30
30
30
30
30
30
30
30
30
30
30
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.
28
30
30
30
30
30
30
30
30
30
30
30
30
30
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.
35
30
30
30
30
30
30
30
30
30
30
I'm going back to coding by hand
A developer abandoned six months of Claude-assisted work on a popular app, resuming hand coding after losing track of what AI-generated changes did.
In a Hacker News post, a developer of an app with a solid user base describes abandoning a six-month Claude-assisted rewrite because they no longer understood what the AI-generated code changed or broke. The author notes their workplace already writes code exclusively with LLMs and says returning to hand coding restored understanding and motivation. The post advises others feeling detached from their craft to stop using AI coding assistants for a few days.
10
F5 enhances AI Gateway to control AI costs, access, and security
F5 integrated AI Gateway into its AI Security Platform, adding model routing, MCP governance, and guardrails, claiming up to 60% token spend reduction.
F5 announced AI Gateway enhancements combining a Model Gateway for cost optimization, an MCP Gateway for agent-to-tool access control, and AI Guardrails for prompt and response inspection. The company cited its 2026 State of Application Strategy Report finding 77% of organizations now treat inference as their dominant AI activity and manage an average of seven AI models. F5 claims smart routing, semantic caching, and GPU-aware load balancing can cut token spend by up to 60% without application changes. The gateway enforces budgets, model routing policies, and agent access controls centrally across SaaS, hybrid SaaS, and hybrid multicloud deployments, with air-gapped support planned.
30