weather app for the terminal
8.5k
Stars
506
Forks
15
Open issues
30
Contributors
AI Analysis
wego is a terminal weather client written in Go that displays forecasts with multiple visualization and data source options. It serves developers and terminal enthusiasts who prefer command-line interfaces and want lightweight weather information without leaving their shell. Best suited for Linux/Unix users and CLI-first workflows; not intended as a replacement for graphical weather apps.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
wego: a mature, composable terminal weather client with multiple backends and frontends
wego is a terminal-based weather forecast tool written in Go that fetches and displays multi-day weather data in a configurable ASCII/emoji/markdown/JSON format. It targets developers, sysadmins, and power users who prefer staying in the terminal. Its plugin-style architecture supports eight weather backends and four frontends, including free keyless options (Open-Meteo, SMHI). The JSON composability feature makes it scriptable. It has been maintained for over a decade, is packaged in multiple Linux distributions, and has accumulated ~8,500 stars, indicating a stable, well-regarded niche tool.
Created in November 2014, wego predates many similar tools and likely inspired the broader terminal-weather genre. It has evolved from a single-backend tool to a multi-backend, multi-frontend system over roughly 12 years.
Growth was driven largely by organic discovery from developer communities (Reddit, Hacker News, dotfiles culture) and word-of-mouth among terminal enthusiasts. Stars accumulate slowly now (~6/week) reflecting a settled niche rather than viral growth. The project is mature and no longer in rapid expansion.
Packaged in multiple Linux distributions (evidenced by the Repology badge in the README), which provides a concrete signal of ecosystem integration. Used by terminal power users and dotfile sharers. Adoption not verified at enterprise or large-scale production level — this is a personal productivity tool by nature.
Appears to use a backend/frontend plugin architecture where data acquisition (backends) and rendering (frontends) are separated. The JSON pipeline capability suggests a clean interface contract between components. Likely structured as a Go CLI application with per-backend and per-frontend packages. Config management is handled via the 'ingo' library.
Not documented in README.
Last push was 2026-06-02, approximately 25 days before the evaluation date — indicating active maintenance. The project has been continuously maintained since 2014 with no apparent abandonment periods based on metadata. README is thorough and up-to-date with modern backends like Open-Meteo and PirateWeather.
ADOPT IF: you live primarily in a terminal, want a locally-installed weather tool with multiple backend choices, disk caching, and JSON composability for scripting. AVOID IF: you need weather data in a non-terminal context, do not want to manage an API key (though Open-Meteo is free and keyless), or need real-time weather rather than forecasts. MONITOR IF: you rely on a specific backend (e.g., WorldWeatherOnline, which no longer offers free keys) and want to ensure continued support.
Independent dimensions
Mainstream potential
2/10
Technical importance
4/10
Adoption evidence
4/10
- Third-party weather API backends can disappear, change terms, or require payment, potentially breaking functionality without notice (WorldWeatherOnline already dropped free keys).
- The project's niche audience limits external contributor pressure, meaning maintenance depends heavily on the primary author's continued interest.
- No documented test coverage may mean regressions when backends update their response formats.
- Requires a UTF-8 terminal with 256 colors and a compatible monospaced font — setup friction in constrained environments (e.g., older servers, Windows without WSL).
- Go 1.20+ dependency means older system Go installations may need upgrading, a minor but real friction point for some users.
wego will likely remain a stable, slowly maintained niche tool for terminal enthusiasts. It is unlikely to grow significantly beyond its current audience but equally unlikely to be abandoned given 12 years of consistent maintenance.
Explore similar
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- Go
- License
- ISC
- Last updated
- 1w ago
- Created
- 142mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
weather prediction app
Provide API Key in a Separate File
Feat: `auto` location option using public IP
Request: Location cache
Bug/Enhancement: Visibility, Sunrise, Sunset data returned by OpenWeatherMap is not captured in by json frontend
Top contributors
Recent releases
Similar repos
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
schachmat/wego
this
|
8.5k | +2 | Go | 8/10 | 1w ago |
 Veirt/weathr
|
2.9k | — | Rust | 7/10 | 2mo ago |
 chubin/wttr.in
|
30.1k | — | Go | 8/10 | 2d ago |
 fcambus/ansiweather
|
1.9k | — | Shell | 7/10 | 6mo ago |
 gizak/termui
|
13.6k | — | Go | 7/10 | 12mo ago |
 wezterm/wezterm
|
27.5k | — | Rust | 8/10 | 3d ago |
wttr.in is a web service (curl-friendly) with ~3.5x more stars. It requires no local installation and no API key, making it more accessible for casual use. wego offers deeper customization, local caching, more frontend options, and offline/JSON composability — better for persistent local workflows.
WTF is a broader terminal dashboard that includes weather as one module among many. wego is a dedicated, composable weather tool. Users wanting just weather with more backend choice and scriptability would prefer wego; those wanting an all-in-one dashboard would lean toward WTF.
termui is a terminal UI rendering library, not a weather tool. Not a direct competitor — wego could theoretically use such a library internally, but serves a different audience entirely.
go-pretty is a table/text rendering library for Go, not a user-facing weather tool. Not a direct competitor.
