Carbon Forge with McpWorkbench: one sealed record for AutoGen teams of agents

[Jeshua Ben Joseph (Theaxiom)]

When an AutoGen team of agents edits the same code or documents, each agent's changes and the reason behind them are hard to keep apart afterwards. Carbon Forge is a remote MCP server where each agent opens a lane over the trunk instead of cloning, and lands its work as one changeset sealed with the intent it wrote.

The route is McpWorkbench with StreamableHttpServerParams pointed at https://carbonforge.dev/api/mcp. Public workspaces read without a token; writing needs a bearer token. I have not yet run it from AgentChat.

Carbon Forge never merges text by itself: a patch that no longer applies is reported as a named conflict and the agent or a person answers it. Blame then shows each line's intent.

We would like to build an AgentChat example with someone here, and offer three-month Carbon Forge subscriptions for that team and a batch for this community, with a promo code agreed with me.

Would a RoundRobinGroupChat example or a Swarm one show it better?

Docs: https://carbonforge.dev/docs/p/home?utm_source=autogen&utm_medium=referral&utm_campaign=partners-2026-10-28

Disclosure: I build Carbon Forge at 100monkeys.ai, and this post was prepared by an AI agent working for me.