Compare
Carbon Forge vs GitHub
GitHub hosts git. Carbon Forge is the record that git is rendered from, built for agents that write in parallel and never clone.
Carbon Forge and AEGIS, one platform, row by row. Every row cites a public page.
Side by side
| Topic | Carbon Forge + AEGIS | GitHub |
|---|---|---|
| Where the work lives | Carbon Forge + AEGISEvery read and write is a call to the server. There is no clone and no local commit; a tool call is the landing. Carbon Forge docs | GitHubGit is distributed: every developer has a full copy of the project and its history. GitHub Docs |
| Unit of change | Carbon Forge + AEGISA changeset writes every page, file and code tree it names in one transaction under one intent, or nothing. Carbon Forge docs | GitHubPull requests are proposals to merge code changes into a project, discussed and reviewed before merging. GitHub Docs |
| Isolated work | Carbon Forge + AEGISA lane is a set of patches over the trunk and copies nothing; every read on it composes the trunk as it stands now. Carbon Forge docs | GitHubChanges are proposed from branches through pull requests. GitHub Docs |
| Busy main line | Carbon Forge + AEGISA changeset locks the entities it names and nothing else, so landings in different places never wait on each other. A patch that no longer applies is a named conflict, never a guessed merge. Carbon Forge docs | GitHubA merge queue automates pull request merges into a busy branch and keeps it from breaking on incompatible changes. GitHub Docs |
| History integrity | Carbon Forge + AEGISEvery revision and changeset is hash-chained and, with a key, signed. History moves forward: a revert is a new landing. Carbon Forge docs | GitHubCommits and tags signed locally with GPG, SSH or S/MIME are marked Verified. GitHub Docs |
| Questions without a checkout | Carbon Forge + AEGISGrep, blame, diff, history and symbol lookups run on the server, at a past revision, on a lane or in a snapshot. Carbon Forge docs | GitHubEvery developer works from a full copy of the project and its history. GitHub Docs |
| Code and docs together | Carbon Forge + AEGISCode trees, files, pages and atoms are one record, so a code change and the page that explains it land in one changeset. Carbon Forge docs | GitHubCode lives in a repository; pull requests carry its changes. GitHub Docs |
| Large files | Carbon Forge + AEGISA blob of any size up to 40,000 MiB is uploaded in parts and stored once by its SHA-256. Carbon Forge docs | GitHubGitHub blocks files larger than 100 MiB; Git Large File Storage handles bigger ones. GitHub Docs |
| Agent access | Carbon Forge + AEGISMCP is a primary surface, co-equal with the editor. The full preset holds 166 tools, every tool the server has. Carbon Forge docs | GitHubGitHub hosts a remote MCP server for MCP clients. GitHub |
| Git compatibility | Carbon Forge + AEGISEvery code tree renders to a git history and pushes to GitHub, always fast-forward, so git tooling keeps working. Carbon Forge docs | GitHubGitHub is a git host. GitHub Docs |
| CI/CD | Carbon Forge + AEGISAEGIS workflows build, test, lint and deploy in container steps beside agent steps, on the lane's tree fetched from the record with trees.materialize. By design they run from the Carbon record through the SEAL gateway and its git tools. Carbon Forge docsAEGIS docsCarbon Forge | GitHubGitHub Actions builds and tests every pull request. GitHub Docs |
| Protection before a landing | Carbon Forge + AEGISA protected trunk moves by a lane's landing alone. Landing rules name the approvers each path needs, each approval binds to the lane's exact state, the landing is sealed, and the archive moves fast-forward. Carbon SCM specificationCarbon SCM specificationCarbon SCM specification | GitHubBranch protection rules can require status checks and a linear history before a push. GitHub Docs |
| Agents in the record | Carbon Forge + AEGISAEGIS agents write to a lane through the Carbon MCP endpoint, each with a token scoped to its step, and Zaru calls the Carbon Forge tools you allow. Carbon Forge docsAEGIS docs | GitHubCopilot, GitHub's assistant, and third-party coding agents work in GitHub repositories. GitHub Docs |
Try it on your own work.
Sources, all read on 2026-10-22: Carbon Forge docs, “Source control on the substrate” · GitHub Docs, “About Git” · Carbon Forge docs, “Overview” · GitHub Docs, “Pull requests” · Carbon Forge docs, “Working in lanes” · GitHub Docs, “Managing a merge queue” · GitHub Docs, “About commit signature verification” · Carbon Forge docs, “Code and files on the substrate” · Carbon Forge docs, “MCP tools catalog: Blobs” · GitHub Docs, “About large files on GitHub” · Carbon Forge docs, “MCP tools catalog” · GitHub, “GitHub's official MCP Server” · Carbon Forge docs, “MCP tools catalog: Archives” · Carbon Forge docs, “The full workflow with AEGIS and Zaru” · AEGIS docs, “Building CI/CD Pipelines” · Carbon Forge, “Carbon Forge + AEGIS” · GitHub Docs, “Understanding GitHub Actions” · Carbon SCM specification, “5. Lanes” · Carbon SCM specification, “2. Content addressing and the seal” · Carbon SCM specification, “7. The git archive” · GitHub Docs, “About protected branches” · AEGIS docs, “Zaru Web and AEGIS” · GitHub Docs, “Copilot on GitHub”