Skip to content

Releases

0.26.0

Choose a tag to compare

@github-actions github-actions released this 17 Nov 23:32
6dbe6cb

Changed — may break callers

  • 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). 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

  • Recordings your telephony provider keeps. A portal that works with an outside telephony provider, such as a
    Beeline cloud PBX, links each recording to the provider's server. b24 refused such a link, so meetings transcribe
    turned none of these calls into text. It now follows the link over https to an address on the public internet,
    never to this computer or a local network, and sends nothing of your Bitrix24 sign-in with it. See
    Calls.
  • meetings transcribe --max-meetings counts calls with a recording. A call with no recording on the portal is
    still listed under failed, but it no longer uses up the limit. Before, when the newest calls had no recording,
    --max-meetings 1 turned nothing into text.
  • A recording sent with no audio type. A telephony provider's server, such as a Beeline cloud PBX, sends a
    recording as application/octet-stream and names the file, call.mp3, in its Content-Disposition. b24 refused
    it as not audio (recording.not-audio), so meetings transcribe turned none of these calls into text. It now takes
    the format from the file name when the type names none.

0.25.0

Choose a tag to compare

@github-actions github-actions released this 17 Nov 21:48
10abda0

Changed — may break callers

  • meetings transcribe answers the same report as beeline. The audio time is audio_ms, in milliseconds (was
    audio_seconds). Each failed call has its ref. A call with no recording on the portal is listed under failed
    with the reason recording.missing, and without_recording is gone. Before, b24 and beeline answered the same
    report in two shapes, so a script written for one could not read the other.

Fixed

  • A local application sign-in saved by an earlier b24 keeps working after the upgrade. Earlier versions kept the
    portal under another name in the saved sign-in, and the new sign-in store answered "the saved sign-in cannot be
    read; sign in again".

0.24.0

Choose a tag to compare

@github-actions github-actions released this 17 Nov 01:56
ccf5f02

Added

  • Built on cli-core 0.683.0 (was 0.670.0), with its CRM additions: deals list and leads list take updated:,
    created:, closed: and owner: (owner:me is your own portal user); pipelines show --since-time --until-time
    answers the funnel of a window with closed deals, cycle time, owners and lost reasons; deals show answers
    stage_history from the portal's own stage history; stages list answers stage_task. See the
    cli-core changelog.
  • people create and organizations create take --email and --phone. A phone is taken only in international
    form (+…). people update and organizations update still refuse them: Bitrix24 would add the new ones to the
    old ones rather than replace them.
  • calls export writes the calls of other phone systems onto the client's contact in Bitrix24, once each, with
    telephony.externalCall.register and finish. Off by default: it needs the setting export_calls, the two methods'
    permissions, and the local application sign-in, since Bitrix24 lets no webhook write a call. --dry-run shows each
    call's fields and where it lands, and sends nothing. See Calls.
  • Bitrix24 telephony calls in the store. meetings sync copies the portal's call history: each call is a meeting
    of kind call with its direction, the client's number, the employee, the talk time and how it ended, for the
    signed-in user or the users chosen in unassigned, never the whole portal. The employee is the portal's user in
    the copy; the client joins the contact, messenger account or other phone system's calls with the same mobile
    number. meetings list, show, transcript, export and people read them, and memo context shows them in a
    person's history. The webhook needs the telephony scope. See Calls.
  • meetings transcribe and models turn call recordings into text with a local speech model, on this computer.
  • download_recordings keeps each call's recording in the state folder, for WireCat Desktop to play;
    phone_region reads the numbers the portal writes without +.
  • b24 setup walks you through connecting a portal, and WireCat Desktop draws the same steps: create an inbound
    webhook, tick its permissions, paste its address. b24 setup show --json prints the steps (setup format v1),
    b24 work setup apply checks the address against the portal the way session start does and only then keeps it.
    A local application stays one session start --portal … --client-id … away, shown at the end.
  • The permissions to tick now name task for Bitrix24 tasks, telephony for calls, and disk and
    documentgenerator for client files and documents
    , beside crm, user_basic and department. Ticking disk
    now saves editing the webhook again when the files feature comes.
  • changes list from cli-core 0.678.0: what changed in the CRM copy in a window, and --format report for a
    morning digest.
  • sync copies the portal's calls too, after the CRM, as meetings sync does, so WireCat Desktop's sync and the
    sync after install bring calls. A calls step that fails, such as a webhook without the telephony scope, is a note,
    and the CRM sync still succeeds. The setting sync_calls (on when not set) leaves them out. When calls came in and
    phone_region is not set, the note says how to set it. See Calls.

