Repository navigation
Carbon Forge over MCP: a shared, versioned record smolagents can read and write #3087
Theaxiom
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Carbon Forge keeps code, files and prose in one record on the server, and people and agents read and write it through the same tools over MCP. It fits smolagents as the place an agent's work goes when other agents and people need to see it with its history.
The connection is
MCPClientpointed athttps://carbonforge.dev/api/mcp(Streamable HTTP). Without a token it reads public workspaces; writing needs a bearer token. I have not yet run it from aCodeAgent; that is what the example below would settle.What each write gives you: an agent opens a lane instead of cloning, a landing is one all-or-nothing changeset, and history is hash-chained, so a revert is a new landing rather than a rewrite.
The proposal: a short example in this repository's examples or a joint post. For whoever builds it with us there are three-month Carbon Forge subscriptions for the team and a batch for this community, with a promo code agreed with me. Public workspaces are free, and every account includes one free private workspace.
Would an example like this be useful here, and which agent type should it use?
Docs: https://carbonforge.dev/docs/p/home?utm_source=smolagents&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.
All reactions