What kinds of modules and data sources does WTF support?

WTF (wtfutil.com) is a personal information dashboard that runs in your terminal, and its module list is broad: it covers developer tooling (Git, GitHub, GitLab, Jenkins, TravisCI), monitoring and on-call services (Datadog, PagerDuty, UptimeRobot, OpsGenie, New Relic), and everyday widgets such as clocks, weather, stocks, crypto prices, and feed readers. Each module appears in the documentation with its own settings, so the practical answer to "what can it show?" is "whatever module you enable and configure in your config file." The condition: you need a terminal environment and a config file where modules are declared; nothing on the site indicates a hosted or browser-based version.

How the module list is organized

The documentation groups modules by purpose rather than by vendor. The main clusters:

The list is long, but the pattern is consistent: each entry is a self-contained module with its own configuration block. You don't get a fixed set of panes — you choose which modules to declare.

What this means in practice

A typical setup mixes one or two work sources with a few ambient widgets. For example, a developer might run GitHub for pull requests, Jenkins for build status, PagerDuty for who's on call, and a clock plus weather in a corner. The grid layout settings control where each module sits, so the dashboard is composed rather than pre-built.

Two things to keep in mind when reading the module list:

• Modules are opt-in. A module appearing in the docs doesn't mean it's active; it must be added to the configuration with its settings. The docs describe per-module settings, but the site excerpt doesn't spell out credential requirements for each service — expect services like GitHub, Jira, or Datadog to need their own access tokens or API keys, and check the individual module page for the exact fields.
• Some modules are read-only views, others are interactive. Feed readers, clocks, and weather are display-only; Todo, Todoist, and GitLab Todo imply you can manage items. The docs list them separately, so treat "can I act on this from the terminal?" as a per-module question.

Choosing modules for your dashboard

Use the clusters above as a checklist against your actual day:

1. Work queue — pick the one or two systems where tasks actually land for you (GitHub/GitLab issues, Jira, Trello, Asana).
2. Build and deploy health — Jenkins, TravisCI, CircleCI, or BuildKite, whichever your team uses.
3. Incidents — PagerDuty, OpsGenie, or VictorOps, plus UptimeRobot or Healthchecks for uptime.
4. Ambient context — clock, weather, stocks, crypto, or a feed reader for the corners of the grid.

If a service you rely on isn't in the list, the docs include a "Creating New Modules" section under Development, which is the documented path for extending the dashboard rather than waiting for built-in support.

The short version: WTF's value is the breadth of its module catalog combined with terminal-native display — you assemble the dashboard from documented modules, each configured individually, and the site's module index is the authoritative place to confirm a specific integration exists before you plan around it.