← All blog posts

Product update

ForkMesh Forever: a full-song tour through the mesh

We turned the first-party “ForkMesh Forever” track into a 2:27 product journey. Follow one developer from discovering a repository to mirroring it, cloning through the mesh, creating signed collaboration, and directing supervised agents in the Office.

July 28, 2026Product update4 min read2:27 video
Read the film’s visual transcript

0:00–0:14 A developer enters a luminous distributed World as the message “Code should outlive any one host” introduces local-first source preservation.

0:14–0:31 The developer discovers ForkMesh on a late-night screen, walks through Town Square, and enters a repository portal built around people and projects.

0:31–0:46 Git branches, commits, reviews, and release context travel with the repository instead of being trapped in one hosted database.

0:46–0:59 In the desktop app, the developer adds a remote clone URL. A full Git mirror lands locally and the machine becomes a current node in the mesh.

0:59–1:11 The public network map distinguishes live mirrors, unavailable hosts, and catalog stubs so the developer can see what is actually reachable.

1:11–1:19 A clone keeps the public ForkMesh URL while Git bytes move over HTTPS from an eligible, healthy, integrity-matching mirror.

1:19–1:35 The developer opens a signed issue and pull request. Authorship and collaboration events remain verifiable as the work moves with the code.

1:35–1:43 A source-attested refs digest lets a client confirm that a mirror matches the history the source published before relying on it.

1:43–1:55 In the Office, the developer gives bounded issues to Codex and Claude Code, sees questions and activity, and remains responsible for review and merge.

1:55–2:07 Multiple supervised agents work in isolated worktrees. Their results converge as reviewable changes rather than silently modifying the developer’s working tree.

2:07–2:17 More independent, current mirrors reduce reliance on any one host while the film repeats the experimental-status and backup guidance.

2:17–2:26 Connected nodes surround the closing invitation: run a node, mirror a repository, and help keep code available.

The lyric captions are a reviewed timed transcription of the first-party recording, not artist-published lyrics. The sung word at 2:11 can be heard as either “note” or “node”; the caption follows the song’s keyboard metaphor.

“ForkMesh Forever” begins at a late-night screen and ends with independent nodes glowing across the World. Between those beats, the film maps out the core ForkMesh journey: discover a project, mirror its Git repository, bring a node online, clone from an eligible origin, open a signed issue and pull request, and review agent work before merge.

A journey, not a feature reel

The twelve lyric-aligned chapters keep one developer in motion. Town Square introduces the network. A repository portal becomes a local mirror. The public network distinguishes healthy mirrors from stubs and offline hosts. The Office turns an issue into bounded agent work, visible questions, a reviewable diff, and an explicit human merge.

The song supplies the story while the interface explains what each moment means: one independently operated node can hold a real replica, more current mirrors can improve resilience, and collaboration can travel with the repository instead of belonging only to one hosted account.

What actually moves through the mesh

ForkMesh World makes the system legible, but it is not the Git transport. Repository bytes travel over ordinary HTTPS. The coordination layer handles signed discovery, health checks, integrity metadata, and bounded routing; it is not canonical Git object storage. Real replicas remain on independently operated desktop and headless nodes.

A clone still depends on at least one eligible, current, healthy, integrity-matching mirror being reachable. The film uses that precise model rather than promising that every repository is always online.

Portable work, explicit control

Issues and pull-request events are signed so authorship and changes can be verified. Accepted collaboration can become part of portable, repository-backed history. Codex and Claude Code work in isolated worktrees, while the developer sees questions and transcripts, reviews the result, and decides whether to merge.

Captured from ForkMesh World

The World action plates were recorded from the working local Three.js implementation with deterministic scene fixtures. Product labels, diagrams, timed lyric captions, and motion graphics were then composed around those captures. It is a directed product explainer, not live production telemetry or an availability proof.

ForkMesh remains experimental. Keep independent backups, inspect the code, and verify mirror health and integrity before relying on any replica.

Run a node. Mirror a repo. Keep code available.

Enter ForkMesh World, read the documentation, or get the desktop app and start with a repository you care about.