@lark-project/meegle 1.0.9 → 1.0.10

package/CHANGELOG.md

@@ -8,6 +8,13 @@ versioned section on each npm release.
 
 ## [Unreleased]
 
+## [v1.0.10] - 2026-06-25
+
+### Fixed
+
+- `mywork todo` now adds an actionable troubleshooting suggestion when the backend returns `get action info fail`, pointing users to refresh command metadata and pass `--asset-key` for multi-workspace accounts.
+- Meegle runtime flags such as `--refresh` and `--profile` are no longer forwarded as backend tool parameters when passed explicitly on dynamic commands.
+
 ## [v1.0.9] - 2026-06-11
 
 ### Added

package/README.md

@@ -85,7 +85,15 @@ The default `meegle auth login` uses an arrow-key host picker plus a browser OAu
 npm install -g @lark-project/meegle
 ```
 
-**Step 2 — Persist the host**
+**Step 2 — Install the Agent Skill**
+
+> Recommended for AI-agent workflows, optional for direct CLI use. The skill teaches agents how to choose and run `meegle` commands correctly.
+
+```bash
+npx skills add larksuite/meegle-cli -y -g
+```
+
+**Step 3 — Persist the host**
 
 ```bash
 meegle config set host <host>
@@ -93,7 +101,7 @@ meegle config set host <host>
 
 Examples of `<host>`: `project.feishu.cn`, `meegle.com`, or your self-hosted tenant domain such as `your-tenant.example.com`.
 
-**Step 3 — Log in with Device Code**
+**Step 4 — Log in with Device Code**
 
 > Run this command in the background. It prints an authorization URL — extract it and send it to the user. The command exits automatically once the user completes authorization in the browser.
 
@@ -107,7 +115,7 @@ Alternatively, pass the host inline each time without persisting it:
 meegle auth login --device-code --host <host>
 ```
 
-**Step 4 — Verify**
+**Step 5 — Verify**
 
 ```bash
 meegle auth status
@@ -332,6 +340,11 @@ meegle mywork todo --action done --page-num 1
 meegle mywork todo --action overdue --page-num 1
 ```
 
+If `mywork todo` fails with `get action info fail`, refresh command metadata first:
+`meegle --refresh mywork todo --action this_week --page-num 1`. If your account
+belongs to multiple workspaces, pass the workspace key explicitly:
+`meegle mywork todo --action this_week --page-num 1 --asset-key Asset_xxx`.
+
 ### Querying Work Items
 
 ```bash

package/README.zh-CN.md

@@ -85,7 +85,15 @@ meegle inspect workitem.create
 npm install -g @lark-project/meegle
 ```
 
-**Step 2 — 持久化 host**
+**Step 2 — 安装 Agent Skill**
+
+> 推荐用于 AI Agent 场景；如果只是手动使用 CLI，则是可选步骤。Skill 会教 Agent 正确选择和执行 `meegle` 命令。
+
+```bash
+npx skills add larksuite/meegle-cli -y -g
+```
+
+**Step 3 — 持久化 host**
 
 ```bash
 meegle config set host <host>
@@ -93,7 +101,7 @@ meegle config set host <host>
 
 `<host>` 示例：`project.feishu.cn`、`meegle.com`，或自建租户域名（如 `your-tenant.example.com`）。
 
-**Step 3 — Device Code 登录**
+**Step 4 — Device Code 登录**
 
 > 建议后台执行。命令会输出授权 URL —— 提取后发给用户，用户在浏览器完成授权后命令自动退出。
 
@@ -107,7 +115,7 @@ meegle auth login --device-code
 meegle auth login --device-code --host <host>
 ```
 
-**Step 4 — 验证**
+**Step 5 — 验证**
 
 ```bash
 meegle auth status
@@ -332,6 +340,11 @@ meegle mywork todo --action done --page-num 1
 meegle mywork todo --action overdue --page-num 1
 ```
 
+如果 `mywork todo` 返回 `get action info fail`，先刷新命令元数据：
+`meegle --refresh mywork todo --action this_week --page-num 1`。如果账号同时属于多个工作区，
+请显式传入工作区 key：
+`meegle mywork todo --action this_week --page-num 1 --asset-key Asset_xxx`。
+
 ### 查询工作项
 
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lark-project/meegle",
-  "version": "1.0.9",
+  "version": "1.0.10",
   "description": "Agent-First CLI for Meegle (Lark Project)",
   "license": "MIT",
   "homepage": "https://github.com/larksuite/meegle-cli#readme",