Repository navigation
Releases
Releases · WireCatLabs/bitrix24-cli
0.26.0
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
--profilesis a required argument with the examplepersonal: the client asks for one profile, a
comma-separated list orall. 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 alluntil it is set up again; a
server added by hand or withmcp configdoes 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, someetings 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-meetingscounts calls with a recording. A call with no recording on the portal is
still listed underfailed, but it no longer uses up the limit. Before, when the newest calls had no recording,
--max-meetings 1turned nothing into text.- A recording sent with no audio type. A telephony provider's server, such as a Beeline cloud PBX, sends a
recording asapplication/octet-streamand names the file,call.mp3, in itsContent-Disposition. b24 refused
it as not audio (recording.not-audio), someetings transcribeturned none of these calls into text. It now takes
the format from the file name when the type names none.
0.25.0
Changed — may break callers
meetings transcribeanswers the same report as beeline. The audio time isaudio_ms, in milliseconds (was
audio_seconds). Each failed call has itsref. A call with no recording on the portal is listed underfailed
with the reasonrecording.missing, andwithout_recordingis 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
Added
- Built on cli-core 0.683.0 (was 0.670.0), with its CRM additions:
deals listandleads listtakeupdated:,
created:,closed:andowner:(owner:meis 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 showanswers
stage_historyfrom the portal's own stage history;stages listanswersstage_task. See the
cli-core changelog. people createandorganizations createtake--emailand--phone. A phone is taken only in international
form (+…).people updateandorganizations updatestill refuse them: Bitrix24 would add the new ones to the
old ones rather than replace them.calls exportwrites the calls of other phone systems onto the client's contact in Bitrix24, once each, with
telephony.externalCall.registerandfinish. Off by default: it needs the settingexport_calls, the two methods'
permissions, and the local application sign-in, since Bitrix24 lets no webhook write a call.--dry-runshows each
call's fields and where it lands, and sends nothing. See Calls.- Bitrix24 telephony calls in the store.
meetings synccopies 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 inunassigned, 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,exportandpeopleread them, andmemo contextshows them in a
person's history. The webhook needs thetelephonyscope. See Calls. meetings transcribeandmodelsturn call recordings into text with a local speech model, on this computer.download_recordingskeeps each call's recording in the state folder, for WireCat Desktop to play;
phone_regionreads the numbers the portal writes without+.b24 setupwalks 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 --jsonprints the steps (setup format v1),
b24 work setup applychecks the address against the portal the waysession startdoes and only then keeps it.
A local application stays onesession start --portal … --client-id …away, shown at the end.- The permissions to tick now name
taskfor Bitrix24 tasks,telephonyfor calls, anddiskand
documentgeneratorfor client files and documents, besidecrm,user_basicanddepartment. Tickingdisk
now saves editing the webhook again when the files feature comes. changes listfrom cli-core 0.678.0: what changed in the CRM copy in a window, and--format reportfor a
morning digest.synccopies the portal's calls too, after the CRM, asmeetings syncdoes, 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 settingsync_calls(on when not set) leaves them out. When calls came in and
phone_regionis not set, the note says how to set it. See Calls.
Changed — may break callers
syncreads the portal's stage history every time, 90 days back at first, so the funnel anddeals showcount
the stages a deal really passed. A webhook without the right tocrm.stagehistory.listnames 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 listandpipelines showleave out a stage the portal removed unless a deal stands in
it.- The agent skill is shorter.
SKILL.mdkeeps what an agent needs on every turn (the profile rule, answering
from the CRM, the limits on writes, MCP'saskthat does not ask, output) in about 8 KB instead of 18 KB, and links
the rest inskills/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 listtakesupdated:,created:,closed:andowner:me,pipelines showcounts a
window's funnel,people createandorganizations createtake--emailand--phonewhileupdaterefuses
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,organizationsandusersare WireCat's shared CRM commands now, the same words, query and answer
as in every CRM tool. An organization answerstypeandowninstead oftype_id; its industry, revenue and
currency move underprovider_metadata, andindustry_id:is no longer a filter. Every live list and show gives
the custom fields underprovider_metadata, every item names itsuntrustedfields, and--offlinestill refuses
them. A user is thecrm_userentity, notuser. A name that fits several records iscrm.record-ambiguous, not
organization.ambiguousorperson.ambiguous.- These three lists page with
--limit(1 to 250, 50 when left out) and--page.--all, a limit above 250 and
the profile'sdefaults.limitno 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 createandorganizations updateare the shared writes. They
take--name,--owner,--field, and for people--first-name,--last-nameand--position;--bodyis
gone (api callwrites any other field). Each answers the record as the portal holds it, and stores it.- A label in
--fieldneeds asyncfirst. Before one, name the field by its code, asfields listprints 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, andapi callrefuses 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 untilsync --rescan. - A field the portal will not describe still shows, from
userfield.list, with no label:syncstores it and
--fieldcan set it. api callrefuses 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, socrm.lead.listhanded an employee the whole portal's lead contact
data past the 100-a-day rule.- Won and lost stages read from
EXTRA.SEMANTICSare won and lost, not open. A stage the portal lists without
the shortSEMANTICScarries onlysuccess,failureorapology, whichsyncstored as open: their deals counted
as open anddeals closefound no won stage. - A round of activities spread over several
syncruns no longer loses what changed while it ran. It ended with
the last run's time, so the next round'ssinceskipped 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, andsearch allfound them by their contacts' e-mails and phones. Now another user's deal is
not_foundand 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 withsession start. The administrator, as its lastsyncfound,
reads the whole copy as before. Until asyncof this version runs, every profile reads only its own deals and
leads: runsynconce 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, insyncand in everyshow,listand 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 callprints[link removed]in place of every download link, every
generated document'spublicUrl, and every portal link with a token. A copy synced before this version may still
hold such links:b24 work sync --rescanrewrites the records the portal still lists; a record deleted or outside
the sync's scope keeps what it held untilaccount remove --delete-data. See Security. api callrefuses the methods that make a public link: `ena...
0.23.0
Changed — may break callers
- A
readonlylevel no longer stopsb24 sync(cli-core 0.662.0, was 0.659.0). A command that only fetches from
Bitrix24 into the local store runs atreadonly;denystill refuses it. Commands that write the owner's files
or call another service stay blocked byreadonly. A profile that usedreadonlyto stop syncing sets the key
todeny.
0.22.0
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 asconfig.json.bak-<time>; other damage names its line and the likely fix. See the
cli-core changelog.
0.21.0
Added
- Timeline comments on deals and leads. With
activitieson,syncreads 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 showandsearch allsee 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.
syncasked 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
Added
- An agent can run a schedule over MCP.
schedule list,schedule runandschedule execare MCP tools, each
behind its own permission key. Adding, pausing, resuming or removing a timer over MCP is still refused unless
permissions.mcp.authorityisallow. Before, b24 kept all ofscheduleoff MCP. See
MCP. b24 --helplistspbx, 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
syncruns 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 oldersetupshape) made b24 refusesyncwith "setup's answer keeps every
WireCat tool read-only". Now only the owner's own "read only" answer limits b24, and even thensyncruns: it only
reads the portal into the local store (cli-core 0.654.0).
0.19.0
Added
- A stage task opens for a stage passed between two syncs.
syncreads the portal's stage history
(crm.stagehistory.list) whilestage-tasksnames 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
- Built on cli-core 0.650.0 (was 0.648.0). See the
cli-core changelog.
Fixed
synckeeps 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 as98765432109.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 insync'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. synchands 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
Added
search allfinds 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 leasefinds 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_foundwith reasonprofile.unknown, the profiles here, and the
sign-in hint, exit code 6; it wasauthentication_error, exit code 4. A profile set in the environment keeps the
sign-in refusal. store resetis no longer offered over MCP: it needs--yes, which an MCP call cannot pass.
0.17.0
Fixed
crm syncwith 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 reacheddeals show.crm syncwith 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.