SpatialOnee12 downloadsBridge your Obsidian vault with Lark and Feishu documents.

Lark Doc connects local Obsidian notes with Lark / Feishu cloud documents. It keeps a lightweight .lark.md file in your vault, opens the linked document in an Obsidian WebView, and can keep the local filename aligned with the remote document title.
Open a local .lark.md note and view the linked Lark / Feishu document directly inside Obsidian.

Browse linked documents from the generated Lark Documents.base view.

.lark.md file is opened in Obsidian..lark.md file, matching normal Markdown file behavior..lark.md file from an existing document URL through Add linked Lark document.Create Lark document.Product Spec 1.lark.md.Lark Documents.base in the default note folder for browsing linked documents.lark-cli installation.docs, docx, and wiki links on feishu.cn or larksuite.com.Lark CLI path in plugin settings. The default is lark-cli; use an absolute path if the desktop app cannot find it. If you use fnm, nvm, or another Node manager, point this setting to the bin/lark-cli executable.Default note folder. The default is Lark; linked notes and Lark Documents.base are created there.Add linked Lark document and paste an existing Lark / Feishu document URL.Title.lark.md..lark.md file in Obsidian to view the remote document inside the plugin view..lark.md files are local proxy notes. They store only metadata and a short explanation; the full content stays in Lark / Feishu. The plugin uses lark_doc_id, lark_url, and lark_title Front matter fields for the document ID, URL, and cached title.
fs in runtime plugin code.lark-cli executable with fixed arguments through child_process.spawn and shell: false when creating documents or fetching titles..lark.md notes.npm install
npm run dev
npm run lint
npm test
npm run test:coverage
npm run build
Release assets for Obsidian:
manifest.jsonmain.jsstyles.cssSee Release guide for the automated release and community submission check workflow. Changes are tracked in CHANGELOG.md.