Changed — may break callers

  • sync reads the portal's stage history every time, 90 days back at first, so the funnel and deals show count
    the stages a deal really passed. A webhook without the right to crm.stagehistory.list names it as an issue.
  • Offline CRM reads read the stored sign-in to know your portal user, from B24_TOKEN, the OS keyring or the
    credentials file, without the network. Where no keyring can be reached, the read warns and uses the file; with no
    sign-in found it shows no deals or leads.
  • pipelines list, stages list and pipelines show leave out a stage the portal removed unless a deal stands in
    it.
  • The agent skill is shorter. SKILL.md keeps what an agent needs on every turn (the profile rule, answering
    from the CRM, the limits on writes, MCP's ask that does not ask, output) in about 8 KB instead of 18 KB, and links
    the rest in skills/bitrix24-cli/references/: reading, writing, MCP, output and setup. No rule was dropped. The
    skill now says what changed since it was written: activities, tasks and comments on deals are read when the owner
    turns them on, deals list takes updated:, created:, closed: and owner:me, pipelines show counts a
    window's funnel, people create and organizations create take --email and --phone while update refuses
    them, and a profile that is not the administrator reads offline only its own deals and leads. An agent that reads
    the skill pays about 2,500 fewer tokens on every turn.
  • people, organizations and users are WireCat's shared CRM commands now, the same words, query and answer
    as in every CRM tool. An organization answers type and own instead of type_id; its industry, revenue and
    currency move under provider_metadata, and industry_id: is no longer a filter. Every live list and show gives
    the custom fields under provider_metadata, every item names its untrusted fields, and --offline still refuses
    them. A user is the crm_user entity, not user. A name that fits several records is crm.record-ambiguous, not
    organization.ambiguous or person.ambiguous.
  • These three lists page with --limit (1 to 250, 50 when left out) and --page. --all, a limit above 250 and
    the profile's defaults.limit no longer apply to them. users list name: matches part of the whole name across
    every employee, not the portal's own name search.
  • people create, people update, organizations create and organizations update are the shared writes. They
    take --name, --owner, --field, and for people --first-name, --last-name and --position; --body is
    gone (api call writes any other field). Each answers the record as the portal holds it, and stores it.
  • A label in --field needs a sync first. Before one, name the field by its code, as fields list prints it.
  • The 100-a-day count of other people's contacts and companies is cli-core's and starts again from zero. Its
    message and its reason (crm.foreign-contacts-spent) are the shared ones, and api call refuses client reads with
    crm.client-reads-admin-only.
  • Sign in again after an upgrade with a local application (session start --app). The stored sign-in moved to
    cli-core's shape; the old one no longer reads. A webhook sign-in is not affected.
  • A run with moved folders (B24_CONFIG_DIR, B24_STATE_DIR) no longer renews an expired application sign-in.
    Bitrix24 replaces the refresh token on every renewal, so a moved run that renewed it would sign the owner's own
    runs out. It says so; renew it in a run without moved folders.

Fixed

  • A contact given to a colleague leaves the copy at the next sync, with its phone and e-mail. Before, its one
    phone and e-mail stayed until sync --rescan.
  • A field the portal will not describe still shows, from userfield.list, with no label: sync stores it and
    --field can set it.
  • api call refuses lead reads to anyone but a Bitrix24 administrator, as it refuses contact and company reads.
    A lead holds its own name, phones and e-mails, so crm.lead.list handed an employee the whole portal's lead contact
    data past the 100-a-day rule.
  • Won and lost stages read from EXTRA.SEMANTICS are won and lost, not open. A stage the portal lists without
    the short SEMANTICS carries only success, failure or apology, which sync stored as open: their deals counted
    as open and deals close found no won stage.
  • A round of activities spread over several sync runs no longer loses what changed while it ran. It ended with
    the last run's time, so the next round's since skipped every activity, task and comment changed in between: a
    task completed then stayed open in the copy until it changed again. The round now ends with its first page's time.

Security

  • A profile that is not the portal's administrator reads offline only the deals and leads assigned to it. The copy
    is kept per portal, so an ordinary employee's profile on the same portal as the administrator's read every deal the
    administrator synced, and search all found them by their contacts' e-mails and phones. Now another user's deal is
    not_found and the reports count only its own. A profile whose sign-in names no portal user reads none of the
    copy's deals, says so and exits 1; sign in again with session start. The administrator, as its last sync found,
    reads the whole copy as before. Until a sync of this version runs, every profile reads only its own deals and
    leads: run sync once after upgrading.
  • No file download link in the copy or the output. A file in a CRM record's custom field is now kept as its
    file id, in sync and in every show, list and write answer: Bitrix24's download link (urlMachine,
    downloadUrl) carries an access token. A file with no id and a portal link with a token show as [link removed];
    a site or link field typed by hand stays. api call prints [link removed] in place of every download link, every
    generated document's publicUrl, and every portal link with a token. A copy synced before this version may still
    hold such links: b24 work sync --rescan rewrites the records the portal still lists; a record deleted or outside
    the sync's scope keeps what it held until account remove --delete-data. See Security.
  • api call refuses the methods that make a public link: `ena...
Read more

0.23.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 08:17
e4dee88

Changed — may break callers

  • A readonly level no longer stops b24 sync (cli-core 0.662.0, was 0.659.0). A command that only fetches from
    Bitrix24 into the local store runs at readonly; deny still refuses it. Commands that write the owner's files
    or call another service stay blocked by readonly. A profile that used readonly to stop syncing sets the key
    to deny.

0.22.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 03:21
2d20d84

Changed — may break callers

  • Built on cli-core 0.659.0 (was 0.654.0). A shared WireCat config (~/.config/WireCat/config.json) with a
    byte-order mark, a comment, a trailing comma or a missing comma between two lines is now mended when it is read,
    the old file kept beside it as config.json.bak-<time>; other damage names its line and the likely fix. See the
    cli-core changelog.

0.21.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 00:35
52be9da

Added

  • Timeline comments on deals and leads. With activities on, sync reads the comments in the timeline of each
    open deal and lead in the copy, and of each closed one that changed since the last sync. deals show,
    leads show and search all see them. The portal answers one deal or lead per request, so a copy of 100 open
    deals takes about 100 requests a sync. A comment on a closed deal that nothing else changed waits until the deal
    changes. See Activities and tasks on a deal.

Fixed

  • Only the tasks of the copy's deals and leads are read. sync asked the portal for every task changed in 90
    days and dropped those on other deals. It now filters by the copy's deals and leads, 50 a request.

0.20.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 17:16
932c60a

Added

  • An agent can run a schedule over MCP. schedule list, schedule run and schedule exec are MCP tools, each
    behind its own permission key. Adding, pausing, resuming or removing a timer over MCP is still refused unless
    permissions.mcp.authority is allow. Before, b24 kept all of schedule off MCP. See
    MCP.
  • b24 --help lists pbx, the Asterisk tool, under "Works with" (cli-core 0.651.0).

Changed — may break callers

  • Built on cli-core 0.651.0 (was 0.650.0). A stale meeting project fingerprint is now conflict, not
    configuration_error. See the cli-core changelog.
  • Built on cli-core 0.654.0 (was 0.651.0). See the
    cli-core changelog.

Fixed

  • sync runs on a fresh install. A shared WireCat config that could not be read (a byte-order mark, broken
    JSON, a folder in its place, an older setup shape) made b24 refuse sync with "setup's answer keeps every
    WireCat tool read-only". Now only the owner's own "read only" answer limits b24, and even then sync runs: it only
    reads the portal into the local store (cli-core 0.654.0).

0.19.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 03:44
c227310

Added

  • A stage task opens for a stage passed between two syncs. sync reads the portal's stage history
    (crm.stagehistory.list) while stage-tasks names a stage, so a deal moved from "New" through "Quote" to "Won" in
    one day opens the tasks of both "Quote" and "Won"; before, only "Won". The history is read from the last sync on,
    a page or two a day, and not at all without the setting (cli-core 0.650.0).

Changed — may break callers

Fixed

  • sync keeps a deal's or lead's amount as the portal wrote it. From about 10 billion with kopecks or cents, the old
    rounding added digits such as 98765432109.869995, and the copy then left that deal out. An amount the copy cannot
    hold, more than about 90 trillion or with more decimals than its currency has, is still named in sync's issues
    and left out, as before.
  • Two profiles on one portal now share one request pace. Bitrix24 counts requests per portal, so before, they could
    go twice as fast as the portal allows and get refused.
  • A write the portal refused because of its request limit is sent again after the wait the portal asks for, as a read
    is. The portal refuses such a request before doing anything, so it is not made twice. A write that got no answer is
    still never sent again.
  • sync hands every phone and e-mail of a contact to the copy, not only the first, so a call or chat from any of
    them can be matched to the contact.

0.18.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 01:12
4cee215

Added

  • search all finds a deal or lead by the words of its activities. With activities on, the subject and text of
    each call, e-mail, meeting, to-do and task on a deal count as its words, beside its title, company and contacts:
    b24 work search all warehouse lease finds the deal whose e-mail spoke of it (cli-core 0.648.0).

Changed — may break callers

  • Built on cli-core 0.648.0 and cli-base 0.98.0 (were 0.647.0 and 0.97.0). See the
    cli-core changelog.
  • A profile this computer has never seen is not_found with reason profile.unknown, the profiles here, and the
    sign-in hint, exit code 6; it was authentication_error, exit code 4. A profile set in the environment keeps the
    sign-in refusal.
  • store reset is no longer offered over MCP: it needs --yes, which an MCP call cannot pass.

0.17.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 22:58
80e0802

Fixed

  • crm sync with activities on also keeps an e-mail, call or meeting whose own owner is a contact or company and
    that is only bound to your deal or lead. Before, such an activity never reached deals show.
  • crm sync with activities on reads only the activities on your own deals and leads, fifty deals or leads per
    request, instead of every activity on the portal. The first read of a large portal took about four minutes for a
    handful of activities; it now takes as many requests as you have deals and leads, divided by fifty.