For some reason, Axle releases often come in pairs. Often one release ships something new and interesting, then it prompts follow-up work. In a way, that’s the mark of a productive design iteration.
0.35 highlights
- Continuations. A send can now carry
after, a program that runs once the turn settles. This holds the queue and allows follow-up messages. This is useful in places where a program wants to run a judge process in loop. - Cost tracking. Axle now has
computeCost, and when paired withModelCatalog, can compute cost priced from models.dev. This handles context-length pricing correctly as well, and can price across an entire Agent run. - Providers and Protocols. One long-awaited change is to split protocols from providers. Now you can run the Anthropic Messages protocol against Bedrock, or OpenAI Responses API to OpenRouter.
- Ergonomics and performance. Finally, we cleaned up errors so that client-side handling is simpler and more coherent. Also long overdue, multiple tool calls now run concurrently.
0.36 highlights
- Remote Agents. The client-server layer every agent app rebuilds is now in the library. A numbered event log on the server, a
RemoteAgentin the client with the same API as a local Agent, and resume after a dropped connection built in. It’s the design we’ve been working toward for a long time, and it does most of the heavy lifting. - Deferred tools. Create tools that can be handled later. Deferred tools do not require an execution block when instantiated so they are perfect for scenarios such as asking the user for inputs. Runs remotely too.
- Agent lifecycle events. To round it all out, agents now fire lifecycle events so that you can observe and respond to agent changes. This is useful for running parallel programs and saving agent state.
Posted Nov 11, 2026