Infinity

Infinity is built around the Reactive Agent Protocol (RAP), a successor to MCP that makes tool calls asynchronous. RAP servers deliver results whenever they're ready, without any long-lived connections. RAP also makes subscriptions a first-class concept, so a single call can stream an ongoing series of events to the agent, which reacts to each webhook, schedule, or alert as it arrives. Existing MCP servers run unchanged through a compatibility layer.

Agent work is full of things that don't finish right away: a build runs for twenty minutes, a webhook fires hours later, a human approves tomorrow, a child thread reports when it's done. RAP expresses all of them with one set of semantics, so long-running calls, real-world events, and concurrency are one mechanism instead of three subsystems.

The Infinity Runtime offers a new time-sliced architecture for running durable, concurrent agents without amplifying resource costs. Each turn runs as a short slice that loads state, runs the model, dispatches calls, and yields, releasing all compute and memory in between. Agents waiting on a tool call or event consume zero resources, and thousands of agents can share the same compute.

Because state lives in durable storage rather than process memory, agents survive restarts, redeploys, and cold starts, whether running as a local daemon or on AWS Lambda in production.

Infinity Code leverages RAP and the Infinity Runtime to put the whole stack to work on your codebase. It spawns child threads to handle independent work in parallel, and streams logs from long-running commands back through subscriptions instead of blocking on them. It hibernates while that work runs, then merges each result into a sandboxed diff you review.

Sessions persist in the local daemon, so you can detach from a busy agent and reconnect later, from the terminal or the desktop UI, with full context intact.