lightweight, instantaneous, zero-provisioning git for agents
Lightweight Git Repositories
for Agents
GitFork is lightweight Git built for agent work. A repository exists the
moment git clone runs. Zero provisioning, no dashboard, nothing
to wire up. Seed it from any upstream, push and pull at wire speed. Let it
expire when the work is complete.
demo
Try for yourself.
Initialize a fresh repo and make the first commit.
Clone a brand-new empty repo, add a README.md that says hello, commit, push it back.
$ git clone https://x:demo@gitfork.app/demo/hello-26cfa0.git
how it works
The URL is the API.
Every /:namespace/:repo.git path on gitfork.app is a
live Git endpoint. The first time a client touches one, GitFork materializes
the repository on demand — empty, or seeded from an upstream you name.
Clone to create.
No POST /repos. No API token to mint. An agent runs
git clone https://gitfork.app/<namespace>/<name>.git
and the repo exists.
Seed from anywhere.
Append ?from=github.com/owner/repo on the first clone
and GitFork imports the upstream history as the initial state.
Fork, don't download.
Push, pull, branch, merge.
A GitFork repo is a real Git remote — every plumbing command works. Branches, tags, history, rebase. Your agent's existing Git workflow transfers as-is; there's nothing GitFork-specific to learn.
Expire automatically.
Repos are short-lived by design. Set a ttl on the first
clone and GitFork releases the repo when it lapses — no janitor to
wire up, no stale remotes to chase.
why it exists
Agents don't want a control plane.
Every coding agent eventually needs somewhere to commit. The existing answer is a human-shaped workflow: provision a repo, set up permissions, clone, work, delete, clean up the trail. GitFork collapses that into a single URL.
Zero round-trips.
No create call. No webhooks. No dashboard login. The repo stands up on the first Git request and retires on the last.
Shaped for automation.
Credentials fit in a single Basic-Auth line. Concurrent agents get their own slugs without stepping on each other. No human UI in the critical path.
Built on the edge.
GitFork runs on Cloudflare Workers and Artifacts, so clones are served from the closest region. Upstream fetches happen once, then it's all local.