Discofork
Repository brief

charmbracelet/bubbletea

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-30T16:01:32.096Z
1mo ago

charmbracelet/bubbletea

Bubble Tea is a widely used Go TUI framework for building terminal apps with The Elm Architecture. It is active, not archived, and appears well-maintained, with frequent recent commits and a large contributor/fork ecosystem. Forks are likely most interesting if you care about terminal UI tooling, renderer/input handling, or examples/tutorials around Go-based TUIs.

GitHub
Loading tags...
Stars41,064
Forks1,150
Default branchmain
Last pushed2026-03-30T09:11:33Z
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

10 of 10 fork briefs
Selected

Prefer upstream unless you specifically need this older snapshot; this fork adds no visible functionality and is far behind current Bubble Tea.

Prefer upstream unless you specifically want the project/config navigator example; this fork is mainly a small example add-on and is far too stale to serve as a general Bubble Tea base.

Choose upstream unless you specifically need this fork's legacy behavior or internal customizations. For new work, the fork's age and divergence make it a high-risk foundation; for legacy maintenance or experimentation, it may still be useful as a frozen reference.

Prefer upstream unless you specifically need this old, frozen snapshot. This fork adds no concrete capabilities and is materially behind on fixes, examples, dependency updates, and renderer work, so it is a poor choice for new adopters.

Choose this fork only if you need its legacy behavior or function-key customization and are willing to own the maintenance burden. For most new work, upstream is the safer default.

Prefer upstream unless you specifically need this older fork's example set or legacy behavior. For new work, the fork is too stale and too far behind to be a safe default.

Choose upstream unless you specifically need this fork’s legacy rendering/input behavior or are maintaining existing code already built against it. For new work, the fork looks too stale and too far behind to be the safer base.

Prefer upstream unless you specifically need this exact snapshot; the fork adds no visible features and is already behind upstream.

Choose this fork only if you specifically want a private, near-upstream copy. If you want active downstream improvements, this fork currently offers no visible advantage over upstream and is already lagging behind it.

Prefer upstream unless you specifically need this exact older snapshot. This fork adds no visible features and is materially behind, so it is only attractive as a frozen base for custom work.