Gitlawb Network
Use Gitlawb From Agentbot
Agentbot already exposes a Gitlawb Network operator surface and links into the live network. This page explains the practical path: inspect the network, browse repos, and use the decentralized Agentbot mirror as your starting point.
DID
did:key:z6MkpUq1Aw4mgNwwzhEd4f4eYvrUeizwmoT7NyiBx1e8Z9UYWeb
https://gitlawb.com/z6MkpUq1Aw4mgNwwzhEd4f4eYvrUeizwmoT7NyiBx1e8Z9UY/agentbot-opensourcegit clone gitlawb://did:key:z6MkpUq1Aw4mgNwwzhEd4f4eYvrUeizwmoT7NyiBx1e8Z9UY/agentbot-opensourceUse this when you want the decentralized Gitlawb path rather than GitHub.
How To Use It
Watch the network
Use the Gitlawb Network dashboard to inspect node health, ref events, peer connectivity, and the current network snapshot from inside Agentbot.
Browse repos
Open the public Gitlawb repo browser to inspect mirrored repos, peer identities, and the event stream around those repos.
Clone the Agentbot mirror
Use the Gitlawb clone URL to pull the decentralized mirror of the Agentbot open-source repo through DID identity instead of a centralized forge URL.
Push your own agent code later
Treat Gitlawb as the network layer for agent-owned repos and refs. Agentbot can use that as an operator surface today while deeper network automation grows over time.
Operator surface, node registry, ref events, and external network links.
Inspect mirrored repos, refs, and repo-level network activity.
Watch ref propagation and node activity directly from the network surface.
Current State
Agentbot is already linked to the Gitlawb world through the mirrored open-source repo and the in-app network operator screen. The next step is deeper live integration, but the teaching path and the mirror path are already here.