Read a public Carbon Forge workspace with no account
Attach any MCP client with no token, ground it, name the workspace on every call, read, search and follow history, and slow down at the rate limit.
Guides
Step by step, from the docs
How-to guides from the people who build Carbon Forge at 100monkeys.ai, so read them as a maker's account. Each one quotes the docs page it relies on and says what the docs leave open.
Scope a Carbon Forge MCP token to one agent
Pick a role cap and the narrowest tool preset for each agent, add one tool with a custom scope, and mint a short-lived child token for one agent run.
Roll a Carbon Forge workspace back to a cut
Cut a snapshot before risky work, read what changed since, then restore the workspace to the cut as one forward changeset that removes nothing.
Answer a lane conflict in Carbon Forge
Read the named conflict when the trunk moves under a lane, answer it with a resolution bound to the trunk you saw, or drop the patch, then land.
Export a deterministic slice of a workspace with perspectives
Define a perspective, preview it at a cut, and download a zip or tar that gives the same bytes every time, with a manifest for each file.
Landing rules: code owners kept in the record, with an AEGIS workflow as a gate
Name who approves each path on a .landing-rules page, bind every approval to the exact change, and let an AEGIS workflow be the gate.
Land a code change and its documentation in one changeset
Change code and the page that documents it on one lane, review both, and land them as one changeset or not at all.
Cut a release in Carbon Forge and push it to GitHub
Name a release with a cut, read its notes, then render the code tree as git and push it to GitHub fast-forward only.
Declare governed seams so a drift report catches stale docs before a landing
Declare which pages govern which code, then read a drift report on a lane to catch code that changed without its docs.
Connect Claude Code to Carbon Forge over MCP: shared memory your agents can read, write and cite
Attach Claude Code to a workspace with a scoped token, ground it, and have it write and cite pages a person can read.
Connect Cursor, Codex and any MCP client to one Carbon Forge workspace
One token per client, the exact configuration for Cursor and Codex, and how to check that every client sees the same record.
More guides from 100monkeys.ai: AEGIS and agent traceability and Zaru.