wldx-cli 0.1.1 → 1.1.0

package/README.md

@@ -1,34 +1,257 @@
 # wldx-cli — `wx`, a command line for Wildix
 
-**Version 0.1.1** · unofficial · MIT
+**Version 1.1.0** · unofficial · MIT
 
-`wx` works with Wildix as **the logged-in user**: your chats today, more of x-bees later. It is the command-line
-twin of the [Wildix agent skills](https://github.com/gorets/wildix-skills) and shares their login.
+`wx` works with Wildix as **the logged-in user**: chats, calls and meetings on record, queue reports, what is going
+on now, and your phone. It is the command-line twin of the
+[Wildix agent skills](https://github.com/gorets/wildix-skills) and shares their login.
 
 ```sh
-npx wldx-cli chat list               # without installing
-npm i -g wldx-cli && wx chat list    # installed: the command is `wx`
+npm i -g wldx-cli          # the command is `wx`
+wx login you@company.com   # a code comes by e-mail
+wx status
+wx chat list
+
+npx wldx-cli chat list     # without installing
 ```
 
-Requires Node.js 22 or newer. No dependencies.
+Requires Node.js 22 or newer. One dependency: [`wldx-core`](https://github.com/gorets/wildix-cli/tree/main/packages/core), the core it shares with `wx-admin`, from the
+same repository and of the same version.
+
+Unofficial: not made or supported by Wildix. It uses the same internal APIs as the Wildix apps, which may change.
 
 ## Commands
 
+Every command has `-h`, takes `--profile EMAIL` (which login to use, see [Profiles](#profiles)), and prints text or, with `--output json`, JSON. `wx <group> -h`
+lists the commands of a group.
+
+<!-- commands:start (generated by tools/readme-commands.mjs) -->
+### wx chat
+
+Chats: channels, messages, reactions, mentions, search, the live feed.
+
 | Command | What it does |
 | --- | --- |
 | `wx chat list [--filter unread\|archived] [--section ID] [--cursor C]` | your channels, newest activity first |
 | `wx chat read <channel> [--unread] [--from SEQ] [--to SEQ]` | messages of a channel, newest first, 30 per page |
-| `wx chat send <channel> <text\|-> [--markdown] [--reply-to MESSAGE]` | send a message (`-` reads the text from stdin) |
-| `wx auth status` | the accounts you are logged in with and until when their token is valid (no network) |
+| `wx chat send <channel> <text\|-> [--markdown] [--reply-to MESSAGE] [--mention USERID]... [--file PATH]...` | send a message to a channel ("-" reads the text from stdin) |
+| `wx chat get <channel> <message>` | one message |
+| `wx chat edit <channel> <message> <text\|-> [--markdown]` | edit your own message ("-" reads the new text from stdin) |
+| `wx chat delete <channel> <message> --yes` | delete your own message, for everyone (needs --yes) |
+| `wx chat pin <channel> <message>` | pin a message in its channel (clients then show it as edited) |
+| `wx chat unpin <channel> <message>` | unpin a message |
+| `wx chat react <channel> <message> <type>` | react to a message (eyes, white_check_mark, thumbsup, heart…) |
+| `wx chat unreact <channel> <message> <type>` | take your reaction back |
+| `wx chat reactions <channel> <message> [--type TYPE] [--users]` | who reacted to a message: one entry per person and type |
+| `wx chat mentions [--unread] [--cursor C]` | messages that mention you |
+| `wx chat search <query> [--channel C] [--sender USERID]... [--attachments] [--links] [--size 1-50] [--cursor C] [--sort relevance\|recency\|recency_asc]` | search messages in your channels |
+| `wx chat watch [--channel C]... [--from USERID]... [--type TYPE]... [--mine] [--count N] [--for SECONDS] [--raw]` | follow your chats live: messages, reactions, reads, members, channel changes |
+
+### wx channel
+
+Chat channels: get, search, create, 1:1, update, join, leave, delete, members.
+
+| Command | What it does |
+| --- | --- |
+| `wx channel get <channel>` | one channel |
+| `wx channel query <channel>...` | several channels by id (not implemented by the service yet) |
+| `wx channel search <query> [--type direct\|group] [--member USERID] [--size 1-50] [--cursor C] [--sort relevance\|recency\|recency_asc]` | search your channels by subject or member |
+| `wx channel create --subject S [--description D] [--access private\|public] [--member USERID]... [--invite EMAIL]... [--id 8-4-4-4-8] [--auto-transcribe \| --no-auto-transcribe]` | create a group channel |
+| `wx channel direct (--user USERID \| --email EMAIL)` | the 1:1 channel with a person (created when it does not exist yet) |
+| `wx channel direct-id (--user USERID \| --email EMAIL)` | only the id of the 1:1 channel with a person (nothing is created) |
+| `wx channel update <channel> [--subject S] [--description D] [--access private\|public] [--unset FIELD]...` | change the subject, description or access of a channel (not implemented by the service yet) |
+| `wx channel join <channel>` | join a public channel (not implemented by the service yet) |
+| `wx channel leave <channel>` | leave a channel |
+| `wx channel delete <channel> --yes` | delete a channel for everyone (needs --yes) |
+| `wx channel members <channel> [--limit 1-100] [--offset 0-1000]` | members of a channel |
+| `wx channel member <channel> <userId>` | one member of a channel (not implemented by the service yet) |
+| `wx channel add <channel> (--user USERID \| --invite EMAIL)... [--hide-history]` | add people to a channel |
+| `wx channel remove <channel> <userId>` | remove a person from a channel |
+| `wx channel read-status <channel>` | who has read a channel up to where (channels with up to 100 members) |
+
+### wx inbox
+
+Your inbox: unread, mark read or unread, mute, pin, hide (only for you).
+
+| Command | What it does |
+| --- | --- |
+| `wx inbox get` | your inbox: recent channels with your state, and the counters of the sections |
+| `wx inbox mark-read <channel> [--message MESSAGE]` | mark a channel read, up to the latest message (or up to a message) |
+| `wx inbox mark-unread <channel> [--message MESSAGE] [--force]` | mark a channel unread from a message on |
+| `wx inbox mute <channel> [--until ISO8601]` | mute a channel (no notifications), for good or until a time |
+| `wx inbox unmute <channel>` | unmute a channel |
+| `wx inbox pin <channel>` | pin a channel at the top of your inbox |
+| `wx inbox unpin <channel>` | unpin a channel |
+| `wx inbox hide <channel>` | archive a channel (hide it from your inbox) |
+| `wx inbox show <channel>` | restore an archived channel |
+
+### wx file
+
+Files in chat channels: upload, info, download.
+
+| Command | What it does |
+| --- | --- |
+| `wx file upload <channel> <path>` | upload a file to a channel and print the attachment object (to put into a message) |
+| `wx file info <channel> <fsId>` | name, type and size of an uploaded file |
+| `wx file download-url <channel> <message> <fsId>` | a temporary download link of a file of a message |
+| `wx file download <channel> <message> <fsId> --to PATH` | save a file of a message (never overwrites a file) |
+
+### wx user
+
+People: you, a colleague by name, e-mail or phone.
+
+| Command | What it does |
+| --- | --- |
+| `wx user me` | the logged-in user: id, name, e-mail, extension |
+| `wx user find <query> [--mode auto\|name\|email\|phone] [--kind human\|bot\|all] [--with-extension] [--min-confidence 0..1] [--brief] [--size 1-50] [--cursor C]` | find a colleague by name (any script, typos, as it sounds), e-mail or phone |
+| `wx user get [<id\|email\|phone>...] [--id USERID]... [--email EMAIL]... [--phone PHONE]...` | people by user id, e-mail or phone (exact lookup) |
+
+### wx section
+
+Your inbox sections (not implemented by the service yet, except list).
+
+| Command | What it does |
+| --- | --- |
+| `wx section list` | your inbox sections with their counters |
+| `wx section create <sectionId> <name>` | create a section (not implemented by the service yet) |
+| `wx section rename <sectionId> <name>` | rename a section (not implemented by the service yet) |
+| `wx section delete <sectionId>` | delete a section (not implemented by the service yet) |
+| `wx section add <channel> <sectionId>` | put a channel into a section (not implemented by the service yet) |
+| `wx section remove <channel> <sectionId>` | take a channel out of a section (not implemented by the service yet) |
+
+### wx calls
+
+Your call history and calls after the fact: record, transcript, summary, insights.
+
+| Command | What it does |
+| --- | --- |
+| `wx calls list [--direction INTERNAL\|INBOUND\|OUTBOUND] [--status COMPLETED\|MISSED] [--flag FAX\|VOICEMAIL]... [--from ISO] [--to ISO] [--search TEXT] [--tag TAG]... [--has-attachment] [--user-direction INCOMING\|OUTGOING] [--limit 1-100] [--offset N] [--brief]` | your own call history, newest first, 50 per page |
+| `wx calls missed [the options of list, without --status]` | your missed calls, newest first (list --status MISSED) |
+| `wx calls get <callId> [flow]` | the record of a call: who called whom, times, queue, trunk, recordings |
+| `wx calls brief <callId> [flow]` | a call as one readable object: record, summary, insights |
+| `wx calls transcript <callId> [flow] [--to FILE] [--structured]` | the dialogue of a call (exit 3 when there is none) |
+| `wx calls annotations <callId> [flow]` | the annotations of a call (404 when there are none) |
+| `wx calls insights <callId> [flow] [--raw]` | the AI insights that were generated: {projection: {field: value}} |
+| `wx calls summary <callId> [flow]` | the AI title, brief and the structured summary of a call |
+| `wx calls characteristics <callId> [flow]` | talk time, interruptions, sentiment and talk speed of a call |
+| `wx calls state <callId> [flow]` | your own state of a call: playlists, playback position |
+| `wx calls recordings <callId> [flow]` | the recordings of a call: file names and their links on the PBX |
+| `wx calls schedule-summary <callId> [flow]` | ask the service to generate the summary of a call again (only when asked: it does work) |
+
+### wx meetings
+
+Meetings (conferences) after the fact: record, transcript, summary, insights, recording.
+
+| Command | What it does |
+| --- | --- |
+| `wx meetings get <conference>` | the record of a meeting: subject, times, participants, recordings, transcription status |
+| `wx meetings brief <conference>...` | a meeting as one readable card: record, participants, summary, insights (several: oldest first) |
+| `wx meetings transcript <conference> [--to FILE] [--structured]` | the dialogue of a meeting with a header (exit 3 when there is none) |
+| `wx meetings annotations <conference>` | the annotations of a meeting (404 when there are none) |
+| `wx meetings insights <conference> [--raw]` | the AI insights that were generated: {projection: {field: value}} |
+| `wx meetings summary <conference>` | the AI title, brief and the structured summary of a meeting |
+| `wx meetings state <conference>` | your own state of a meeting: playlists, playback position |
+| `wx meetings timeframes <conference>` | who spoke when in a meeting |
+| `wx meetings recording-url --file-id ID --category channels\|recordings\|wizyconfRecordings [--download]` | a link to download or play a recording of a meeting |
+| `wx meetings schedule-summary <conference>` | ask the service to generate the summary of a meeting again (only when asked: it does work) |
+
+### wx conversations
+
+Search calls, meetings and chats with their AI summary; counts and statistics.
+
+| Command | What it does |
+| --- | --- |
+| `wx conversations find [--entity call\|conference\|chat]... [--email E]... [--phone P]... [--extension X]... [--everyone] [--transcribed] [--recorded] [--direction inbound\|outbound\|internal] [--from ISO --to ISO [--tz ZONE]] [--when PERIOD] [--tag T]... [--language L]... [--cursor KEY] [--brief]` | the search over conversations with the summary of each, 10 per page |
+| `wx conversations count [the filter of find, without --cursor and --brief]` | how many conversations match the filter |
+| `wx conversations aggregate (--by DIM[,DIM...] \| --by DIM --then DIM [--then DIM] \| --projections) [the filter of find] [--tz ZONE] [--top N] [--raw]` | how many conversations fall into each value of a dimension (the data of a chart) |
+| `wx conversations tags <prefix> [--limit 1-20]` | the tags that start with a prefix |
+
+### wx reports
+
+Reports of the call queues over days: service level, abandoned, lost, waits, agents.
+
+| Command | What it does |
+| --- | --- |
+| `wx reports list [--name TEXT] [--pbx SERIAL]` | the queues of the company: id, name, PBX (and how many on each PBX) |
+| `wx reports summary [filter]` | every queue call of the filter: offered, answered, abandoned, lost, waits, talk, ring, the SLA counts |
+| `wx reports by-queue [filter]` | the same figures per queue |
+| `wx reports by-period --by hour\|day\|week\|month\|weekday [filter]` | the same figures as a series (hour: the 24 hours of the day over the window) |
+| `wx reports answered [--by queue\|agent\|user\|reason\|talk-time] [--band S --steps N] [filter]` | the answered calls: summary, or grouped by queue, agent, user, reason or talk time |
+| `wx reports unanswered [--by queue\|reason] [filter]` | the abandoned and unanswered calls: summary (lost, overflow), or grouped by queue or reason |
+| `wx reports service-level answered\|unanswered [--band S] [--steps N] [filter]` | how many calls were answered (or given up) within 20, 40, … seconds |
+| `wx reports calls [--limit N] [--pages N] [--cursor C] [--call CALLID] [--full] [filter]` | the queue calls one by one, newest first: queue, times, wait, talk, outcome, who answered |
+| `wx reports events <callId> <flowIndex> [--queue ID] [--full]` | one call in one queue: its row and its events (INIT, RING, CANCEL, ANSWER, END) with the agents rung |
+
+### wx live
+
+What is going on now: queues and agents, calls and chats in progress, presence, live transcripts.
+
+| Command | What it does |
+| --- | --- |
+| `wx live queues [--name TEXT] [--pbx SERIAL] [--busy] [--paused] [--active] [--stats] [--window W] [--sla S] [--full]` | the call queues of the company: strategy, calls in them now, agents with their status (Premium) |
+| `wx live conversations [--calls] [--chats] [--conferences] [--mine] [--status S] [--limit N] [--full]` | the calls, customer chats and conferences going on now, newest first, with their live insights (Premium) |
+| `wx live presence <extension>... [--full]` | status, status message, "until" and phone registration of colleagues (is someone available) |
+| `wx live transcript <callId\|conference:ID> [--follow] [--for SECONDS] [--full]` | the live transcript of a call or conference in progress; --follow prints each new line until it ends |
+| `wx live watch [--conversations] [--calls] [--mine] [--queues] [--stats] [--window W] [--sla S] [--presence EXT]... [--for SECONDS] [--full]` | a live feed: one line per change of the conversations, queues or presence until stopped |
+
+### wx phone
+
+Live calls on your PBX: place, answer, hold, transfer, DTMF, record; your devices; watch live.
+
+| Command | What it does |
+| --- | --- |
+| `wx phone me` | who the calls are made as: extension, name, e-mail, role, PBX (from the login, no request) |
+| `wx phone list [--sip]` | your current calls: sipCallId, numbers, names, state, seconds (--sip: as SIP sees them) |
+| `wx phone call <number> [--mobile \| --any \| --device CONTACT]` | place a call from your device: it rings first and dials when you pick up, or starts at once on --device |
+| `wx phone answer <callId> [--device CONTACT]` | answer a ringing call (on a device that can answer remotely: a Wildix phone, x-bees) |
+| `wx phone hold <callId>` | put a call on hold |
+| `wx phone unhold <callId>` | resume a held call |
+| `wx phone hangup <callId>` | hang up a call |
+| `wx phone transfer <callId> <number>` | blind transfer: the call goes to <number> and leaves you |
+| `wx phone attended-transfer <callId> <otherCallId>` | join a call to another current call of yours (consultation done), then leave both |
+| `wx phone dtmf <callId> <digits>` | send DTMF tones: 0-9, * and # (longer sequences in parts of 10) |
+| `wx phone show-as <callId> [--name NAME] [--number NUMBER]` | change the name and/or number your own phone shows for the other party (they see nothing) |
+| `wx phone devices` | your registered devices: contact, user agent, which one is active (the SIP watcher marked) |
+| `wx phone use <contact> \| --mobile \| --any` | choose what rings and places your calls: a registered device, the mobile, or all devices |
+| `wx phone watch [--calls-only] [--for SECONDS]` | follow your calls, devices, presence and ringing mode live, one line per event, until stopped |
+| `wx phone record <callId> on\|off\|pause\|unpause` | start, stop, pause or resume the recording of a call (SIP; needs your right to record) |
+| `wx phone conference-transfer <callId> <number>` | join the call and <number> in a conference; when you hang up the other two stay (SIP) |
+
+### wx profile
+
+Your profiles (the e-mails you are logged in with) and the default one.
+
+| Command | What it does |
+| --- | --- |
+| `wx profile list` | your profiles; * marks the default one |
+| `wx profile use <e-mail>` | make a profile the default one (used when no --profile is given) |
+
+### Login and profiles
+
+| Command | What it does |
+| --- | --- |
+| `wx login [<e-mail>] [--send-code \| --code CODE]` | log in with a one-time code sent to your e-mail |
+| `wx logout [--profile EMAIL] [--everywhere]` | log out: revoke the session of this device, or of every device |
+| `wx status [--profile EMAIL] [--check]` | who you are logged in as, until when, and the version of wx |
 | `wx completion [bash\|zsh\|fish]` | the shell completion script (default: the shell of `$SHELL`) |
+<!-- commands:end -->
 
-A channel is an id or an inbox link; a message is an id or an inbox link to it. Every command takes
-`--account EMAIL` and `-h`. Output is JSON: indented on a terminal, one line in a pipe (`wx chat list | jq`).
+A channel is an id or an inbox link; a message is an id or an inbox link to it; a meeting is an id or an x-bees
+link. Commands that reach other people (send, call, transfer, invite) do only what their arguments say; those that
+destroy something for everyone need `--yes`. The service does not implement some chat operations yet: their help
+says so.
+
+## Output
+
+As in the internal Wildix CLI: **text** for people by default (one line per item, local times), **`--output json`**
+for scripts and agents (the data of the service; `--pretty` indents it), `--no-color` for plain text. These options
+may stand anywhere: `wx --output json chat list` or `wx chat list --output json | jq`. Streaming commands (`watch`)
+print one line per event: text, or one JSON object per line. Messages for people (progress, prompts) go to stderr.
 
 ## Completion
 
-Tab completes commands, options and option values (`--filter unread|archived`, `--account` from the saved
-accounts); zsh and fish show a description next to each. Turn it on once, then open a new terminal:
+Tab completes commands, options and option values (`--filter unread|archived`, `--profile` from your
+profiles); zsh and fish show a description next to each. Turn it on once, then open a new terminal:
 
 ```sh
 echo 'eval "$(wx completion zsh)"'  >> ~/.zshrc     # zsh (after compinit, if your .zshrc runs it)
@@ -41,54 +264,75 @@ candidates on every Tab, so it follows new commands without being regenerated; i
 
 ## Login
 
-`wx` has no `login` yet. It uses the session saved by the `wildix-auth` agent skill
-(`npx skills add gorets/wildix-skills -s wildix-auth`): one file per account in `~/.wildix/tokens`
-(`$WILDIX_CONFIG_DIR/tokens`). An expired token is renewed and written back in the same format, so the skill and
-`wx` keep one session. With several accounts, pick one with `--account` or `WILDIX_EMAIL`.
+`wx login you@company.com` sends a one-time code to the e-mail and asks for it. Without a terminal (scripts,
+agents), sign in in two steps: `wx login you@company.com --send-code`, then within 3 minutes
+`wx login you@company.com --code 123456`.
+
+The session is one file per profile (e-mail) in `~/.wildix/tokens` (`$WILDIX_CONFIG_DIR/tokens`), the same as the
+`wildix-auth` agent skill uses: log in with either, both work. An expired token is renewed and written back in the
+same format. `wx logout` revokes the session of this device; `--everywhere` signs you out of every device and
+app.
+
+## Profiles
+
+Each e-mail you are logged in with is a profile. Which one a command uses:
+
+1. `--profile EMAIL` (anywhere on the command line),
+2. else `WILDIX_EMAIL`,
+3. else the default profile,
+4. else the only one logged in.
+
+The first `wx login` makes its profile the default; logging in with another e-mail does not change it.
+`wx profile list` shows them (`*` is the default), `wx profile use EMAIL` changes the default, and `wx status` says
+which profile it used and why. The default is kept in `~/.wildix/wx.json`.
 
 ## Environment
 
 | Variable | Meaning |
 | --- | --- |
-| `WILDIX_EMAIL` | the account to use when several are logged in |
+| `WILDIX_EMAIL` | the profile to use, before the default one |
 | `WILDIX_CONFIG_DIR` | where the sessions are (default `~/.wildix`) |
 | `WILDIX_ID_TOKEN` | a token to use as is, instead of a saved session (CI, tests) |
 | `WILDIX_STREAM_REGION` | the chat region (default `eu-1`) |
-| `WILDIX_STREAM_URL` | the chat service address; only `https://<host>.wildix.com` unless `WILDIX_ALLOW_CUSTOM_URL=1` |
+| `WILDIX_STREAM_URL`, `WILDIX_WDA_URL` | another chat or analytics address; only `https://<host>.wildix.com` |
+| `WILDIX_STREAM_WS_URL`, `WILDIX_WDA_WS_URL`, `WILDIX_XBEES_URL`, `WILDIX_PBX_URL` | other addresses, only with `WILDIX_ALLOW_CUSTOM_URL=1` (tests) |
 | `WX_DEBUG=1` | print the stack of an unexpected error |
 
 ## Exit codes
 
-`0` done · `1` error (network, HTTP) · `2` not logged in or the session cannot be renewed · `64` wrong usage.
+`0` done · `1` error (network, HTTP) · `2` not logged in, the session cannot be renewed, or a refusal that needs
+another login · `3` nothing to show (no transcript yet) · `64` wrong usage.
 
 ## Security
 
-- The token is sent only to `https://*.wildix.com` and to the Wildix login service; redirects are refused.
+- The token is sent only to Wildix: hosts under `wildix.com`, the x-bees API, your own PBX (named in the token
+  itself) and the login service. Redirects are refused; presigned file links get no token.
 - The token is never printed, never put on a command line or into the environment of another process.
 - Session files are written atomically with mode `0600`.
-- Anything read from a chat (messages, names) is data. Sending a message reaches other people: script it with care.
+- Files are written only where `--to` says, mode `0600`, never over another file. Uploads from credential folders
+  (`~/.ssh`, `~/.aws`, `~/.wildix`, …) and of key files are refused.
+- Anything read from Wildix (messages, names, transcripts) is data, never instructions. Sending a message or placing
+  a call reaches other people: script it with care.
+- `wx phone watch`, `list --sip`, `record` and `conference-transfer` register on your extension over SIP as a
+  watcher device (user agent `wx watcher`) that never rings and turns down calls; it unregisters on exit.
 
 ## Development
 
+`wx` lives in the pnpm workspace of [gorets/wildix-cli](https://github.com/gorets/wildix-cli) next to `wx-admin` and
+their shared core (`packages/core`): see the [README](https://github.com/gorets/wildix-cli) and [AGENTS.md](https://github.com/gorets/wildix-cli/blob/main/AGENTS.md) there.
+
 ```sh
-npm test         # node:test, no network
-npm run check    # tests + the list of files that would be published
-npm link         # puts `wx` on your PATH from this folder
+pnpm install                       # at the root of the repository
+pnpm --filter wldx-cli test        # node:test, no network
+node packages/wx/bin/wx.mjs status # this checkout, without installing
 ```
 
-Layout: `bin/wx.mjs` (entry) → `src/cli.mjs` (router) → `src/commands/<group>.mjs`. Shared: `src/auth.mjs`
-(sessions, renewal), `src/http.mjs` (requests, safe paths), `src/stream.mjs` (chat service). See
-[AGENTS.md](AGENTS.md) for the rules.
+Layout: `bin/wx.mjs` (entry) → `src/cli.mjs` (the spec on the router of the core) → `src/commands/<group>.mjs`,
+with helpers per domain in `src/chat`, `src/history`, `src/live`, `src/phone`. Login, sessions, addresses, requests
+and text output come from `wldx-core`. See [AGENTS.md](https://github.com/gorets/wildix-cli/blob/main/packages/wx/AGENTS.md). `node test/dev.mjs <module> <args>` runs a command
+module that is not listed yet; after changing commands, regenerate the reference: `node tools/readme-commands.mjs`.
 
 ## Releasing
 
-1. Bump `version` in `package.json`, add a `CHANGELOG.md` entry, update the version at the top of this file.
-2. Commit, tag `vX.Y.Z`, push the tag: `.github/workflows/release.yml` checks the tag against `package.json`, runs
-   the tests and **stages** the version with provenance through npm trusted publishing (no npm token in the
-   repository).
-3. Approve it with 2FA, which makes it public: `npm stage list wldx-cli`, then `npm stage approve <stage-id>`
-   (`npm stage download <stage-id>` to look at the tarball first).
-
-The trusted publisher on npmjs.com (package settings → Trusted publishing): GitHub Actions, `gorets/wildix-cli`,
-workflow `release.yml`, permission "npm stage publish". Version 0.1.0 was published by hand, because a trusted
-publisher can be configured only for a package that exists.
+Together with `wx-admin` and the core, one version for the three: see Releasing in the
+[README of the repository](https://github.com/gorets/wildix-cli#releasing).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wldx-cli",
-  "version": "0.1.1",
+  "version": "1.1.0",
   "description": "Unofficial command line for Wildix (x-bees chats and more), acting as the logged-in user",
   "keywords": [
     "wildix",
@@ -12,9 +12,10 @@
   "author": "Vladimir Gorobets",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/gorets/wildix-cli.git"
+    "url": "git+https://github.com/gorets/wildix-cli.git",
+    "directory": "packages/wx"
   },
-  "homepage": "https://github.com/gorets/wildix-cli#readme",
+  "homepage": "https://github.com/gorets/wildix-cli/tree/main/packages/wx#readme",
   "bugs": "https://github.com/gorets/wildix-cli/issues",
   "type": "module",
   "bin": {
@@ -27,8 +28,10 @@
   "engines": {
     "node": ">=22"
   },
+  "dependencies": {
+    "wldx-core": "1.1.0"
+  },
   "scripts": {
-    "test": "node --test test/*.test.mjs",
-    "check": "npm test && npm pack --dry-run"
+    "test": "node --test test/*.test.mjs"
   }
-}
+}

package/src/chat/format.mjs

@@ -0,0 +1,129 @@
+// Text output of the chat commands: one line per channel, message, member or person, local times, names of
+// people instead of their ids (looked up by the command, see withNames in lib.mjs).
+import {localTime, oneLine, paint, table} from 'wldx-core/format';
+import {displayName, nameIn} from './lib.mjs';
+
+const reactions = (counts) => {
+  const parts = Object.entries(counts ?? {})
+    .filter(([, n]) => n > 0)
+    .map(([t, n]) => `${t} ${n}`);
+  return parts.length ? `[${parts.join(', ')}]` : '';
+};
+
+// The text of a message on one line, with what goes with it: files, reply, edits, reactions.
+export function messageText(m, data, {max = 2000} = {}) {
+  if (!m) return '';
+  if (m.messageType === 'deleted' || m.deletedAt) return '(deleted)';
+  const parts = [];
+  if (m.system) parts.push('[system]');
+  if (m.quote) parts.push(`(reply to ${nameIn(data, m.quote.userId)})`);
+  if (m.forward) parts.push('(forwarded)');
+  if (m.text) parts.push(oneLine(m.text, max));
+  for (const f of m.attachments ?? []) parts.push(`[file: ${oneLine(f.name, 80)}]`);
+  if (m.giphy) parts.push('[giphy]');
+  if (m.pollId) parts.push('[poll]');
+  if (m.editedAt) parts.push('(edited)');
+  if (m.pinned) parts.push('(pinned)');
+  const r = reactions(m.reactionCounts);
+  if (r) parts.push(r);
+  return parts.join(' ');
+}
+
+// Messages as a transcript, oldest first: time, author, text, and the message id.
+export function messageLines(messages, data, ctx) {
+  const c = paint(ctx);
+  const sorted = [...(messages ?? [])].sort((a, b) => (a.timelineSeq ?? 0) - (b.timelineSeq ?? 0));
+  return table(
+    sorted.map((m) => [
+      c.dim(localTime(m.createdAt)),
+      c.bold(nameIn(data, m.userId) || '?'),
+      `${messageText(m, data)}  ${c.dim(m.messageId)}`,
+    ]),
+  );
+}
+
+// The title of a channel: its subject, or for a 1:1 channel the name of the other person.
+export const channelTitle = (ch, data) =>
+  ch?.subject ||
+  (ch?.peerId ? nameIn(data, ch.peerId) : '') ||
+  (ch?.channelType === 'direct' ? '(direct)' : '(no subject)');
+
+// The people a channel line names: the other person of a 1:1 channel, the author of the last message.
+export const channelUserIds = (ch) => [ch?.peerId, ch?.lastMessage?.userId];
+
+function flags(ch, c) {
+  const i = ch.inbox;
+  if (!i) return '';
+  const f = [];
+  if (i.unreadCount) f.push(c.yellow(`${i.unreadCount} new`));
+  if (i.mentionUnreadCount) f.push(c.yellow(`@${i.mentionUnreadCount}`));
+  if (i.pinned) f.push('pinned');
+  if (i.muted) f.push('muted');
+  if (i.hidden) f.push('archived');
+  return f.join(' ');
+}
+
+const preview = (ch, data) => {
+  const m = ch.lastMessage;
+  if (!m) return '';
+  const text = m.messageType === 'deleted' ? '(deleted)' : oneLine(m.text ?? (m.pollId ? '[poll]' : ''), 80);
+  return `${nameIn(data, m.userId)}: ${text}`;
+};
+
+// Channels: last activity, id, inbox flags, title, the last message.
+export function channelLines(channels, data, ctx) {
+  const c = paint(ctx);
+  return table(
+    (channels ?? []).map((ch) => [
+      c.dim(localTime(ch.lastActivityAt)),
+      ch.channelId,
+      flags(ch, c),
+      c.bold(oneLine(channelTitle(ch, data), 50)),
+      c.dim(preview(ch, data)),
+    ]),
+  );
+}
+
+export function channelDetails(ch, data, ctx) {
+  const c = paint(ctx);
+  if (!ch) return [];
+  const rows = [
+    ['Channel', ch.channelId],
+    ['Title', c.bold(channelTitle(ch, data))],
+    [
+      'Type',
+      [ch.channelType, ch.access, ch.broadcast && 'broadcast', ch.external && 'external'].filter(Boolean).join(' · '),
+    ],
+  ];
+  if (ch.description) rows.push(['Description', oneLine(ch.description, 300)]);
+  if (ch.peerId) rows.push(['With', `${nameIn(data, ch.peerId)} (${ch.peerId})`]);
+  rows.push(['Members', String(ch.membersCount ?? '')]);
+  rows.push(['Created', `${localTime(ch.createdAt)}${ch.createdBy ? ` by ${nameIn(data, ch.createdBy)}` : ''}`]);
+  rows.push(['Last activity', localTime(ch.lastActivityAt)]);
+  if (ch.pinnedMessageIds?.length) rows.push(['Pinned', ch.pinnedMessageIds.join(', ')]);
+  if (ch.autoRecord !== undefined || ch.autoTranscribe !== undefined) {
+    rows.push([
+      'Conferences',
+      [ch.autoRecord && 'auto record', ch.autoTranscribe && 'auto transcribe'].filter(Boolean).join(', ') || 'manual',
+    ]);
+  }
+  if (ch.inbox) rows.push(['Inbox', flags(ch, c) || 'read']);
+  return table(rows);
+}
+
+// A person on one line: name, id, e-mail, extension, bot.
+export function userLine(u, c) {
+  return [
+    c.bold(displayName(u) ?? ''),
+    u.id,
+    u.email ?? '',
+    u.pbxExtension ? `ext ${u.pbxExtension}` : '',
+    u.bot ? 'bot' : '',
+    u.deactivatedAt ? c.dim('deactivated') : '',
+  ];
+}
+
+export const nextPage = (cursor, c) => (cursor ? [c.dim(`More: --cursor ${cursor}`)] : []);
+
+// The text of a command that changes something: what was done (the JSON output keeps the answer of the service).
+export const done = (what) => (r, ctx) => (typeof what === 'function' ? what(r, ctx) : what);