Tangled relaunches as a federated Git forge where issues and pull requests live in the repository

Discussion that travels with the repository

Tangled's launch post argues that centralised forges leave teams dependent on one company's uptime and stewardship, while email and Git have lasted far longer. Tangled calls itself "the first truly federated code forge" on the AT Protocol: users can self-host selected parts such as Git hosting or CI runners, or the whole stack, and still collaborate with everyone else.

The release splits the backend. A read-only in-memory indexer called bobbin runs in more than 11 regions and feeds a Svelte frontend at the edge, and Knot2, a Rust rewrite of the git server, bundles an SSH server. Issues, PRs and comments now live on the knot as chains of Git objects, with an attestation record written to the user's own PDS. Organizations are passwordless AT Protocol accounts, and stacked PRs work for Git and Jujutsu with interdiffs. Private repos, a CLI and SDKs are staggered launches.

First reports from users

Tangled's co-founder and CEO said private repos roll out in the next couple of weeks. Two users brought concrete gaps. One with a SHA-256 repository asked when it will be supported, noting "Git 3 is moving to SHA256 anyway". A user who compared the old and new review UI said the new one is "much better, but "Comments" section without a "Comment" button is unforgivable."

For anyone weighing a move off GitHub, those are the two checks to run first: your repo's hash format and the review flow.