Most problems announce themselves in the header line, next to the status LED. Here's what the common ones mean and the shortest way out of each.
Your token expired or was revoked, or the password changed. Press A to reopen the connect form as "Reconnect to GoCD", enter the new credential, and you're back in, no quitting, no hand-editing the config file.
Running with env vars? Remember GOCD_TOKEN / GOCD_PASSWORD override the file, so a stale exported value will keep producing 401s even after you reconnect.
The LED turns red and the header shows the error, but nothing goes blank: the last loaded dashboard stays fully browsable from the disk cache, so you can still navigate the tree and read cached history.
You don't need to do anything to recover. The app re-polls every poll_interval_secs (30 seconds by default), so as soon as the VPN or network comes back, the next poll succeeds and the view refreshes on its own. Press r if you want to retry immediately.
Your GoCD server uses a self-signed or internal-CA certificate. Press A and choose Yes at the "Skip TLS certificate verification?" step of the connect form, or launch with GOCD_INSECURE=1.
The deployed-commit check works unauthenticated for public repos (rate-limited), but a private repo needs credentials. Press @ and paste a GitHub personal access token with read access to the repo, or export GITHUB_TOKEN before launching. Until then it shows this soft hint rather than an error.
No comparison shown at all? That's expected when the pipeline's latest run has no direct Git material, for example when it's triggered by an upstream pipeline.
The very first load has no cache to lean on and has to pull the whole dashboard once. Gzip keeps that reasonable (2–4 seconds on a 2,389-pipeline instance), and the client allows up to 45 seconds for slow links. Every launch after that paints instantly from the disk cache while refreshing in the background.
It isn't; it starts fully collapsed on purpose, since hundreds of expanded groups would be unusable. Move onto a group and press l or enter to expand it, or press / and type a few characters to fuzzy-filter across everything at once.
| Path | Contents | Safe to delete? |
|---|---|---|
~/.config/lazygocd/config.toml | Server URL, credential, TLS choice, poll interval, optional GitHub token (mode 0600) | Yes; the connect form reappears on next launch |
~/.config/lazygocd/dashboard_cache.json | Last successful dashboard load | Yes; the next launch just waits for the network once |
~/.config/lazygocd/favorites.json | Starred pipeline names | Yes; you lose your stars |
Deleting all three is a full reset. Env vars (GOCD_URL, GOCD_TOKEN, ...) still override whatever the files say; see the quickstart.