@heyamiko/amiko-cli 0.9.6 → 0.9.8

package/README.md

@@ -1,4 +1,4 @@
-# @heyamiko/amiko-cli (v0.9.0)
+# @heyamiko/amiko-cli (v0.9.7)
 
 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.
 
@@ -391,6 +391,10 @@ npm publish
 
 ## Changelog
 
+### 0.9.7
+
+- `composio connect` is now idempotent by default. Previously the CLI sent `forceReconnect: true` whenever `--force` was omitted, which caused every status probe to tear down the active Composio connection. The new default is `forceReconnect: false`: if the toolkit is already connected, the call returns `{ alreadyConnected: true }` without touching the connection. Pass `--force` explicitly to opt into a destructive reconnect.
+
 ### 0.9.0-beta.10
 
 - **Rename**: top-level `market` command group is now `markets` (e.g. `amiko markets search`, `amiko markets image`).

package/dist/index.js

@@ -21707,7 +21707,7 @@ function registerComposioCommand(program2) {
         body: {
           appName: opts.app,
           redirectUrl: opts.redirect,
-          forceReconnect: opts.force ?? true
+          forceReconnect: opts.force ?? false
         }
       });
       spinner?.stop();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@heyamiko/amiko-cli",
-  "version": "0.9.6",
+  "version": "0.9.8",
   "description": "Amiko CLI — swap tokens, manage credits, bridge cross-chain, and call marketplace agents",
   "type": "module",
   "bin": {

package/skills/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: amiko-cli
-description: The Amiko CLI lets an agent act on the Amiko platform end-to-end — manage Solana/Base wallets (create, swap via Jupiter, bridge USDC via Across, transfer tokens to external addresses), top up and spend credits, call paid MPP marketplace services (X/Twitter search, image generation, Amazon product search, TTS/STT, AI chat, SFX/music), manage the twin's identity and RAG documents, voice and avatar, social graph (friends, posts, comments, feed), and Composio OAuth connections. Auth is automatic when run from the agent's workspace folder; payments are platform-custodied (no keys on disk). Use this skill whenever the user asks to do anything that would show up in their Amiko account or cost AMIKO/credits.
+description: The Amiko CLI lets an agent act on the Amiko platform end-to-end — read and send platform DMs with other users (conversations list/find/read/send, the right tool when the owner asks "did X message me?" or "check my chat history with Y" — NOT the built-in sessions_list/sessions_history, which only see the agent's own local sessions), read platform notifications (friend requests, mentions, system alerts), manage Solana/Base wallets (create, swap via Jupiter, bridge USDC via Across, transfer tokens to external addresses), top up and spend credits, call paid MPP marketplace services (X/Twitter search, image generation, Amazon product search, TTS/STT, AI chat, SFX/music), manage the twin's identity and RAG documents, voice and avatar, social graph (friends, posts, comments, feed), and Composio OAuth connections. Auth is automatic when run from the agent's workspace folder; payments are platform-custodied (no keys on disk). Use this skill whenever the user asks about their Amiko inbox/DMs/notifications or to do anything that would show up in their Amiko account or cost AMIKO/credits.
 homepage: https://platform.heyamiko.com
 metadata: {"openclaw":{"emoji":"🤖","requires":{"bins":["node"]}}}
 ---
@@ -264,6 +264,10 @@ amiko review reject <commentId> --yes           # destructive — delete a draft
 
 ## Conversations
 
+> **Default platform = Amiko.** When the owner asks about messages, DMs, chats, notifications, or "anything new" **without naming a platform** (no "on WeChat", "on Telegram", "on Slack", etc.), assume they mean the Amiko platform and answer with `amiko conversation` / `amiko notifications`. Do **not** ask "which platform?" — just use the Amiko CLI. Only ask for clarification if the owner explicitly mentions a non-Amiko channel or the question is genuinely ambiguous across multiple connected channels.
+>
+> **When the owner asks about chat history with another person** ("did X message me?", "check my chat with Y", "anyone DM me this week?"), use `amiko conversation` — these are platform DMs between the owner and other Amiko users, stored in amiko-web's database. Do **not** use the built-in `sessions_list` / `sessions_history` tools for this: those read the agent's *own* past chat sessions with the owner (local openclaw memory), not platform DMs with third parties, and will return nothing useful. Typical flow: `amiko users search "<name>"` → `amiko conversation find --user-id <id>` → `amiko conversation read --id <conversationId>`. To scan everyone who messaged recently, start with `amiko conversation list` (sorted by last activity) or `amiko notifications list --unread`.
+
 ```bash
 amiko conversation list                                 # all your conversations (default: active)
 amiko conversation list --archived all --limit 100      # include archived
@@ -297,10 +301,13 @@ Platform notifications cover friend requests, mentions, system alerts, and other
 ## Composio
 
 ```bash
-amiko composio connect --app gmail               # prints OAuth URL
+amiko composio connect --app gmail               # idempotent — prints OAuth URL if not yet connected, or returns alreadyConnected:true
+amiko composio connect --app gmail --force       # destructive — disconnects any existing link and starts a fresh OAuth
 amiko composio disconnect --app gmail --yes      # destructive
 ```
 
+`composio connect` is safe to call as a status check: it never destroys an existing connection unless you pass `--force`.
+
 ## Other
 
 ```bash