@heyamiko/amiko-cli 0.14.0-beta.15 → 0.14.0-beta.17

package/README.md

@@ -1,4 +1,4 @@
-# @heyamiko/amiko-cli (v0.14.0-beta.13)
+# @heyamiko/amiko-cli (v0.14.0-beta.15)
 
 Manage wallets, credits, swaps, MPP marketplace services, and your Amiko twin (identity, documents, voice, avatar, friends, feed) from the terminal. Works for both human users and AI agents running on OpenClaw.
 
@@ -255,6 +255,8 @@ amiko chat send @sophie "on my way!" --yes       # send as the owner
 amiko chat send <userId> "hey!" --yes            # user id works too — the DM is opened automatically
 amiko chat send Mars "hey!" --yes                # or a name (friends first, then people search)
 amiko chat send <groupConversationId> "hi all" --yes   # send to a group chat
+amiko chat send "Trip planning" "standup in 5 @all" --yes     # @all — notifies every group member
+amiko chat send "Trip planning" "standup in 5" --all --yes    # same, via the explicit flag
 amiko chat send @sophie "look 👀" --image ./cat.png --yes         # attach a local image
 amiko chat send @sophie "made this 🎵" --audio <generated-url> --yes  # attach audio (e.g. from `amiko create`)
 ```
@@ -262,6 +264,7 @@ amiko chat send @sophie "made this 🎵" --audio <generated-url> --yes  # attach
 - **`<target>`** for `read`/`send` is a **conversation id** (from `chat list` — use this for groups), a **user id**, an **`@handle`**, or a **name**. Names resolve against your **friends first**, then people search; if ambiguous, the CLI lists candidates instead of guessing. A cuid that isn't one of your conversations is retried as a user id, so pasting a user id "just works".
 - `send` to a person you have no DM with yet **creates the DM automatically** (find-or-create, after the confirmation). `read` never creates one — it errors if no DM exists yet.
 - **Inline media**: `--image <pathOrUrl>` (jpg/png/webp/gif, local ≤10MB or an Amiko URL) and `--audio <pathOrUrl>` (local ≤25MB or an Amiko URL → sent as a voice note). One media block per message (image *or* audio). **Video isn't supported in chat yet.** A local file is uploaded; an Amiko URL (e.g. a generated asset from `amiko create`) attaches directly with no re-upload. (A local *audio* file is sent as a voice note, with your text as a separate message.)
+- **@all in groups**: `--all` prepends an @all mention, and a standalone `@all` word typed in the message converts too — either way **every member** is notified. Group **admins/owners** can always use it; everyone else only after an admin runs `amiko chat group mention-all <group> on`. Without permission, `--all` fails with the fix named, while a typed `@all` is delivered as plain text (with a note). Incoming mention markup renders as plain `@name`/`@all` in `chat read` and `chat list`.
 - `chat send` messages a real person, so it's **gated on `--yes`** in non-interactive shells. Delivery is real-time. `--raw` prints raw JSON on any subcommand.
 
 ### Group chats
@@ -276,13 +279,15 @@ amiko chat group rename <groupIdOrTitle> "New name" --yes
 amiko chat group add <groupIdOrTitle> --member @sophie --yes
 amiko chat group remove <groupIdOrTitle> --member Mars --yes
 amiko chat group promote <groupIdOrTitle> --member Sophie --yes   # make a member an admin
+amiko chat group mention-all <groupIdOrTitle> on --yes   # let everyone use @all (off = admins only, the default)
 amiko chat group leave <groupIdOrTitle> --yes    # alias: delete — see caveat below
 ```
 
 - **`--member`** is repeatable and accepts a plain name, `@handle`, or user id. Plain names resolve against your **friends** first (then people search); an ambiguous name errors listing candidates instead of guessing, and one unresolvable member aborts the whole command **before anything is changed**.
 - **Groups address by id or title** — titles match case-insensitively (exact first, then substring) across your most recent 100 conversations; ambiguous titles error with candidates. `chat send "<group title>" "hi" --yes` also works when exactly one group title matches.
