Discofork
Repository brief

oobabooga/text-generation-webui

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T11:52:34.166Z
3mo ago

oobabooga/text-generation-webui

oobabooga/text-generation-webui is the original local LLM web UI: a Gradio-based interface for running models fully offline. It covers text generation, vision, tool-calling, training, image generation, file attachments, and an OpenAI/Anthropic-compatible API. The repo is very active and widely forked, so forks may be interesting if they add niche integrations, UI changes, or backend/model support on top of an already broad base.

GitHub
Loading tags...
Stars46,378
Forks5,905
Default branchmain
Last pushed2026-03-30T01:51:10Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

9 of 9 fork briefs
Selected

Choose this fork only if its custom memory/chat direction is the point. For most users, upstream is the safer choice because it is active, much newer, and materially broader in supported features.

Prefer the upstream project unless you specifically need this older frozen snapshot; the fork offers no demonstrated added capability and is far behind on maintenance.

Prefer upstream unless you explicitly need this fork’s older UI conventions or specific 2023 compatibility tweaks. This fork looks attractive only for legacy deployments and niche extension/workflow preferences; for new installs, the active upstream is the safer choice.

Choose this fork only if you specifically need its older custom behavior. For most adopters, upstream is the better choice because this fork is far behind, diverged, and likely missing major newer capabilities.

Choose this fork only if your goal is a lightweight Colab launch path. For anything that depends on current upstream features, fixes, or long-term maintenance, the main oobabooga repository is the safer choice.

Choose this fork if your priority is keeping older ExLlama/GPTQ-based setups alive. Choose upstream if you want the broadest current feature set, ongoing fixes, and lower compatibility risk.

Choose this fork if your priority is Intel GPU support and IPEX-LLM-specific performance tuning. Choose upstream if you want the broadest feature set, newest fixes, and maximum compatibility across backends.

Do not adopt this fork for new work unless you specifically need its exact historical state; it offers no visible additions over upstream and is substantially behind on maintenance.

Prefer upstream unless you specifically need this exact older snapshot. This fork adds no visible capabilities and is far enough behind that it is mainly useful as an archival mirror, not as the better day-to-day adoption choice.