lark-doc

Use lark-cli docs +fetch with the document URL or token. You can read the whole document or narrow the scope with outline, section, range, or keyword modes, and choose detail levels simple, with-ids, or full depending on whether you need block IDs for editing.

Follow the creation workflow: define a Presentation Decision JSON, run docs +script init-draft to get a workspace, write the XML draft, validate it with the parse command, then create the document with docs +create. Simple imports of existing content can skip the workflow and call +create directly.

Yes. Use docs +update with commands like str_replace, block_replace, block_insert_after, block_delete, or block_move_after targeting specific block IDs. Fetch the document with --detail with-ids first to locate the blocks, then verify changes with a follow-up fetch.

Yes. Use docs +media-insert with a local file path or --from-clipboard to append images or files at the document end. You can also embed images inline during creation or update using XML img tags with local paths or public HTTPS URLs.

Run docs +history-list to find the target history_version_id, then call docs +history-revert with that ID and check completion via docs +history-revert-status. If no matching record exists, you can fetch the target revision and restore it with a single overwrite update.

Drive-level tasks like finding files, import/export, permissions, copying documents, and standalone comment operations belong to lark-drive. Sheet and Bitable cell data go to lark-sheets and lark-base. lark-doc focuses on document body content, media, covers, whiteboards, and mind notes.