feishu-user-plugin 1.3.0 → 1.3.2

package/skills/feishu-user-plugin/references/CLAUDE.md

@@ -6,7 +6,7 @@ All-in-one Feishu plugin for Claude Code with three auth layers:
 - **Official API** (app credentials): Read group messages, docs, tables, wiki, drive, contacts, upload files
 - **User OAuth UAT** (user_access_token): Read P2P chat history, list all user's chats
 
-## Tool Categories (76 tools)
+## Tool Categories (66 tools)
 
 ### User Identity — Messaging (reverse-engineered, cookie-based)
 - `send_to_user` — Search user + send text (one step, most common). Returns candidates if multiple matches.
@@ -14,7 +14,8 @@ All-in-one Feishu plugin for Claude Code with three auth layers:
 - `send_as_user` — Send text to any chat by ID, supports reply threading (root_id/parent_id)
 - `send_image_as_user` — Send image (requires image_key from `upload_image`)
 - `send_file_as_user` — Send file (requires file_key from `upload_file`)
-- `send_post_as_user` — Send rich text with title + formatted paragraphs
+- `send_post_as_user` — Send rich text with title + formatted paragraphs. Elements: `{tag:"text"}`, `{tag:"a",href,text}`, `{tag:"at",userId,name}`. **@-mentions trigger real notifications** (fixed by registering AT element IDs in RichText.atIds field 6 — reverse-engineered from Feishu Web bundle's AtProperty + RichText schemas).
+- `send_as_user` / `send_to_user` / `send_to_group` — plain text sends now accept optional `ats: [{userId, name}]`; the text must contain the `@<name>` marker for each entry. The marker is spliced into a real AT element so the mentioned user is notified. Identity is the cookie user (not bot).
 - `send_sticker_as_user` — Send sticker/emoji
 - `send_audio_as_user` — Send audio message
 
@@ -25,9 +26,10 @@ All-in-one Feishu plugin for Claude Code with three auth layers:
 - `get_user_info` — User display name lookup (official API first, cookie cache fallback)
 - `get_login_status` — Check cookie, app, and UAT status
 
-### User OAuth UAT Tools (P2P chat reading)
+### User OAuth UAT Tools (P2P chat reading + user-identity creation)
 - `read_p2p_messages` — Read P2P (direct message) chat history. chat_id accepts both numeric IDs (from create_p2p_chat) and oc_xxx format. Returns newest messages first by default.
 - `list_user_chats` — List group chats the user is in. Note: API only returns groups, not P2P. For P2P, use: `search_contacts` → `create_p2p_chat` → `read_p2p_messages`.
+- **All docx + bitable + drive create/read/write tools are UAT-first**: when UAT is configured, every operation (create/edit/delete doc blocks, bitable tables/fields/views/records, drive folders) tries the user's token first and falls back to app token on failure. This keeps resources consistently owned by the user and avoids 403 errors when the app can't access user-created resources. Read-only tools (e.g. `read_doc`, `get_doc_blocks`, `list_bitable_tables`) are also UAT-first so user-owned resources remain readable.
 
 ### Official API Tools (app credentials)
 - `list_chats` / `read_messages` — Chat history (read_messages accepts chat name, oc_ ID, or numeric ID; auto-resolves via bot's group list → im.chat.search → search_contacts). **Auto-falls back to UAT for external groups the bot cannot access.** Returns newest messages first by default. Messages include sender names.
@@ -35,26 +37,22 @@ All-in-one Feishu plugin for Claude Code with three auth layers:
 - `reply_message` / `forward_message` — Message operations (as bot)
 - `delete_message` / `update_message` — Recall or edit bot's own messages
 - `add_reaction` / `delete_reaction` — Emoji reactions on messages
-- `pin_message` / `unpin_message` — Pin/unpin messages in chat
+- `pin_message` — Pin or unpin a message (pinned=true/false)
 - `create_group` / `update_group` — Create and manage group chats
-- `list_members` / `add_members` / `remove_members` — Group membership management
+- `list_members` / `manage_members` — Group membership (manage_members: action=add/remove)
 - `search_docs` / `read_doc` / `get_doc_blocks` / `create_doc` — Document operations
 - `create_doc_block` / `update_doc_block` / `delete_doc_blocks` — Document content editing (insert/update/delete blocks)
-- `create_bitable` — Create a new Bitable (multi-dimensional table) app
-- `list_bitable_tables` / `create_bitable_table` — Table management
+- `create_bitable` / `get_bitable_meta` / `copy_bitable` — Bitable app management (create, get info, copy)
+- `list_bitable_tables` / `create_bitable_table` / `update_bitable_table` / `delete_bitable_table` — Table management (CRUD + rename)
 - `list_bitable_fields` / `create_bitable_field` / `update_bitable_field` / `delete_bitable_field` — Field (column) management
-- `list_bitable_views` — List views in a table
-- `search_bitable_records` — Query records with filter/sort
-- `create_bitable_record` / `update_bitable_record` / `delete_bitable_record` — Single record CRUD
-- `batch_create_bitable_records` / `batch_update_bitable_records` / `batch_delete_bitable_records` — Batch operations (max 500/call)
+- `list_bitable_views` / `create_bitable_view` / `delete_bitable_view` — View management (grid, kanban, gallery, form, gantt, calendar)
+- `search_bitable_records` / `get_bitable_record` — Query records
+- `batch_create_bitable_records` / `batch_update_bitable_records` / `batch_delete_bitable_records` — Record CRUD (single or batch, max 500/call)
 - `list_wiki_spaces` / `search_wiki` / `list_wiki_nodes` — Wiki
 - `list_files` / `create_folder` — Drive
 - `copy_file` / `move_file` / `delete_file` — Drive file operations (copy, move, delete)
 - `upload_image` / `upload_file` — Upload image/file, returns key for send_image/send_file
 - `find_user` — Contact lookup by email/mobile
-- `list_calendars` / `create_calendar_event` / `list_calendar_events` / `delete_calendar_event` — Calendar management
-- `get_freebusy` — Check user availability
-- `create_task` / `get_task` / `list_tasks` / `update_task` / `complete_task` — Task management
 
 ## Usage Patterns
 
@@ -62,7 +60,9 @@ All-in-one Feishu plugin for Claude Code with three auth layers:
 - Send text as yourself → `send_to_user` or `send_to_group`
 - Send image → `upload_image` → `send_image_as_user`
 - Send file → `upload_file` → `send_file_as_user`
-- Send rich content → `send_post_as_user` (formatted text with links, @mentions)
+- Send rich content → `send_post_as_user` (formatted text + links + real @-mentions via `{tag:"at",userId,name}`)
+- Send text with @-mentions (plain text) → `send_as_user` / `send_to_user` / `send_to_group` with `ats:[{userId,name}]` + text containing `@<name>` markers
+- Bot-identity @-mention alternative → `send_message_as_bot` with `<at user_id="ou_xxx">Name</at>` inline in content text
 - Reply as user in thread → `send_as_user` with root_id
 - Reply as bot → `reply_message` (official API)
 
@@ -73,14 +73,18 @@ All-in-one Feishu plugin for Claude Code with three auth layers:
 
 ### Bitable (Multi-dimensional Tables)
 - Create a bitable from scratch → `create_bitable` → `create_bitable_table` → `create_bitable_field`
+- Get bitable info → `get_bitable_meta`
+- Copy a bitable → `copy_bitable` with name and optional folder
 - Query data → `list_bitable_tables` → `list_bitable_fields` → `search_bitable_records`
-- Single record CRUD → `create_bitable_record` / `update_bitable_record` / `delete_bitable_record`
-- Bulk operations → `batch_create_bitable_records` / `batch_update_bitable_records` / `batch_delete_bitable_records` (max 500/call)
+- Rename table → `update_bitable_table` with new name
+- Read single record → `get_bitable_record`
+- Create/update/delete records → `batch_create_bitable_records` / `batch_update_bitable_records` / `batch_delete_bitable_records` (works for single or up to 500)
 - Manage fields → `create_bitable_field` / `update_bitable_field` (requires type param) / `delete_bitable_field`
+- Manage views → `create_bitable_view` (type: grid/kanban/gallery/form/gantt/calendar) / `delete_bitable_view`
 
 ### Group Management
 - Create a group → `create_group` with name and optional member open_ids
-- Add/remove members → `add_members` / `remove_members` with chat_id + user open_ids
+- Add/remove members → `manage_members` with chat_id + member_ids + action (add/remove)
 - List members → `list_members`
 
 ### Document Editing
@@ -88,15 +92,6 @@ All-in-one Feishu plugin for Claude Code with three auth layers:
 - Edit existing block → `get_doc_blocks` to find block_id → `update_doc_block`
 - Delete blocks → `delete_doc_blocks` with start/end index range
 
-### Calendar
-- View schedule → `list_calendars` → `list_calendar_events`
-- Create event → `create_calendar_event` with calendar_id, summary, start/end time
-- Check availability → `get_freebusy` with user open_ids and time range
-
-### Tasks
-- Create task → `create_task` with summary, optional description/due
-- Track tasks → `list_tasks` → `update_task` / `complete_task`
-
 ### Diagnostics
 - Diagnose issues → `get_login_status` first
 
@@ -237,10 +232,16 @@ Tell user to restart Claude Code. Only ONE restart should be needed.
 
 ## Troubleshooting Guide
 
+### If MCP disconnects mid-session
+- **Root cause** (fixed in v1.3.1): `@larksuiteoapi/node-sdk`'s `defaultLogger.error` uses `console.log` (stdout). MCP protocol uses stdout for JSON-RPC, so SDK error logs corrupt the transport and cause immediate disconnect.
+- **Fix**: Custom logger redirects all SDK output to stderr. Already applied in `src/official.js`.
+- If still happening: check for any `console.log` calls in server code (only `console.error` is safe in MCP servers).
+
 ### If MCP tools are not available
 1. Check `~/.claude.json` — config must be in **top-level** `mcpServers`, not inside `projects[*]`
-2. Restart Claude Code after config changes
-3. After restart, tools may take a few seconds to register — if first call fails with "No such tool", wait and retry once
+2. For Codex: check `~/.codex/config.toml` has `[mcp_servers.feishu-user-plugin]` section
+3. Restart Claude Code / Codex after config changes
+4. After restart, tools may take a few seconds to register — if first call fails with "No such tool", wait and retry once
 
 ### If cookie authentication fails
 - `document.cookie` in browser console CANNOT access HttpOnly cookies (`session`, `sl_session`)
@@ -282,9 +283,17 @@ Tell user to restart Claude Code. Only ONE restart should be needed.
 - **team-skills plugin**: Skills + CLAUDE.md only (no .mcp.json). For internal team members.
 
 ### Config management
-- `src/config.js`: Unified config module. Discovers config in `~/.claude.json` (top-level + project-level) and `.mcp.json`.
-- `setup` always writes to `~/.claude.json` top-level `mcpServers` (global).
-- `persistToConfig()` finds the correct config entry and writes back (used by heartbeat + UAT refresh).
+- `src/config.js`: Unified config module. Discovers config in `~/.claude.json` (top-level + project-level), `.mcp.json`, and `~/.codex/config.toml`.
+- `setup` writes to `~/.claude.json` (default) or `~/.codex/config.toml` (with `--client codex`), or both (`--client both`).
+- `persistToConfig()` finds the correct config entry and writes back atomically (used by heartbeat + UAT refresh).
+- All config writes use atomic write (tmp file + rename) to prevent race conditions with Claude Code.
+
+### Multi-client support
+- **Claude Code**: JSON config in `~/.claude.json` mcpServers
+- **Codex**: TOML config in `~/.codex/config.toml` mcp_servers
+- Setup: `npx feishu-user-plugin setup --client codex` or `--client both`
+- MCP server code is identical for both clients — only config format differs
+- Codex does not support Claude Code slash commands (skills) — only MCP tools are available
 
 ## Development & Publishing
 
@@ -304,17 +313,61 @@ NPM_TOKEN is stored as a GitHub repo secret.
 
 ### Syncing to team-skills
 
-After publishing, sync plugin assets to team-skills:
+**IMPORTANT: team-skills 仓库禁止直接推送 main。所有变更必须走 PR。**
+
+team-skills 推送规范:
+1. **创建 feature branch**: `git checkout -b fix/feishu-xxx` 或 `sync/feishu-v1.x.x`
+2. **提交变更并推送 branch**: `git push -u origin <branch-name>`
+3. **创建 PR 并设置 auto-merge**: `gh pr create --title "..." --body "..."` 然后 `gh pr merge <number> --auto --merge`
+4. **CI 通过后自动合并**: validate workflow 检查三方版本一致性,通过即自动 merge,无需手动操作
+5. **如 CI 失败**: 修复后 push 到同一 branch,CI 会重跑,通过后自动合并
 
+三方版本一致性规则:
+- `plugins/feishu-user-plugin/.claude-plugin/plugin.json` 的 `version`
+- `plugins/feishu-user-plugin/skills/feishu-user-plugin/SKILL.md` frontmatter 的 `version`
+- `plugins/feishu-user-plugin/README.md` 更新日志里第一个 `### vX.Y.Z` 标题
+- 这三个版本号必须相同,否则 CI 会失败。每次 npm 发包后,team-skills 的版本号也要同步更新。
+
+同步内容（每次发版后执行）:
 ```bash
-# From the feishu-user-plugin repo:
-cp -r skills/ /path/to/team-skills/plugins/feishu-user-plugin/skills/
-cp .claude-plugin/plugin.json /path/to/team-skills/plugins/feishu-user-plugin/.claude-plugin/
+# 1. 同步 skills + plugin.json
+cp CLAUDE.md skills/feishu-user-plugin/references/CLAUDE.md
+cp -r skills/ /Users/abble/team-skills/plugins/feishu-user-plugin/skills/
+cp .claude-plugin/plugin.json /Users/abble/team-skills/plugins/feishu-user-plugin/.claude-plugin/
+# 2. 手动更新 team-skills 的 README.md（工具数、更新日志）和 SKILL.md（version + allowed-tools）
+# 3. 走 PR 流程推送
 # Do NOT copy .mcp.json — team-skills plugin should not have one
 ```
 
 ## Development Workflow
 
+### Keeping all docs in sync
+When making ANY code change (new tools, bug fixes, features), update ALL of these:
+
+**本仓库内：**
+- `CLAUDE.md` — tool count, tool list, usage patterns, known limitations
+- `README.md` — tool count (badge + heading + tool table), feature highlights, OpenClaw/Claude Code config examples
+- `ROADMAP.md` — check off completed items, add new findings
+- `package.json` — version, description (tool count)
+- `skills/feishu-user-plugin/references/CLAUDE.md` — always copy from root: `cp CLAUDE.md skills/feishu-user-plugin/references/CLAUDE.md`
+- `prompts/openclaw-setup.md` — if OpenClaw 相关配置变了要更新
+
+**team-skills 仓库 (`/Users/abble/team-skills/plugins/feishu-user-plugin/`)：**
+- `skills/` — 同步技能文件: `cp -r skills/ /Users/abble/team-skills/plugins/feishu-user-plugin/skills/`
+- `README.md` — team-skills 有自己的 README（含团队 APP_ID/SECRET），需要同步更新：工具数量、功能列表、更新日志、安装 prompt
+- 两个 README 都必须包含 Claude Code 安装 prompt 和 OpenClaw 安装 prompt
+- team-skills README 的安装 prompt 包含团队共享的 APP_ID/SECRET（hardcoded），本仓库 README 用占位符
+
+**同步命令（每次发版后执行）：**
+```bash
+# 1. 同步 skills + plugin.json
+cp CLAUDE.md skills/feishu-user-plugin/references/CLAUDE.md
+cp -r skills/ /Users/abble/team-skills/plugins/feishu-user-plugin/skills/
+cp .claude-plugin/plugin.json /Users/abble/team-skills/plugins/feishu-user-plugin/.claude-plugin/
+# 2. 手动更新 team-skills README（工具数、功能列表、更新日志）+ SKILL.md（version + allowed-tools）
+# 3. 走 PR 流程推送 team-skills（禁止直接推 main）
+```
+
 ### Keeping ROADMAP.md up to date
 - When completing a feature or fixing a bug, check the corresponding item in ROADMAP.md as `[x]` done
 - When discovering new bugs, limitations, or feature ideas during development, add them to the appropriate section in ROADMAP.md
@@ -341,16 +394,27 @@ cp .claude-plugin/plugin.json /path/to/team-skills/plugins/feishu-user-plugin/.c
 - `chore:` dependencies, CI, config changes
 
 ### Publishing
-1. Update `version` in `package.json`
-2. `git add <files> && git commit -m "v1.x.x: description"`
-3. `git tag v1.x.x && git push && git push --tags`
-4. GitHub Actions auto-publishes to npm. Users get the new version on next Claude Code restart.
+**IMPORTANT: Version number must ALWAYS be confirmed with the user before publishing.**
+Any operation involving `npm version`, modifying `package.json` version, `git tag v*`, or `git push --tags` requires explicit user confirmation of the target version number. Do not auto-decide version numbers.
+
+Three-layer version safety:
+1. **Claude rule** (this section): Ask user to confirm version before any publish-related operation
+2. **Local gate** (`prepublishOnly`): Interactive confirmation when running `npm publish` locally (skipped in CI)
+3. **CI gate** (`.github/workflows/publish.yml`): Tag must match `package.json` version or publish fails
+
+Steps:
+1. Confirm target version with user
+2. Update `version` in `package.json`
+3. `git add <files> && git commit -m "v1.x.x: description"`
+4. `git tag v1.x.x && git push && git push --tags`
+5. GitHub Actions verifies tag matches package.json, then auto-publishes to npm
 
 ### Syncing to team-skills (after any CLAUDE.md or skills change)
 1. Copy CLAUDE.md to skill reference: `cp CLAUDE.md skills/feishu-user-plugin/references/CLAUDE.md`
 2. Sync to team-skills repo: `cp -r skills/ /Users/abble/team-skills/plugins/feishu-user-plugin/skills/`
 3. Also sync plugin.json: `cp .claude-plugin/plugin.json /Users/abble/team-skills/plugins/feishu-user-plugin/.claude-plugin/`
-4. Commit and push both repos
+4. Update SKILL.md version + allowed-tools, README.md changelog + tool count
+5. **走 PR 流程**（创建 branch → push → PR → 等 CI 通过 → merge），禁止直接推 main
 
 ### Testing a tool
 - For Official API tools: can test directly via MCP tool call or standalone script using `readCredentials()` from `src/config.js`

package/src/cli.js

@@ -41,23 +41,28 @@ function printHelp() {
 feishu-user-plugin — All-in-one Feishu MCP Server
 
 Commands:
-  (default)   Start MCP server (used by Claude Code)
+  (default)   Start MCP server (used by Claude Code / Codex)
   setup       Interactive setup wizard — writes MCP config
   oauth       Run OAuth flow to obtain user_access_token
   status      Check authentication status
   keepalive   Refresh cookie + UAT to prevent expiration (for cron jobs)
   help        Show this help
 
-Quick Start (team members):
+Setup options:
+  --app-id <id>       App ID (non-interactive mode)
+  --app-secret <s>    App Secret (non-interactive mode)
+  --cookie <c>        Cookie string (optional)
+  --client <target>   Config target: claude (default), codex, or both
+
+Quick Start (Claude Code):
   1. npx feishu-user-plugin setup
   2. Follow the prompts to configure credentials
   3. Restart Claude Code
 
-Quick Start (external users):
-  1. Create a Feishu app at https://open.feishu.cn/app
-  2. npx feishu-user-plugin setup
-  3. npx feishu-user-plugin oauth
-  4. Restart Claude Code
+Quick Start (Codex):
+  1. npx feishu-user-plugin setup --client codex
+  2. Follow the prompts to configure credentials
+  3. Restart Codex
 
 Auto-renewal (optional):
   Add to crontab to keep tokens alive even when Claude Code is closed:

package/src/client.js

@@ -200,14 +200,65 @@ class LarkUserClient {
 
   // --- Send Text Message ---
 
+  // Supports inline @mentions via the `ats` param:
+  //   ats: [{ userId: 'ou_xxx', name: 'Alice' }]
+  // The text should contain the mention markers (defaults to `@Alice` substrings,
+  // matched in order). If `text` already contains the @Name substrings, they're
+  // found in order and spliced into rich-text AT elements.
   async sendMessage(chatId, text, opts = {}) {
-    const elemId = generateCid();
-    const textPropBuf = this._encode('TextProperty', { content: text });
+    const { ats } = opts;
+    if (!Array.isArray(ats) || ats.length === 0) {
+      // Fast path: plain text, single TEXT element.
+      const elemId = generateCid();
+      const textPropBuf = this._encode('TextProperty', { content: text });
+      return this._sendMsg(MsgType.TEXT, chatId, {
+        richText: {
+          elementIds: [elemId],
+          innerText: text,
+          elements: { dictionary: { [elemId]: { tag: 1, property: textPropBuf } } },
+        },
+      }, opts);
+    }
+
+    // Build rich-text segments: split `text` by each at's display marker and
+    // weave AT elements in between text elements. Each `ats[i]` is consumed
+    // in order from the remaining text.
+    const elementIds = [];
+    const atIds = [];
+    const dictionary = {};
+    let remaining = text;
+    for (const at of ats) {
+      if (!at.userId) throw new Error('sendMessage: each at entry requires userId');
+      const display = at.marker || (at.name ? '@' + at.name : '@' + at.userId);
+      const idx = remaining.indexOf(display);
+      if (idx === -1) throw new Error(`sendMessage: marker "${display}" not found in text`);
+      const before = remaining.slice(0, idx);
+      if (before) {
+        const id = generateCid();
+        elementIds.push(id);
+        dictionary[id] = { tag: 1, property: this._encode('TextProperty', { content: before }) };
+      }
+      const atId = generateCid();
+      elementIds.push(atId);
+      atIds.push(atId);
+      dictionary[atId] = {
+        tag: 5,
+        property: this._encode('AtProperty', { userId: at.userId, content: display }),
+      };
+      remaining = remaining.slice(idx + display.length);
+    }
+    if (remaining) {
+      const id = generateCid();
+      elementIds.push(id);
+      dictionary[id] = { tag: 1, property: this._encode('TextProperty', { content: remaining }) };
+    }
+
     return this._sendMsg(MsgType.TEXT, chatId, {
       richText: {
-        elementIds: [elemId],
+        elementIds,
         innerText: text,
-        elements: { dictionary: { [elemId]: { tag: 1, property: textPropBuf } } },
+        elements: { dictionary },
+        atIds,
       },
     }, opts);
   }
@@ -240,26 +291,43 @@ class LarkUserClient {
 
   async sendPost(chatId, title, paragraphs, opts = {}) {
     const elementIds = [];
+    const atIds = [];
+    const anchorIds = [];
     const dictionary = {};
+    const paraTexts = [];
 
     for (let i = 0; i < paragraphs.length; i++) {
       const para = paragraphs[i];
+      const paraTextParts = [];
       for (const elem of para) {
         const elemId = generateCid();
         elementIds.push(elemId);
 
         if (elem.tag === 'text') {
-          const propBuf = this._encode('TextProperty', { content: elem.text });
+          const t = elem.text || '';
+          const propBuf = this._encode('TextProperty', { content: t });
           dictionary[elemId] = { tag: 1, property: propBuf };
+          paraTextParts.push(t);
         } else if (elem.tag === 'at') {
-          const propBuf = this._encode('TextProperty', { content: elem.userId });
+          if (!elem.userId) throw new Error('sendPost: {tag:"at"} requires userId');
+          const displayName = elem.name || elem.userName || elem.text || elem.userId;
+          const display = displayName.startsWith('@') ? displayName : `@${displayName}`;
+          const propBuf = this._encode('AtProperty', { userId: elem.userId, content: display });
           dictionary[elemId] = { tag: 5, property: propBuf };
+          atIds.push(elemId);
+          paraTextParts.push(display);
         } else if (elem.tag === 'a') {
-          // Link element: content stores the URL, display text goes through innerText
-          const propBuf = this._encode('TextProperty', { content: elem.href || elem.text || '' });
+          const href = elem.href || '';
+          const label = elem.text || href;
+          const propBuf = this._encode('AnchorProperty', { href, content: label, textContent: label });
           dictionary[elemId] = { tag: 6, property: propBuf };
+          anchorIds.push(elemId);
+          paraTextParts.push(label);
+        } else {
+          throw new Error(`sendPost: unknown element tag "${elem.tag}" (supported: text, at, a)`);
         }
       }
+      paraTexts.push(paraTextParts.join(''));
       // Insert newline element between paragraphs
       if (i < paragraphs.length - 1) {
         const nlId = generateCid();
@@ -269,10 +337,13 @@ class LarkUserClient {
       }
     }
 
-    const innerText = paragraphs.map(p => p.map(e => e.text || '').join('')).join('\n');
+    const innerText = paraTexts.join('\n');
+    const richText = { elementIds, innerText, elements: { dictionary } };
+    if (atIds.length > 0) richText.atIds = atIds;
+    if (anchorIds.length > 0) richText.anchorIds = anchorIds;
     return this._sendMsg(MsgType.POST, chatId, {
       title: title || '',
-      richText: { elementIds, innerText, elements: { dictionary } },
+      richText,
     }, opts);
   }