repo.box

Problem Statement

AI agents are writing production code, but Git hosting permissions are still human-first and too coarse. In typical setups, a token gives broad repo access. You cannot cleanly express: "this agent can edit docs, but not contracts" or "this agent can push to feature branches, never merge main". Agent identity is also weak in most workflows: shared bot credentials blur authorship, auditing, and accountability. Permissions should be files — readable by both humans and agents, diffable in Git history, and enforceable at command time. repo.box solves this with repo-local policy (`.repobox/config.yml`), EVM-signed identities, and server-side verification. Because identities are wallets, the model composes directly with on-chain primitives (x402 paid access, token-gated reads, and claim-based reward flows) without introducing a parallel auth stack.