Hydro Infinity:把空闲智能体收成数据行的 Rust 运行时,并提出 RAP 协议
UC Berkeley 与 AWS 相关的 Hydro 项目开源 Infinity(Apache 2.0,Rust):回合之间智能体只保留会话数据、不占进程;并推出面向异步工具投递的 RAP,宣称可兼容现有 MCP 服务。
开源框架 Infinity(Apache 2.0,Rust 核心)来自 Hydro 项目,文档站点为 infinity.hydro.run。设计要点是:每一轮只做「加载状态 → 调模型 → 分发工具 → yield」,然后释放内存与算力;回合之间智能体只剩会话历史,没有常驻进程、调用栈或长连接,因此空闲成本接近「一行数据」。官方用「树莓派内存里放下约 7.5 万个智能体」形容记账能力,强调的是调度簿记而非单智能体智力。
配套提出 Reactive Agent Protocol(RAP):工具结果与订阅事件可在智能体当前没有进程时再投递,定位为偏异步的工具协议;现有 MCP 服务可通过兼容层接入。同一套智能体代码可在笔记本常驻进程或 AWS Lambda 等无服务器环境运行,并提供 CDK 构念。仓库还包含基于该运行时的 Infinity Code 编程智能体示例(并行构建/测试、沙箱叠 diff 等)。
若你在评估多智能体平台的闲置成本与 Serverless 部署,Infinity + RAP 提供了一条与「常驻 MCP 会话」不同的路径;生产采用前仍需验证与现有 MCP 工具链的兼容层成熟度,以及观测、权限与审计是否够用。
Infinity runtime and RAP from Hydro
The clever part of this runtime is that it makes an idle agent indistinguishable from a row in a database. Each turn is a slice: load state, call the model, dispatch tools, yield, release all memory and compute. Between turns the agent is just its conversation history. No process, no stack, no socket, nothing to bill. Infinity, from the Hydro project with UC Berkeley and AWS, Apache 2.0, Rust core, with a protocol called RAP pitched as an async successor to MCP. The README's 75,000-agents-on-a-Raspberry-Pi figure is a claim about bookkeeping rather than intelligence, and bookkeeping is where agent platforms usually die. https://t.co/8aTsqqagUL