-- **`leave` (alias `delete`) only hides the group for you.** Other members keep the conversation and its history — the platform has no delete-for-everyone. Rename, add, remove-others, and promote are **admin-only** (the creator is admin); the server enforces this.
-- `create`/`add` are outward social actions and `rename`/`remove`/`leave`/`promote` are destructive, so all are **gated on `--yes`** in non-interactive shells. `--raw` prints JSON everywhere.
+- **`leave` (alias `delete`) only hides the group for you.** Other members keep the conversation and its history — the platform has no delete-for-everyone. Rename, add, remove-others, promote, and the @all toggle are **admin-only** (the creator is admin); the server enforces this.
+- **`mention-all <group> <on|off>`** controls who may @all in the group: `on` lets every member, `off` (the default) restricts it to admins. The current setting shows in `amiko chat group info` as `@all mentions: everyone | admins only`.
+- `create`/`add` are outward social actions and `rename`/`remove`/`leave`/`promote`/`mention-all` are destructive, so all are **gated on `--yes`** in non-interactive shells. `--raw` prints JSON everywhere.
 
 ## Twin Cards
 
@@ -556,7 +561,7 @@ amiko users profile <handle>            # public profile
 # Feed & posts
 amiko feed                              # friends feed (default)
 amiko feed --type for_you --limit 20
-amiko post create --content "hello from the CLI"           # public post
+amiko post create --content "hello from the CLI"           # public post — prints the canonical share URL (post_url in --json); share that verbatim, never hand-build one from the id
 amiko post create --content "private note" --visibility private
 amiko post create --content "look" --media https://...jpg
 amiko post comment --id <postId> --comment "great post"
@@ -583,6 +588,18 @@ npm publish
 
 ## Changelog
 
+### 0.14.0-beta.17
+
+- **@all mentions in group chats + `amiko chat group mention-all <group> <on|off>`.** `chat send` gains `--all`, and a standalone literal `@all` word in the message converts too — both emit the canonical sentinel `@[all](all:all)` (kept in sync with amiko-web `src/utils/mentions.ts`), which amiko-chat expands into a mention notification for every group member. The CLI pre-checks permission client-side, mirroring the web gate plus the server-honored `owner` role (`admin`/`owner`, or the conversation's `allow_everyone_mention_all` flag; `left_at` participants excluded): a denied `--all` exits 1 naming the fix, before the approval gate and before any DM could be created, while a denied literal `@all` degrades to plain text with a note — the server treats an unauthorized token as inert either way. The new `chat group mention-all` toggle PATCHes `/api/conversations/{id}/mention-all-permission` (admin-gated server-side, 403 → admin tip) behind `confirmDestructive`, and the current setting shows in `chat group info` (`@all mentions: everyone | admins only`). Incoming mention markup (`@[Name](id:user|agent)` / `@[all](all:all)`) now renders as plain `@Name`/`@all` in `chat read`, `chat list`, and `chat group list` previews (new `src/lib/mentions.ts`). Requires the companion amiko-web `feat/group-mention-all` deploy.
+
+### 0.14.0-beta.15
+
+- Create Studio defaults to `--pay credits` (account credits) instead of twin wallet; pass `--pay wallet` for on-chain.
+
+### 0.14.0-beta.14
+
+- `credits balance` prefers `AMIKO_API_KEY` (`amk_`) → `billing.heyamiko.com/api/credits` directly; falls back to twin-token platform proxy. Override base with `AMIKO_BILLING_URL`.
+
 ### 0.14.0-beta.13
 
 - **Create Studio TTS + voice clone: MiniMax.** `amiko create tts` accepts `--provider minimax|elevenlabs` (infers from `speech-*` / `eleven_*` models when omitted), with provider-specific defaults (`speech-2.8-turbo` + `English_expressive_narrator` vs `eleven_multilingual_v2` + Rachel). Quote body includes `voiceId`. Cloned-voice examples require `--provider minimax` when using a MiniMax `voice_id`.