# HubSpot CLI changelog (/en/docs/hubspot/changelog)

Notable changes to `@wirecat/hubspot-cli`. One section per version, newest first.

## 0.4.0 — 19.11.2026 [#040--19112026]

### Changed — may break callers [#changed--may-break-callers]

- **`deals.write`, `people.write` and `organizations.write` are gone.** They stopped only the `api` path, so
  `deals.write: deny` still let `deals update` through. An `api` write on deals, contacts or companies now checks the
  key of the command that does the same (`deals.update`, `people.create`), as amoCRM and b24 do, and a merge
  checks `<group>.update`. So a raw deal, contact or company write goes ahead as its command does, and deletes still
  ask. Watch for: a setting that names one of the three old keys no longer matches anything: set
  `deals.update`, `deals.create` or the group key `deals` instead.

### Fixed [#fixed]

- **A read denied on a CRM command is denied through `api` too.** `config set permissions.people deny` stopped
  `people list` but not `api contacts-list`, which read the same contacts. Each raw read now checks the key of the
  command that reads the same records: `people`, `organizations`, `deals`, `leads`, `activities`, `users`, `pipelines`,
  `stages` and `fields`. See [permissions](/llms.mdx/docs/hubspot/permissions/content.md).

## 0.3.2 — 19.11.2026 [#032--19112026]

## 0.3.1 — 19.11.2026 [#031--19112026]

### Fixed [#fixed-1]

- **Notes, meetings and tasks read as clean text.** HTML codes such as `&#8217;` and `&mdash;` become the characters
  they stand for, and style blocks are left out, so search finds the words. Before, only six codes were decoded.
- **HubSpot's daily limit says "do not retry" on every path.** The CRM commands called it retryable while `api` did
  not, so an agent could retry for hours.
- **`session start --help` no longer says hubspot changes nothing.** Writes shipped in 0.2.0.

## 0.3.0 — 18.11.2026 [#030--18112026]

### Changed — may break callers [#changed--may-break-callers-1]

- **The MCP Registry entry asks which profiles to serve.** It started `mcp serve --profiles all`, so a client that
  installed the server from the registry reached every account on the computer without the owner choosing. Now
  `--profiles` is a required argument with the example `personal`: the client asks for one profile, a
  comma-separated list or `all`. Why: a CLI never picks an account for the owner
  ([WC-MCP-9](https://github.com/WireCatLabs/cli-base/blob/main/docs/standards/mcp.md#wc-mcp-9--a-server-serves-the-profiles-it-is-told-with-one-connection-for-each)). Watch for: a client set up from the old entry keeps `--profiles all` until it is set up again; a
  server added by hand or with `mcp config` does not change.

### Fixed [#fixed-2]

- **`mcp serve` starts on a computer with no profile yet.** It lists its tools, and each call answers with the command
  that sets up a profile. Before, the server stopped at start, so a directory that checks servers could not list
  them. From cli-core 0.699.0.

## 0.2.0 — 17.11.2026 [#020--17112026]

### Added [#added]

- **`deals create`, `update`, `move`, `close` and `delete` change deals in HubSpot, and the copy takes each answer.**
  `close` moves a deal to its pipeline's closed won or lost stage and keeps `--reason` as HubSpot's closed reason.
  `delete` archives the deal and asks first. See [usage](/llms.mdx/docs/hubspot/usage/content.md).
- **`people create|update` and `organizations create|update` change contacts and companies.** A contact keeps one
  e-mail and two numbers, a company one number and no e-mail; a longer list is refused before anything is sent.
- **`api` offers HubSpot's writes and deletes too: 66 writes and 33 deletes of the CRM API, version 2026-03.** Each
  write checks `api.<command>` and its group's `<group>.write`, each delete its `<group>.delete`, and both ask by
  default. A write that does what a command does checks that command's key too (`deals.update`), a body that sets a
  deal's stage checks `deals.move` and `deals.close`, and one that sets an owner checks `crm.assign-others`, `deny` by
  default. `api contacts-gdpr-delete` also checks `people.erase`, to deny erasing alone. `--dry-run` names every key.
  See [settings](/llms.mdx/docs/hubspot/configuration/content.md#permissions).
- **Write scopes are optional.** The setup and [installation](/llms.mdx/docs/hubspot/installation/content.md#make-a-key) list
  `crm.objects.{deals,contacts,companies}.write`; without them the key only reads.

### Fixed [#fixed-3]

- **`api` sends the key with every operation.** HubSpot's object specs mark 115 operations as needing no sign-in, so
  in 0.1.0 `api deals-get`, `api contacts-list` and the other record operations went out without the key and HubSpot
  answered 401. The pipelines, properties, owners and account operations were not affected.

## 0.1.0 — 17.11.2026 [#010--17112026]

### Added [#added-1]

- Started from `@wirecat/cli-template` 0.25.0.
- **`session start` signs a profile in with a HubSpot service key or a private app token.** The key is read hidden or
  from stdin, never as an argument, checked against the account, and kept in the keyring with the account's id. A
  second profile on the same account is refused. `WCHUBSPOT_TOKEN` works in CI beside `WCHUBSPOT_ACCOUNT`, the
  account's id. See [installation](/llms.mdx/docs/hubspot/installation/content.md).
- **`sync` copies the account's CRM into WireCat's shared store.** Deals, contacts, companies, leads (Sales Hub
  Professional or Enterprise), owners, pipelines and properties, and the notes, calls, e-mails, meetings and tasks
  once the activities setting is on. `deals list`, `pipelines`, `changes list` and `search all` then answer offline. A
  key names no user, so every profile reads the whole copy: filter by `owner:<owner id>`, not `owner:me`.
- **`people`, `organizations` and `users` read contacts, companies and owners live from the account.**
- **`api` offers every read operation of HubSpot's CRM API, version 2026-03, from its 15 specs.** One command per
  operation, each with its own permission key. This release only reads: the API's writes are not offered, and
  `api show` on one says so.
- **A spent daily allowance ends the request at once and says when it comes back.** HubSpot shares one daily
  allowance among every app on the account. `hubspot` reports `hubspot.daily-limit` with the wait to the account's
  midnight, and stops every process on the account from asking again before then. The ten-second limit is waited
  out.
- **`WCHUBSPOT_ACCOUNT` is checked against `WCHUBSPOT_TOKEN` before anything is written.** A `sync` with an id of
  another account stops with `account.mismatch`, naming both ids, so one account's CRM is never filed under another's.
  `session status --check` with the token alone prints the id to set. See
  [troubleshooting](/llms.mdx/docs/hubspot/troubleshooting/content.md).
