agentc - a minimal agent in C: under 1 MB, no runtime

Reddit r/AI_Agents Tools

Summary

agentc 是一个用 C 编写的极简可扩展编码代理:单个静态二进制不到 1 MB、无 libc,通过 MCP 处理外部工具,并提供带版本的 C ABI 支持进程内扩展。项目支持 macOS/Windows 运行时动态加载扩展,作者希望与社区讨论 MCP 与进程内扩展的边界划分。

Hi everyone, just sharing a small project: A minimal, extensible coding agent, built around the question of what an agent's extension surface should actually be. - MCP for anything external: tools, prompts and resources over stdio, with reconnect behind capped exponential backoff - A versioned C ABI (include/agentc_ext.h) for anything that needs to be in-process: sync or async tools, providers, models, and prompt/theme roots - Extensions either link into the binary or load at runtime on macOS/Windows; C and Rust reference extensions included - Session state is JSONL, config is JSONC, and there's no cross-agent file-format compatibility to worry about - One static binary under 1 MB, no libc; ~0.7 MB RSS at startup, ~2–4 MB idle MIT. Would like to hear how others are drawing the line between MCP and in-process extensions. Would love for anyone on macOS or Windows to try it: Linux is tested end to end, but those two have only run in CI so far. Binaries are up for Linux (x64, arm64, riscv64), Windows (x64, arm64) and macOS (arm64).
Original Article

Similar Articles

Code execution with MCP: Building more efficient agents

Anthropic Engineering

This article from Anthropic explores how integrating code execution with the Model Context Protocol (MCP) can improve the efficiency of AI agents. It addresses challenges like token overload from tool definitions and intermediate results, proposing code execution as a solution to reduce latency and costs.

25 agents, 50 MCP servers, 1 app: what stack would you pick?

Reddit r/AI_Agents

A practitioner asks the community how to architect a production agent platform on AWS with ~20 agents and 50 MCP servers, weighing options like Bedrock AgentCore, Claude Agent SDK, Strands, LangGraph, A2A, LiteLLM, and Langfuse while demanding full Claude features and working prompt caching. The post seeks recommendations on framework choice, inter-agent communication, MCP hosting, and repo strategy.