Run the local fork-analysis CLI, then browse cached repo briefs on the web.
Discofork.ai has two jobs: give people a dead-simple install path for the local CLI, and render cached repository brief pages at routes like `/openai/codex` once backend data exists.
The installer bootstraps Bun when needed, downloads Discofork, installs runtime dependencies, and creates a local `discofork` launcher. After that, you run analysis locally with `gh`, `git`, and `codex`.
Paste owner/repo, a GitHub repo URL, or a Discofork repo URL to jump straight into the cached brief or queue a fresh analysis.
Run Discofork locally.
The CLI does the real work: discovering forks with `gh`, comparing them with `git`, and interpreting the results locally with `codex`.
Swap the host and read the brief.
Replace `github.com` with `discofork.ai` for a repo route. If cached data exists, the page renders it. If not, the frontend shows a pending state until backend processing catches up.
- Installs Bun automatically when it is missing.
- Downloads Discofork into `~/.local/share/discofork`.
- Creates a `discofork` launcher in `~/.local/bin`.
- Warns if `git`, `gh`, or `codex` are still missing.
- Discofork analysis still runs locally and depends on Bun, `git`, `gh`, and `codex`.
- This web app reads cached briefs through its backend and queues missing repos for worker processing.
- The `/repos` page lists everything currently stored in Postgres.
Starter repos for first-time visitors
Use a few recognizable repositories to explore Discofork before your own local history or backend cache has warmed up.
Agentic coding from the terminal, with a repo route that makes Discofork's cached summary useful immediately.
Another agent-oriented coding repo that helps visitors compare workflow trade-offs quickly.
A familiar high-signal repo for testing cached briefs, summaries, and queue behavior.
Useful for seeing how Discofork handles a fast-moving runtime with lots of forks and stars.
Top cached repositories by star count.