lightweight · instantaneous · zero-provisioning

Lightweight Git for agents

A repository exists the moment git clone runs. Zero provisioning, no dashboard, nothing to wire up. Seed from any upstream, push and pull at wire speed, let it expire when the work is done.

0round-trips 3scold start 250mswarm clone
▶ try_the_demo → read_the_docs
agent@sandbox  ~
LIVE
$ git clone https://x:demo@gitfork.app/demo/hello-dba095.git
[§01] 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.

01 — clone_to_create
No POST /repos. No token to mint.
An agent runs git clone https://x:demo@gitfork.app/demo/<name>.git and the repo exists. First-byte latency replaces a provisioning step.
$ git clone https://x:demo@gitfork.app/demo/run-4f2.git
02 — seed_from_anywhere
Fork, don't download.
Append ?from=github.com/owner/repo on the first clone and GitFork imports the upstream history as the initial state — at edge speed.
$ git clone https://x:demo@gitfork.app/demo/fork-9c.git?from=github.com/sindresorhus/slugify
03 — push/pull/branch/merge
A real Git remote.
Every plumbing command works. Branches, tags, history, rebase. Your agent's existing Git workflow transfers as-is — nothing GitFork-specific to learn.
$ git push origin feat/retry-logic # wire_speed
04 — expire_automatically
Automatic cleanup.
Pass ttl_absolute for a hard wall-clock deadline, or ttl_activity for a sliding idle timeout that resets on every push or fetch. Either way, GitFork releases the repo itself — no janitor, no stale remotes.
$ git clone https://x:demo@gitfork.app/demo/ephemeral.git?ttl_absolute=2h
[§02] 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 permissions, clone, work, delete, clean up the trail. GitFork collapses that into a single URL.

01 · clone-first

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.

02 · agent-native

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.

03 · fast by default

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.

[§03] get_started
Ready when your
agent is
$ git clone https://x:demo@gitfork.app/demo/hello-558d0d.git
read_the_docs →