🌏 中文版
Today's Highlight
The thing worth connecting today isn't any single repo — it's the same idea surfacing in three unrelated places at once. Claude Code v2.1.323 added an experimental "Code Mode" that lets an agent write a bit of JavaScript to call its tools instead of picking one tool at a time. UTCP's community-built code-mode library, which has been around for half a year, got pulled back into the conversation this week by an article comparing UTCP to MCP — it does the same thing: write code that calls several MCP or UTCP tools in one shot. And Vercel entered the agent-framework race with eve, a filesystem-first take on the same problem space. The old "one tool call per turn" pattern looks like it's being replaced by "let the agent write the program."
Simplified for illustration — context-window size and pricing differ too, but this only shows the structural change in how tools get called.
Trending Repos
vercel/eve ⭐ 5,884
GitHub · TypeScript · Apache-2.0
- What it is: Vercel's open-source agent framework, built around a "filesystem-first" philosophy — an agent's instructions, tools, and workflows live in ordinary files and fixed folders instead of a database or a framework's own runtime objects.
- Why it's worth watching: Most frameworks keep agent state in memory or in custom objects; eve flips that around and spells everything out as files — instructions are literally written in Markdown — so a project can be code-reviewed, version-controlled, and even read by another agent, just like ordinary source code. For coding agents already comfortable working with a filesystem (Claude Code, Cursor, and the like), this fits their native workflow better than hiding logic behind a framework's abstraction layer.
- Tech stack: TypeScript + fixed directory conventions (
agent/agent.ts, etc.) + sandboxed execution + a workflow engine - Getting started: Medium — documentation is solid (eve.dev), but you have to buy into its convention-over-configuration layout; switching frameworks later isn't cheap
universal-tool-calling-protocol/code-mode ⭐ 1,667
GitHub · TypeScript · MPL-2.0
- What it is: A library from the UTCP (Universal Tool Calling Protocol) community that lets an agent skip calling tools one at a time and instead write a program that calls several MCP or UTCP tools in a single pass, then collects the results.
- Why it's worth watching: This happens to be the same idea being discussed alongside Claude Code v2.1.323's new experimental "Code Mode" this week — the core logic is identical: stuffing every tool's schema into context is expensive, so let the agent write code instead and save a lot of tokens and round trips.
code-modeis proof this isn't one vendor's experiment — an independent community already built it, and it stays compatible with the existing MCP ecosystem without requiring any MCP server to be rewritten. - Tech stack: TypeScript + a compatibility layer spanning both MCP and UTCP + agent runtime integration
- Getting started: Medium — the idea itself is simple, but you need to understand how MCP and UTCP describe tools differently before the value becomes obvious
nkarasiak/qgis-mcp ⭐ 436
GitHub · Python · GPL-2.0
- What it is: Lets any MCP-capable agent (Claude Code, Claude Desktop, Cursor, Gemini CLI, and more) drive the desktop GIS software QGIS directly — managing layers, editing features, running processing algorithms, and rendering maps, all from natural-language instructions.
- Why it's worth watching: Unlike a chatbot that merely answers GIS questions, this MCP server plugs the agent straight into QGIS's event loop over a TCP socket to a plugin. Destructive operations ask for a second confirmation by default, and long-running tools report progress. For GIS analysts, that means running a whole workflow in natural language instead of switching back to manual menus.
- Tech stack: Python MCP server (FastMCP) + a QGIS Python plugin (a non-blocking TCP socket on QGIS's QTimer) + the PyQGIS API
- Getting started: Medium — install the QGIS 3.28+ plugin first, then wire up an MCP client; the list of supported clients is long, but setup is more than one step
JuliusBrussee/caveman ⭐ 119,655
GitHub · Go · Apache-2.0
- What it is: A skill-plus-proxy combo written in deliberately caveman-speak, which flattens prompts and tool results into minimal sentences before they reach the model, claiming a 65% cut in token usage for coding agents.
- Why it's worth watching: The interesting part isn't the technique — it's how it spread. Wrapping a real pain point ("stop talking so much, save tokens") in a meme, funny enough and useful enough to get shared widely, took it to nearly 120,000 stars within months — proof that token costs hurt enough that people will star and share a joke-wrapped tool. Strip away the meme and it's a prompt-compression proxy solving the same problem as any other context-compression approach.
- Tech stack: A local Go proxy + prompt/tool-result simplification rules + cross-platform desktop installers
- Getting started: Low — install the proxy and point your existing coding-agent setup at it; no changes to the agent itself
Notable Releases
Mastra @mastra/core 1.83.0
- Key changes: Resumable run streams, previously limited to "durable agents," now work for every
Agent— with replay caching and cross-instanceagent.observe(runId)/abortRunStream;@mastra/serverships a built-in MCP endpoint at/api/mcp, on by default onceserver.authis configured, so you no longer have to hand-roll your ownMCPServer, plus OAuth discovery; Workflow Storage V2 (writing only per-step deltas instead of rewriting the whole run) now officially supports Postgres and libSQL. - Breaking changes:
Agent'sdurableoption now only controls whether a stream can be resumed — it's no longer the same thing as checkpoint-backed durable execution. If you relied ondurable: truefor persistent execution, migrate tocreateDurableAgent({ agent }); plain agents also behave differently on disconnect now that resumable streams are on by default. - What it means for you: If you were treating
durable: trueas "survives a disconnect and keeps running," that behavior isn't equivalent anymore — switch tocreateDurableAgent. If all you wanted was "a client can reconnect without killing the stream," you get that now without setting durable at all.
Today's Takeaway
I assumed Claude Code's new "Code Mode" was Anthropic's own experiment, but digging in turned up a UTCP community library doing the same thing half a year earlier — and it's compatible with both MCP and UTCP. That tells me "let the agent write a program instead of looping through tool calls" isn't one vendor's gimmick; the whole ecosystem is converging on it, just at different speeds.