Built for the agents, not the developer: a governance layer from Microsoft and an agent-only language from Vercel
Something shifted this week. The tools that stood out weren't built for developers. They were built for the agents developers run. Microsoft shipped a governance layer that sits between your AI agents and the actions they take, evaluating every tool call against policy before it executes. Vercel Labs went further and released a programming language whose intended reader isn't a person at all, it's the compiler talking back to a model in clean JSON. Different problems, same premise: agents are now first-class users of our tooling, and the tooling is starting to assume it. Not everything went that way. n8n is still doing the unglamorous work of wiring 400 services together so you don't have to, and html-anything just borrows the agent CLI you already pay for to turn notes into polished HTML. But the direction of travel is hard to miss. We spent years making developers faster. Now the tools are aimed one level down, at the agents doing the work.
AI Agent Governance Toolkit: policy enforcement, zero-trust identity, execution sandboxing, and reliability engineering for autonomous AI agents. Covers 10/10 OWASP Agentic Top 10.
The Lens
Agent Governance Toolkit puts a policy check between your AI agent and every action it takes. Tool calls, resource access, and agent-to-agent messages all get evaluated against rules you write before anything runs. The distinction that matters: this is application-layer enforcement, not prompt instructions asking a model to behave, so a jailbreak in the conversation does not talk its way past it. MIT, maintained by Microsoft, free. It is framework-agnostic on purpose, with adapters for LangChain, CrewAI, AutoGen, AWS Bedrock, Google ADK, and Azure AI among others, plus SDKs for Python, TypeScript, Rust, Go, and .NET. You get a CLI, a governance dashboard, and published specs mapped against the OWASP Agentic Top 10. Installation is a package manager command; the actual work is writing policy that reflects what your agents should be allowed to do, which nobody can do for you. Someone shipping a weekend agent can skip this. Anyone putting an autonomous agent in front of production systems or customer data needs this or an equivalent, and there is no free-versus-paid decision to make because Microsoft ships the whole thing MIT with no commercial gate. The catch is scope, and it is narrower than the marketing suggests. This governs what an agent does, not what a model says, so prompt injection that produces a bad answer rather than a bad action passes straight through and you still need a content safety layer beside it. It is also public preview, with breaking changes expected before GA.
✨ The agentic HTML editor: your local AI agent writes the HTML, you ship it. 🚀 75 Skills × 9 Surfaces (magazine · deck · poster · XHS / tweet · prototype · data report · Hyperframes) 🛡️ Sandboxed preview · 📤 1-click to WeChat / X / Zhihu / HTML / PNG 🔑 Zero API key. Claude Code / Cursor / Codex / Gemini / Copilot / OpenCode / Qwen / Aider.
The Lens
HTML Anything turns Markdown, spreadsheets, PDFs or plain notes into polished single-file web pages by handing them to the coding agent you already use. Pick Claude Code, Codex, Gemini or one of about twenty supported CLIs, pick a template, and it streams back a slide deck, magazine layout, poster or social card. Apache 2.0, from the team behind nexu-io/open-design, and it reuses your logged-in agent session, so there's no API key.
It runs as a local web app in your browser, not a desktop program. Clone it, install with pnpm, and start it with pnpm -F @html-anything/next dev (plain pnpm dev does nothing at the repo root). The 81 templates are agent skill files, and output exports to WeChat, Zhihu, Notion, Bluesky, PNG or straight to your own Vercel account. A command-line version handles batch jobs.
Anyone already paying for an agent subscription who wants presentable HTML without another tool bill should try it. Without an agent CLI installed, it does nothing. The templates are Chinese-first, with CJK font stacks throughout, which suits WeChat publishing better than a US pitch deck.
The catch: to run unattended, it launches your agent with every safety prompt switched off (Claude Code in bypass-permissions mode, Gemini in yolo mode). That's an agent with full access to your machine working from whatever file you drop in, so don't feed it documents you didn't write. Development has also slowed sharply since spring, and there has never been a tagged release.
Fair-code workflow automation with native AI capabilities
The Lens
n8n is a visual workflow automation tool, the self-hostable answer to Zapier and Make. Drag nodes onto a canvas to connect apps, APIs and AI models, drop into JavaScript or Python when the visual editor runs out, and run agents and MCP tools inside workflows. It ships hundreds of integrations. It's source-available, not open source. Self-hosting is free with no execution limits, but the free Community edition leaves out sharing workflows and credentials, projects, SSO, environments, Git version control and external secrets: only the owner and the creator can see a workflow. n8n 3.0, due October 2026, drops npm installs and requires Docker. Security advisories arrive constantly (75 between August and early October 2026), so patching is part of the job. Cloud Starter is $24 a month ($20 billed annually) for 2,500 executions; Pro is $60 a month for 10,000. Business is self-hosted only at $960 a month ($800 annually) for 40,000 executions, adding SSO, Git and environments; Enterprise is custom. Solo builders: self-host free. Small teams that need to share workflows hit the paywall fast, so price Business against Zapier honestly. The catch: the Sustainable Use License allows only internal business, non-commercial or personal use. Embedding n8n in a product you sell, or hosting it for customers, needs a commercial deal. Paid self-hosted licenses also ping n8n's license server daily.
The programming language for agents
The Lens
Zerolang is Vercel Labs' experiment in a programming language that AI agents write and humans review. The program isn't really the text files. It's a compiler-owned graph of symbols, types and calls, and agents change it through checked patches (zero patch) instead of editing lines. Humans read a generated .0 text view. Apache 2.0, free.
Install is a curl | bash script that pulls the compiler from GitHub releases, plus an agent skill via npx skills add. Nothing to host. The pitch is fewer wasted agent loops: stale or invalid edits fail before they touch the program, and the agent gets node IDs and graph hashes instead of guessing from source text. No paid tier, so solo devs, small teams and larger teams all pay nothing, but only people building coding agents have a reason to try it.
The catch is the README's own safety warning: expect breaking changes, rough edges and security issues, and keep it away from production systems and sensitive data. It has also gone quiet. The last release shipped in June, and only a couple of commits have landed since. Study the idea, don't build on it.
Get the next issue in your inbox
Free. No spam. Unsubscribe anytime.