diff --git a/tia.md b/tia.md
index b6e06a8..5f8c369 100644
--- a/tia.md
+++ b/tia.md
@@ -106,7 +106,7 @@ Recording the baseline is the one job where `--tia` belongs on CI. It should liv
 
 Baseline fetching is opt-in. You may enable it with `--tia --baselined` on the command line, the `PEST_TIA_BASELINED=1` environment variable, or — preferred for teams — by calling `pest()->tia()->baselined()` in `tests/Pest.php`. Once enabled, when Pest detects no local graph (or the local graph is out of date) it uses GitHub's CLI to download the latest successful run of a `tia-baseline.yml` workflow's `pest-tia-baseline` artifact. Pest then validates the fetched graph against your project state — if it matches, it is adopted. Otherwise, it is discarded and a local rebuild proceeds.
 
-> **Note:** Baseline fetching relies on the [GitHub CLI](https://cli.github.com/) (`gh`), so it is only available for repositories hosted on GitHub, and `gh` must be installed and authenticated (`gh auth login`) on the machine doing the fetch. When a fetch cannot proceed — missing CLI, no authentication, a network or rate-limit error, or no baseline artifact yet — Pest reports the reason and falls back to recording a local baseline.
+> **Note:** Baseline fetching relies on the [GitHub CLI](https://cli.github.com/) (`gh`), so it is only available for repositories hosted on GitHub or on GitHub Enterprise Server, and `gh` must be installed and authenticated on the machine doing the fetch. Pest reads the host from your `origin` remote: authenticate github.com with `gh auth login`, and an Enterprise Server host with `gh auth login --hostname your-ghe-host` — until you do, Pest records a local baseline instead of fetching one. When a fetch cannot proceed — missing CLI, no authentication, a network or rate-limit error, or no baseline artifact yet — Pest reports the reason and falls back to recording a local baseline.
 
 Here is a starter workflow you may drop into `.github/workflows/tia-baseline.yml`: