textgen

oobabooga/text-generation-webui · now at oobabooga/textgen

Open-source desktop app for local LLMs. Text, vision, tool-calling, OpenAI/Anthropic-compatible API. 100% private.

Ship status

Slowed

Last push 31–120 days ago. Quiet, not gone.

Last push
17 Aug 2026
86 days ago
Ship score
29/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 47,722 → 47,730 (29 Sep – 10 Nov 2026)
+1 stars in the 28 days to 10 Nov 2026

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
47.7K
Forks
6K
Open issues
867
Watchers
349
Primary language
Python
Created
21 Dec 2022
Owner
oobabooga · User

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 112 startups in the directory ship primarily in Python.

Topics

This repository has no GitHub topics.

How it got here

What the classifier decided, and when.

Read by Jev, TypeSafe’s classifier, on 22 Sep 2026, which did not call this an open-source startup — it chose a package or library instead, and put os_startup at 23% (self-hostable 93%, hosted offering 16%). The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory. This one is in that queue, waiting for a person — removing a listing is a pull request a human opens.

Listed since the Sep 2025 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: slowed — last push 17 Aug 2026This is the badge for oobabooga/text-generation-webui, as served from the URL below.
[![OSSEAN: slowed](https://ossean.com/badge/oobabooga/text-generation-webui.svg)](https://ossean.com/oobabooga/text-generation-webui)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.