Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions cspell.json
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@
"Antiloop",
"Cognee",
"Deepgram",
"Vibecode",
"Idial",
"Issabel",
"Sangoma",
Expand Down
14 changes: 7 additions & 7 deletions docs/release-notes-review.json
Original file line number Diff line number Diff line change
Expand Up @@ -36,10 +36,10 @@
"conclusion": "Reviewed WhatsApp v0.30.0 to v0.38.0 from the changelog and the source diff. wa now asks WhatsApp at most 20 times a minute per profile, 10 at once (was 60 and 20), and `messages sync <chat>` asks the phone for a page every 5 to 10 seconds; `--pause` of `messages download --all`, `attachments download` and `store gaps repair` defaults to 5s. `session start` waits for the phone's own signal that its history sync is done (five minutes of quiet at most), `session start phone --json --answer-stdin` lets a window such as WireCat Desktop link by pairing code, the QR event carries `expires_at`, and `--json` reports the pairing code and the history wait as events. `account remove --keep-data|--delete-data` unlinks a profile and forgets it. `contacts add` and `contacts rename` save a WhatsApp contact name (remove and import stay refused); `contacts unlink` needs `--from`, `contacts context` reads only the asked account's scope. Queries gain name patterns in `from:` and `chat:`, `*part*` inside words, `participants_count` and `muted:`; `store import` loads a synthetic test store; `serve` exits when its build is out of date; `--offline` on a networked command is refused with `offline.refused`. From cli-core the reference also gains `models set`, `models add` (`--accept-terms` no longer needed), embeddinggemma as the default model, `search all --only meetings` without `--max-meetings`, `contacts link --reason`, bot `--button` and `--no-buttons`, `messages sync --with-muted` with `history_muted`, `keep_store_runs_for_days`, `owner_languages` and the `crm.*` settings. RU/ES changelog (0.31.0 to 0.38.0), commands (English body, as before), archive, attachments, configuration-reference, limits, people, query-language, sessions and usage reviewed; the RU query-language `kind` row's wrong wording was corrected. No correction changed. Upstream errata left for whatsapp-cli: sessions and archive still say `session start` stops after 45 seconds of quiet, and the changelog does not say that `messages sync --all` now leaves muted chats out. The roadmap is unchanged and none of its planned items shipped."
},
"gcal": {
"version": "v0.34.0",
"version": "v0.35.0",
"roadmapSha256": "5b408de5e9a0f7b12d4f904cd71a20a1fdc91a84a01385985e8fe74cbc9c5a97",
"reviewedAt": "2026-11-17",
"conclusion": "Reviewed gcal 0.34.0 from the changelog and the docs diff since v0.33.0. 0.34.0 builds on cli-core 0.691.0 (store schema 69): `meetings people` answers in the standard envelope with its report in `item` and its next page step in `next`, and `meetings list` names its next page with a `page.next` step. docs/index.md, the overview, was rewritten: the reader's gain first, then the start in a few minutes, the agent and the comparison. RU/ES overview (the RU opening approved by the owner, NEED-2670 A) and changelog translated. The roadmap did not change."
"reviewedAt": "2026-11-18",
"conclusion": "Reviewed gcal 0.35.0 from its changelog and the docs diff since v0.34.0. May break callers: the MCP Registry entry no longer starts `mcp serve --profiles all`; `--profiles` is a required argument, so a client set up from the registry asks which profiles to serve. A client set up from the old entry keeps `--profiles all` until it is set up again. The overview (#189) is rewritten as a sales page: what you get, the ideas a newcomer would not guess (including that over MCP a delete does not ask), an example, why gcal against its comparison, a start and plain limits. RU/ES index retranslated and changelog updated and accepted. The roadmap did not change."
},
"mail": {
"version": "v0.32.0",
Expand All @@ -48,10 +48,10 @@
"conclusion": "Reviewed mail 0.29.0 to 0.32.0 from the changelog and the command diff since v0.28.0. 0.29.0: `rules apply` runs up to 15 minutes by default in a terminal and 45 seconds over MCP, reads headers newest first and saves batch by batch; a run that reaches its limit answers `state: partial` with a cursor, and `rules apply --cursor` goes on from there; `rules apply` takes `--yes` over MCP; `score:` and `--kind` judge a sender from the store; the time-limit error names the time limit. 0.30.0 builds on cli-core 0.659.0 and mends a shared config with a small slip, keeping a `.bak` copy. 0.31.0: `rules import --format gmail` takes its own `--yes` over MCP, `rules export` answers over MCP, a resumed `rules apply` that read nothing points to `MAIL_TIMEOUT` over MCP or adds `--timeout 30m` in a terminal, and `messages delete --rules` keeps mail from senders the owner wrote to. 0.32.0: a `readonly` level no longer stops `mail sync`; `deny` still does. RU/ES changelog and commands reviewed. The Email guide and the Yandex Telemost page were checked against the new behaviour: neither says `rules apply` needs a long `--timeout`, fails on a big mailbox or that `readonly` stops sync, so both stay unchanged; the pin moves to v0.32.0. The roadmap is unchanged since v0.17.0: its Next item, a live test of Gmail over OAuth, is not claimed as done. Earlier: Reviewed mail 0.25.0 to 0.28.0 from the changelog and the command diff since v0.24.0. `rules add --do meeting-notes:<provider>` keeps the matched mail whole and protected and saves it as a meeting on sync; `rules apply --yes` saves notes stored before the rule, and its dry run counts them. Telemost notes in Yandex's older layout take the text before the first heading as their summary, and the footer is not stored. `doctor reports show|create`, the `crm.<provider>:<account>.activities` setting, the local-only model switch, declared hosts, and sync on a fresh install with an unreadable shared config. RU/ES changelog and commands reviewed. The Email guide does not describe any of these and stays correct; its pin moves to v0.28.0. The new Yandex Telemost page documents the meeting-notes rule. The roadmap is unchanged since v0.17.0: its Next item, a live test of Gmail over OAuth, is not claimed as done."
},
"b24": {
"version": "v0.24.0",
"roadmapSha256": "fa72ac2974db647979b6c3ac78acb05bc61b37846d938d15c00c3259534ec617",
"reviewedAt": "2026-11-17",
"conclusion": "Reviewed b24 0.16.0 to 0.24.0 from the changelog and the docs diff since v0.15.0. 0.16.0 to 0.21.0: with activities on, sync reads calls, e-mails, meetings, to-dos, Bitrix24 tasks and timeline comments of the copy's deals and leads, deals show and leads show list them and search all finds a deal by their words; sync reads the stage history so a stage passed between two syncs opens its stage task; schedule list, run and exec are MCP tools; store reset is no longer offered over MCP; an unknown profile is not_found. 0.22.0 and 0.23.0: a broken shared config no longer stops sync, and a readonly level no longer stops sync. 0.24.0: Bitrix24 telephony calls in the store (meetings sync and sync copy the call history, meetings transcribe with a local model, download_recordings, calls export of other phone systems' calls, off by default), the new Calls page, b24 setup, people, organizations and users as cli-core's shared CRM commands (breaking: paging, fields, no --body), a local application signs in again after the upgrade, a non-administrator profile reads offline only its own deals and leads, download and public links are kept out of the copy and api call output, api call refuses lead reads to non-administrators. The roadmap moved activities on deals and leads out of Later, which shipped; contacts and companies from the local store stay planned. RU/ES translations of every changed page and the new Calls page reviewed and accepted; the compare page now says api call reads leads too for an administrator only."
"version": "v0.25.0",
"roadmapSha256": "f67e821673b7f32d1b66dbaba258f19008949638a2fb1b96521a553417ae6cae",
"reviewedAt": "2026-11-18",
"conclusion": "Reviewed b24 0.25.0 from its changelog and the docs diff since v0.24.0. May break callers: `meetings transcribe` answers the report beeline gives (`audio_ms` instead of `audio_seconds`, a `ref` on each failed call, a call without a recording under `failed` with `recording.missing`, no `without_recording`). Fixed: a local application sign-in saved by an earlier b24 keeps working after the upgrade. The docs rewrite (#140) and the new overview (#147) open every user page with the reader's gain: the overview is a sales page with what you get, the ideas a newcomer would not guess, an example, why b24 against its comparison and a start. RU/ES of all twelve pages updated and accepted, the changelog's pinned README links moved to v0.25.0. The roadmap now lists what works today, including the morning digest, deal activities, calls and their transcription, and adds client files and documents under Next. None of the earlier Next items shipped."
},
"pbx": {
"version": "v0.8.0",
Expand Down
14 changes: 0 additions & 14 deletions scripts/docs-corrections.json
Original file line number Diff line number Diff line change
Expand Up @@ -2570,20 +2570,6 @@
]
}
},
{
"tool": "b24",
"slug": "index",
"source": "https://github.com/WireCatLabs/bitrix24-cli/blob/main/docs/index.md",
"reason": "The overview page's sidebar label is its title. b24's overview is titled with the command name; the other tools' overview pages carry the product name. Drop this once the release's own heading is Bitrix24.",
"replacements": {
"en": [
{
"before": "title: \"b24\"",
"after": "title: \"Bitrix24\""
}
]
}
},
{
"tool": "zm",
"slug": "search",
Expand Down
4 changes: 2 additions & 2 deletions tools.json
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@
"repo": "WireCatLabs/gcal-cli",
"package": "@wirecat/gcal-cli",
"lang": "en",
"docsRef": "v0.34.0",
"docsRef": "v0.35.0",
"summary": {
"en": "Keep your Google Calendar on your computer, search meetings offline and know who the attendees are in your other chats.",
"ru": "Храните Google Календарь на своём компьютере, ищите встречи без интернета и узнавайте участников из других ваших чатов.",
Expand Down Expand Up @@ -121,7 +121,7 @@
"repo": "WireCatLabs/bitrix24-cli",
"package": "@wirecat/bitrix24-cli",
"lang": "en",
"docsRef": "v0.24.0",
"docsRef": "v0.25.0",
"tier": "extra",
"category": "crm",
"summary": {
Expand Down
38 changes: 27 additions & 11 deletions translations/b24/calls.es.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,16 +2,26 @@
title: "Llamadas"
---

Lee esta página si los teléfonos de tu empresa funcionan con la telefonía de Bitrix24. Explica cómo copiar las
llamadas del portal al almacén local de WireCat, convertir sus grabaciones en texto en este ordenador y encontrar las
llamadas de un cliente junto a sus negociaciones, mensajes y correo. Al final, `memo context` muestra las llamadas de
un cliente en su historial.
Guarda en tu ordenador las llamadas de los teléfonos de Bitrix24, con lo que se dijo como texto, en el mismo almacén
local que las negociaciones, los mensajes y el correo del cliente. El portal guarda sus llamadas en el historial de
llamadas (Telephony → Call history), y `b24` las copia de ahí.

Palabras que usa esta página:
Luego un agente te dice cuándo llamó un cliente por última vez, cómo terminó la llamada y qué se dijo en ella. Las
llamadas de otra centralita también pueden llegar al contacto del cliente en Bitrix24, para que el CRM las muestre.

- **Historial de llamadas**: la lista de llamadas que el portal guarda en Telephony → Call history. b24 la lee con el
método `voximplant.statistic.get`.
- **Perfil**: el nombre del inicio de sesión de un portal, como `work`. Es la primera palabra de un comando.
`meetings sync` copia las llamadas al almacén local de WireCat, y cada `sync` también lo hace. `meetings transcribe`
convierte las grabaciones en texto con un modelo de voz que funciona en este ordenador. `calls export` escribe en
Bitrix24 las llamadas de otras centralitas. Necesitas el permiso `telephony` del webhook.

**En esta página:**

1. [Antes de la primera sincronización](#before-the-first-sync)
2. [Copiar las llamadas](#copy-the-calls)
3. [El cliente y el empleado](#the-client-and-the-employee)
4. [Grabaciones](#recordings)
5. [Convertir las llamadas en texto](#turn-calls-into-text)
6. [Permisos](#permissions)
7. [Escribir en Bitrix24 las llamadas de otras centralitas](#write-other-phone-systems-calls-into-bitrix24)

## Antes de la primera sincronización

Expand All @@ -31,7 +41,7 @@ igualmente. Para dejar las llamadas fuera de `sync`: `b24 work config set sync_c
solo las llamadas:

```sh
b24 work meetings sync # calls since the last sync; the first reads 30 days
b24 work meetings sync # calls since the last sync, the first reads 30 days
b24 work meetings sync --since-time 2026-11-01T00:00:00Z # calls from a date on
b24 work meetings list # newest first, from the store, offline too
b24 work meetings show 12 # one call: who, when, how it ended
Expand Down Expand Up @@ -126,8 +136,14 @@ Las llamadas de otra centralita, como pbx, pueden llegar al contacto del cliente
muestre junto a las llamadas del propio portal. Está desactivado hasta que lo actives, y escribe cada llamada una vez.

Bitrix24 solo deja escribir una llamada a una aplicación, no a un webhook. Primero inicia la sesión del perfil como
aplicación local:
`b24 work session start --portal <portal> --client-id <id>`. Luego actívalo y permite sus dos métodos:
aplicación local ([con una aplicación local](./usage.md#with-a-local-application)), con el host de tu portal y tu
Application ID en lugar de estos ejemplos:

```sh
b24 work session start --portal example.bitrix24.ru --client-id local.0123abcd.45678901
```

Luego actívalo y permite sus dos métodos:

```sh
b24 work config set export_calls true
Expand Down
38 changes: 27 additions & 11 deletions translations/b24/calls.ru.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,16 +2,26 @@
title: "Звонки"
---

Прочитайте эту страницу, если телефоны вашей компании работают через телефонию Битрикс24. Здесь описано, как
скопировать звонки портала в локальное хранилище WireCat, превратить их записи в текст на этом компьютере и найти
звонки клиента рядом с его сделками, сообщениями и почтой. В итоге `memo context` покажет звонки клиента в его
истории.
Храните звонки с телефонов Битрикс24 на своем компьютере, вместе с текстом разговора, в том же локальном хранилище,
что и сделки, сообщения и почту клиента. Портал хранит звонки в истории звонков («Телефония → Детализация звонков»),
и `b24` копирует их оттуда.

Слова, которые использует эта страница:
Агент потом скажет, когда клиент звонил в последний раз, чем закончился звонок и о чем в нем говорили. Звонки из
другой телефонной системы тоже могут попасть в контакт клиента в Битрикс24, и CRM покажет их рядом.

- **История звонков**: список звонков, который портал хранит в разделе «Телефония → Детализация звонков». b24 читает его
методом `voximplant.statistic.get`.
- **Профиль**: имя входа на один портал, например `work`. Это первое слово команды.
`meetings sync` копирует звонки в локальное хранилище WireCat, и каждый `sync` делает это тоже. `meetings transcribe`
превращает записи в текст моделью речи, которая работает на этом компьютере. `calls export` записывает в Битрикс24
звонки других телефонных систем. Вебхуку нужно право `telephony`.

**На этой странице:**

1. [Перед первой синхронизацией](#before-the-first-sync)
2. [Скопировать звонки](#copy-the-calls)
3. [Клиент и сотрудник](#the-client-and-the-employee)
4. [Записи разговоров](#recordings)
5. [Превратить звонки в текст](#turn-calls-into-text)
6. [Разрешения](#permissions)
7. [Записать звонки других телефонных систем в Битрикс24](#write-other-phone-systems-calls-into-bitrix24)

## Перед первой синхронизацией

Expand All @@ -31,7 +41,7 @@ title: "Звонки"
звонки:

```sh
b24 work meetings sync # calls since the last sync; the first reads 30 days
b24 work meetings sync # calls since the last sync, the first reads 30 days
b24 work meetings sync --since-time 2026-11-01T00:00:00Z # calls from a date on
b24 work meetings list # newest first, from the store, offline too
b24 work meetings show 12 # one call: who, when, how it ended
Expand Down Expand Up @@ -125,8 +135,14 @@ b24 work config set permissions.meetings.sync deny
записывается один раз.

Битрикс24 разрешает записывать звонок только приложению, а не вебхуку. Сначала войдите в профиль как локальное
приложение:
`b24 work session start --portal <portal> --client-id <id>`. Затем включите запись и разрешите два ее метода:
приложение ([с локальным приложением](./usage.md#with-a-local-application)), подставив вместо примеров адрес своего
портала и код приложения:

```sh
b24 work session start --portal example.bitrix24.ru --client-id local.0123abcd.45678901
```

Затем включите запись и разрешите два ее метода:

```sh
b24 work config set export_calls true
Expand Down
Loading
Loading