Claim: "The CLI's purpose is to build and deploy apps to HubSpot and develop on the HubSpot CMS with version control — scoping it to dev assets and CMS, not CRM records."
Verdict: REFUTED (the "not CRM records" scoping is false)
Source 1 (primary cited) — CLI commands overview
https://developers.hubspot.com/docs/developer-tooling/local-development/hubspot-cli/reference (the cited /docs/cms/... URL redirects here) Quote: "The HubSpot CLI connects your local development tools to HubSpot, allowing you to build and deploy apps to HubSpot, develop on the HubSpot CMS with version control, integrate with your favorite text editor, and more." Note the "and more" — this is a non-exhaustive marketing summary, NOT a scope boundary.
Source 2 (refutation) — Custom object CLI commands (CRM data)
https://developers.hubspot.com/docs/developer-tooling/local-development/hubspot-cli/commands/custom-object-commands
Last modified February 9, 2026.
The CLI manages CRM custom objects directly:
- hs custom-object fetch <name> <dest> — fetch a custom object schema
- hs custom-object fetch-all <dest> — fetch all custom object schemas
- hs custom-object update --path=definition — update a schema
- hs custom-object delete <name> — delete a schema
- hs custom-object create <name> --path=definition — create a new custom object
Custom objects are CRM data objects. The CLI therefore does operate on CRM
schema/records, contradicting the claim's "not CRM records" scoping.
Also: hs manages HubDB tables, sandboxes, secrets, accounts.