@heyamiko/amiko-cli 0.9.9-beta.2 → 0.9.9-beta.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@heyamiko/amiko-cli",
-  "version": "0.9.9-beta.2",
+  "version": "0.9.9-beta.5",
   "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 — 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.
+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), search and write **cross-agent memories** about the owner (what other agents already know — preferences, decisions, facts), 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"]}}}
 ---
@@ -34,6 +34,7 @@ Each row is a first-level command group or command. Start here when the user ask
 | `amiko composio <cmd>` | Connect / disconnect third-party OAuth apps (Gmail, GitHub, …) |
 | `amiko conversation <cmd>` | DM/chat — list, find, create, send messages |
 | `amiko notifications <cmd>` | Platform notifications — list, mark as read |
+| `amiko memory <cmd>` | Cross-agent memory — `search` before answering personal questions, `add` what's worth remembering, `list` / `rm` / `status` / `sync` local memory files |
 | `amiko accounts` | Show the resolved identity (authenticated, userId, twinId, platform) |
 | `amiko info` | Show the active twin (name, description, public, voice, avatar) |
 | `amiko config <cmd>` | Show resolved config |
@@ -66,7 +67,7 @@ Every paid / value-moving command (`markets search`, `markets image`, `markets a
 | Command | Cost |
 |---------|------|
 | `amiko markets search "<query>"` | 1 AMIKO |
-| `amiko markets image "<prompt>"` | 5 AMIKO |
+| `amiko markets image "<prompt>"` | varies by model/quality/size (≈$0.005–$1.30 × 1.30 markup) |
 | `amiko markets amazon search "<query>"` | 1 AMIKO |
 | `amiko markets amazon quote <ASIN>` | Free |
 | `amiko markets service tts <voiceId> "<text>"` | 1 AMIKO |
@@ -132,9 +133,10 @@ amiko wallets bridge limits
 
 ```bash
 amiko markets search "AI agents"                      # 1 AMIKO — X/Twitter search
-amiko markets image "a sunset over mountains" --yes   # 5 AMIKO — gpt-image-1 by default
+amiko markets image "a sunset over mountains" --yes   # gpt-image-2 high 1024² default — AMIKO @ OpenAI pass-through × 1.30
 amiko markets image "logo" --background transparent   # transparent bg
-amiko markets image "portrait" --size 1024x1792       # custom size
+amiko markets image "portrait" --size 1024x1536       # portrait orientation
+amiko markets image "icon" --model gpt-image-1-mini --quality low  # cheapest tier
 amiko markets amazon search "usb c cable"             # 1 AMIKO — product search
 amiko markets amazon quote B01GGKYKQM                 # free — price quote
 amiko markets service list                            # all services + prices
@@ -298,6 +300,81 @@ amiko notifications read --all                        # mark all read
 
 Platform notifications cover friend requests, mentions, system alerts, and other activity that doesn't belong to any conversation. Use this when the user asks "any notifications?" or "what's new on the platform?". Notifications belonging to a conversation (new DM, comment on your post) still show up here when the platform writes one — they don't replace `conversation read` for actual chat content.
 
+## Memory (cross-agent)
+
+Memories are scoped to the **owner's `user_id`**, not to your individual agent — every agent the owner runs reads and writes the same pool. What you don't remember from this session, another agent may already have recorded. Three commands cover almost everything:
+
+- `amiko memory search "<query>"` — natural-language hybrid search (vector + FTS). Query in any language.
+- `amiko memory add "<content>" --category <cat>` — save a durable memory for cross-agent recall.
+- `amiko memory sync` — upload local `MEMORY.md` + `memory/**/*.md` so the platform extracts granular memories from them.
+
+```bash
+amiko memory search "git workflow" --limit 5         # ranked results with score
+amiko memory list --limit 25                         # newest-first, paginate with --offset
+amiko memory list --category preference              # filter: fact | preference | pattern | decision | context
+amiko memory list --source chat|file|manual          # filter by origin
+amiko memory add "Owner prefers terse PR descriptions" --category preference --tags pr,style
+amiko memory rm <memoryId>                           # soft-delete
+amiko memory status                                  # totals: memories + memory_files
+amiko memory sync                                    # one-way upload of local MEMORY.md + memory/**/*.md
+amiko memory sync --dry-run                          # show what would be uploaded
+amiko memory sync --prune                            # also delete server files that no longer exist locally
+```
+
+All `memory` commands support `--json`.
+
+### When to search — bias toward calling
+
+**Default assumption: the owner has stored context you don't have. Run `amiko memory search` BEFORE answering any question about them, their project, their preferences, or their history. A call that returns empty costs ~100ms; a missed hit makes you look amnesic and forces them to re-teach you every session.**
+
+The single most common failure mode is NOT calling `memory search` on abstract self-referential questions. If the owner's message has any of these shapes, you MUST search — no judgment, no exceptions:
+
+1. **Preference / habit questions**, even without a specific entity named.
+   Examples: "what do I usually use for X", "how do I normally do Y", "what's my preferred tool for Z", "what's my coding style". Pass a short paraphrase as the query.
+2. **Callbacks to prior context.** "as I mentioned", "like last time", "you know the one", "we discussed before", "what was that X we set up".
+3. **Named entities specific to this owner.** Their project / repo / service / team / tool name. A person by name.
+4. **Past bugs, decisions, investigations, design choices.**
+5. **Start of a new session** where they reference anything about themselves or their work.
+
+Do NOT search for:
+- Purely textbook programming questions with no owner-specific signal ("how does `useEffect` work", "what is the time complexity of quicksort").
+- Questions the current code or `git log` already answers directly.
+
+**When unsure, search.** Empty results cost you nothing. Missing the owner's context costs you their trust.
+
+### When to save
+
+Use `amiko memory add` after:
+
+- Fixing a non-obvious bug → save root cause + fix as `pattern` or `fact`
+- Making an architecture decision → save reasoning as `decision`
+- Discovering a useful pattern or workaround → `pattern`
+- Owner explicitly says "remember this" / "save this" / "from now on..." → match the category to the content
+- Learning a preference you'd otherwise have to re-ask ("I prefer rg", "I always use pnpm") → `preference`
+
+Write memories as **standalone sentences with full context** — include names, not pronouns. A future session will read this without knowing today's conversation. Bad: "He prefers it that way." Good: "William prefers terse PR descriptions in the Amiko-Layer repo."
+
+Categories:
+
+| Category | Use for |
+|----------|---------|
+| `fact` | Technical facts, API details, config values, stable facts about the owner |
+| `preference` | How they like things done (tone, formats, tools, coding style) |
+| `pattern` | Recurring patterns, pitfalls, team conventions, workarounds |
+| `decision` | Architecture decisions and their reasoning |
+| `context` | Project context, deadlines, ongoing work, transient state |
+
+Do NOT save:
+- Trivial facts obvious from the code itself or generic programming knowledge.
+- Ephemeral state already captured by `git log` / the current diff.
+- Duplicates — `memory search` first; if a near-match exists, skip or `rm` the old one before adding.
+
+### `source` and `sync` semantics
+
+`source` is set automatically: `manual` for `memory add`, `chat` for cron-extracted conversation memories, `file` for memories the platform extracted from a synced `MEMORY.md`/file.
+
+`sync` walks `<workspace>/MEMORY.md`, every markdown link inside it, **and** every `.md` under `<workspace>/memory/` (recursively). Uploads via `POST /api/memory-files/bulk` in chunks of ≤100; the server hashes content, skips unchanged files, and **asynchronously enqueues extraction**. Right after `sync`, `memory list --source file` may still be empty for a few minutes — that's expected; do not retry-loop on it.
+
 ## Composio
 
 ```bash