Discofork
Repository brief

microsoft/terminal

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-29T22:27:17.406Z
3mo ago

microsoft/terminal

microsoft/terminal is an active, high-traffic Windows command-line UI repository that contains Windows Terminal, Windows Terminal Preview, the legacy Windows console host, shared components, ColorTool, and sample projects. It is well-established rather than archived, with very large adoption signals (102,412 stars, 9,167 forks) and recent commits as of 2026-03-27. Forks are likely interesting if you care about Windows terminal UX, console internals, or shared Windows command-line tooling.

GitHub
Loading tags...
Stars102,412
Forks9,167
Default branchmain
Last pushed2026-03-28T01:32:15Z
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

6 of 6 fork briefs
Selected

Choose this fork only if you specifically want its README customization; otherwise upstream is the better default because it is much more current and actively maintained.

Choose this fork only if you want its specific downstream modifications and are willing to own long-term merge and maintenance debt. If you want current Windows Terminal behavior, upstream is the safer default.

Choose this fork if your goal is a legacy conhost-focused codebase and you are willing to own substantial divergence from upstream. Do not choose it if you need the modern Windows Terminal product, upstream parity, or an actively preserved test and packaging pipeline.

Choose this fork only if you want a customized, experimental Windows Terminal base and are prepared to maintain your own branch. If you want a current, low-risk terminal distribution, upstream is the better default.

Prefer this fork only if you want a custom, self-owned Windows Terminal base and are prepared to maintain it. If you want current Windows Terminal behavior with lower maintenance burden, upstream is the better choice.

Choose this fork only if its added settings/architecture changes match a specific need; otherwise upstream is the safer default because it is much more active and less divergent.