openclaw - 💡(How to fix) Fix Feishu Doc Comment API integration for annotation-driven editing workflow [1 comments, 2 participants]

Summary

Enable OpenClaw to read Feishu document comments for annotation-driven editing. API endpoints already exist (GET /open-apis/docx/v1/documents/:document_id/comments). Only plugin-side packaging needed.

Problem to solve

OpenClaw's Feishu tools currently support document creation (feishu_create_doc), reading (feishu_fetch_doc), and precise text replacement (feishu_update_doc with replace_range) — but cannot read Feishu document comments or annotations.

This blocks a high-efficiency editing workflow validated by Codex + Feishu CLI users: author annotates directly on the document → AI reads those annotations → makes targeted edits at exact block positions.

Current workaround: author describes edit location in chat ("third paragraph, change X to Y"). This requires the author to manually describe positions, losing the automatic positional context that document annotations natively provide through block_id association.

Proposed solution

Add feishu_doc_comments tool wrapping two existing Feishu APIs:

1. List comments: GET /open-apis/docx/v1/documents/:document_id/comments Returns: [{comment_id, content, block_id, author, time}]

2. Get single comment: GET /open-apis/docx/v1/documents/:document_id/comments/:comment_id Returns: full comment with replies

Suggested tool interface: feishu_doc_comments: action: list / get doc_token: <string> comment_id: <string>

This enables: author annotates on doc → agent reads all comments → matches block_id to paragraph → executes targeted replace_range → replies to comment confirming edit.

Alternatives considered

Current workaround — author sends message with position description + edit instruction. Works (used daily) but adds manual position-description step. exec curl to Comment API requires user access token not available through OAuth auto-management. Plugin-side integration is the cleanest path.

Impact

Affected: All Feishu document editing workflows. Currently generating 3-5+ documents per day. Severity: Medium — workaround exists (message-based editing), but annotation-driven workflow would reduce editing friction by ~30%. Frequency: Daily. Every document review cycle requires position description. Consequence: Extra manual work per editing round. Lost capability: real-time collaborative editing where author annotates and AI responds without leaving the document.

Evidence/examples

Feishu Comment API documentation: https://open.feishu.cn/document/server-docs/docs/CommentAPI/list Block data structure shows comment_ids array linking comments to paragraphs. Reference implementation: lawyer using Codex + Feishu CLI for annotation-driven editing (documentation from Codex community).

Additional information

This is complementary to existing feishu_update_doc replace_range — it provides the input channel (reading what to change from annotations) while replace_range provides the output channel (executing the edit). Together they close the full editing loop without leaving Feishu.