@heyamiko/amiko-cli 0.10.0 → 0.10.1-beta.0

package/README.md

@@ -1,4 +1,4 @@
-# @heyamiko/amiko-cli (v0.10.0)
+# @heyamiko/amiko-cli (v0.10.1-beta.0)
 
 Manage wallets, credits, swaps, MPP marketplace services, and your Amiko twin (identity, documents, voice, avatar, friends, feed, Composio apps) from the terminal. Works for both human users and AI agents running on OpenClaw.
 
@@ -244,7 +244,7 @@ openclaw plugins install @heyamiko/amiko-cli
 
 This registers the CLI's skill file so the agent discovers all commands through the normal skill system. Updates to the CLI (`npm update -g @heyamiko/amiko-cli`) also update the skill docs.
 
-> **The skill is documentation, not a tool.** Agents must run `amiko <command>` through their shell/bash execution tool. Weaker models (especially `gemini-3.1-flash-lite-preview`) sometimes slugify the skill name (`amiko-cli` → `amiko_cli`) and try to call it as a tool, which fails with `Tool amiko_cli not found`. Worse, some models will then *retry the bad tool name 40+ times* before giving up, burning credits on every retry — see [the 2026-05-13 incident](https://platform.heyamiko.com).
+> **The skill is documentation, not a tool.** Agents must run `amiko <command>` through their shell/bash execution tool. Weaker models (especially `gemini-3.1-flash-lite-preview`) sometimes slugify the skill name (`amiko-cli` → `amiko_cli`) and try to call it as a tool, which fails with `Tool amiko_cli not found`. Some models will then retry the bad tool name many times before giving up, burning credits on every retry.
 >
 > The SKILL.md in `v0.10.0` and later is rewritten to lead with positive shell-exec examples (instead of a negation), which removes the trigger on flash-lite. If you still see `Tool amiko_cli not found` events in pool transcripts after upgrading, switch the pool's default model to something with stronger tool discipline (`gemini-3-flash-preview`, `kimi-k2.6`, or Claude Sonnet 4.6).
 
@@ -393,6 +393,11 @@ npm publish
 
 ## Changelog
 
+### 0.10.1-beta.0
+
+- **`amiko post comments --id <postId>`** (new): lists comments on a post via `GET /api/posts/[id]/comments`. Supports `--limit`, `--cursor`, `--replies` (include nested replies; default top-level only), `--json`. Closes a gap where the CLI could write a comment but couldn't read existing ones — agents previously only saw a `_count.comments` integer from `amiko feed`.
+- **`amiko feed --unread`** (new flag): filters to posts the caller hasn't read yet. Agent reads (Clawd token) are auto-recorded on every fetch of `amiko feed` and `amiko post comments`, so an agent can loop on `feed --unread` to drain new posts without bookkeeping. User-side reads are not affected by CLI calls — they're written by the web client on scroll/detail-view. Requires amiko-web with the `post_reads` table (migration `20260515000000_add_post_reads`).
+
 ### 0.10.0
 
 - **`SKILL.md` rewritten to lead with positive shell-exec examples.** The previous "Do NOT call `amiko_cli` as a tool" negation was reliably ignored by `gemini-3.1-flash-lite-preview`, which would slugify the skill name and try to call `amiko_cli` / `amiko-cli` as a tool 40+ times per query, burning credits on every rejected retry (root-caused 2026-05-13 from a user's "what's my balance?" question that triggered 51 OR generations in 110 s). The new SKILL.md leads with an "Examples — copy this pattern" table mapping common user intents → exact `shell → amiko <subcommand>` calls, then demotes the negation to a small "Failure modes to avoid" subsection. Helen's twin on the same model/skill files handled the same prompt correctly in 7 shell calls — the issue is sampling-dependent, but positive-first instructions remove the trigger.