Add shopify doc fetch command to download MD doc from shopify.dev

[nelsonwittwer]

What

Adds shopify doc fetch --url <url>, which downloads a complete document from shopify.dev and prints it to stdout (or writes it to a file with --output).

This is part of the new doc namespace for documentation tooling — the "full document" half. The "discovery" half is doc search (#7770).

Why

Every page on shopify.dev has a Markdown representation. doc fetch requests that representation, giving agents (and scripts) a clean, verbatim way to pull instructional content from the centralized docs — for example, a set of instructions an agent follows like a centrally-served skill.

Details

• shopify doc fetch --url <url> — requests the Markdown version of the page.
• --output <path> (-o) — write to a file instead of stdout.
• Only shopify.dev (and subdomains) URLs are allowed; malformed/disallowed URLs and non-ok responses throw before any output.

shopify doc fetch --url https://shopify.dev/docs/api/shopify-cli
shopify doc fetch --url https://shopify.dev/docs/api/shopify-cli --output docs/shopify-cli.md

🎩 Testing instructions

doc fetch hits a public endpoint on shopify.dev — no auth, no app, no login required. It just needs network access.

# 1. Check out this branch and build (dev.js runs the prebuilt bundle, so a build is required)
cd <your cli checkout>
git checkout add-fetch-doc-command && git pull
pnpm nx build cli

Run commands from the repo root via node packages/cli/bin/dev.js …:

1. Fetch a real page → prints Markdown to stdout

node packages/cli/bin/dev.js doc fetch --url https://shopify.dev/docs/api/shopify-cli | head -20
#   → Markdown content of the page

2. --output writes to a file (creating missing parent dirs)

node packages/cli/bin/dev.js doc fetch --url https://shopify.dev/docs/api/shopify-cli --output /tmp/doc-fetch/cli.md
head -5 /tmp/doc-fetch/cli.md
#   → "Saved …" message, and the file exists with the Markdown content

3. Disallowed host → rejected before any network call

node packages/cli/bin/dev.js doc fetch --url https://example.com/whatever
#   → "Only documents from the following hosts can be fetched: shopify.dev."

4. Malformed URL → rejected

node packages/cli/bin/dev.js doc fetch --url not-a-url
#   → "Invalid URL: not-a-url"

5. Non-ok response surfaces status

node packages/cli/bin/dev.js doc fetch --url https://shopify.dev/this-page-does-not-exist-xyz
#   → "Failed to fetch …: 404 Not Found"  (exit non-zero)

6. Required arg + help

node packages/cli/bin/dev.js doc fetch          # → "Missing required flag url"
node packages/cli/bin/dev.js doc fetch --help   # → usage, description, examples, --output flag

Inspecting the Monorail analytics payload

This branch is rebased on the app-context telemetry PR (#7771), so every command emits a command-analytics event. To see exactly what would be sent to Monorail — without sending it — set two env vars:

• SHOPIFY_CLI_NO_ANALYTICS=1 — dump the payload via debug logging instead of POSTing it.
• SHOPIFY_FLAG_VERBOSE=1 — raise the log level so the debug line prints.

SHOPIFY_CLI_NO_ANALYTICS=1 SHOPIFY_FLAG_VERBOSE=1 \
  node packages/cli/bin/dev.js doc fetch --url https://shopify.dev/docs/api/shopify-cli 2>&1 \
  | grep "Skipping command analytics"
#   → a "Skipping command analytics, payload: {…}" line with "command": "doc fetch"

To confirm the inherited app-context hook, run the same command from inside an app directory while logged in — the payload then also carries app-level identifiers (api_key, project_type, app_*). Run it from a non-app directory and those fields are absent.

Notes

• @shopify/cli: minor.
• Lives under the doc topic (commands/doc/fetch.ts, registered as doc:fetch); adds a doc topic description.
• Generated artifacts regenerated (oclif manifest, README, dev-docs interface, e2e command-tree snapshot).
• Rebased on telemetry-app-context-everywhere (Capture app context in analytics for every command run inside an app #7771), so it inherits the app-context telemetry hook automatically.

Related

• Add doc search command (JSON documentation search) #7770 — doc search (JSON documentation search).
• Deprecate and fix search #7778 — deprecates the old browser search command, pointing users to doc search.

🤖 Generated with Claude Code

[github-actions]

Differences in type declarations

We detected differences in the type declarations generated by Typescript for this branch compared to the baseline ('main' branch). Please, review them to ensure they are backward-compatible. Here are some important things to keep in mind:

• Some seemingly private modules might be re-exported through public modules.
• If the branch is behind main you might see odd diffs, rebase main into this branch.

New type declarations

We found no new type declarations in this PR

Existing type declarations

packages/cli-kit/dist/public/node/session.d.ts

@@ -47,6 +47,22 @@ export declare function isUserAccount(account: AccountInfo): account is UserAcco
  * @returns True if the account is a ServiceAccount.
  */
 export declare function isServiceAccount(account: AccountInfo): account is ServiceAccountInfo;
+/**
+ * Reports whether the CLI already has stored credentials, without prompting the
+ * user, opening a browser, or making any network request.
+ *
+ * This is a passive, side-effect-free check: it reads the local session store and
+ * returns  when at least one valid session is present. Unlike the
+ *  functions, it never triggers a login flow and never logs
+ * the user out. Because it does not contact the network, it cannot tell whether the
+ * stored token is currently valid/unexpired — only that credentials exist locally.
+ *
+ * Intended for best-effort, opportunistic behaviour (for example, enriching
+ * telemetry only for users who are already logged in).
+ *
+ * @returns True if local credentials exist, false otherwise.
+ */
+export declare function sessionExists(): Promise<boolean>;
 /**
  * Ensure that we have a valid session with no particular scopes.
  *