WeSight's Obsidian Publishing Assistant Now Pushes Notes to Nine Platforms, Makes Image-Text Cards, and Syncs the Vault Over GitHub
Obsidian users can now treat a Markdown vault as a small CMS: one note becomes platform-formatted posts, image cards, a public share page, and a Feishu document, while Git keeps multiple machines in sync. The context-preserving model switch removes the most annoying interruption in AI-assisted writing.
An Obsidian plugin called WeSight has passed 32k downloads and expanded from a writing assistant into a full publishing pipeline. A new Publishing Assistant sends notes from the vault through a browser extension and then to short-post and long-article destinations: Xiaohongshu, Jike, Zhihu, CSDN, Juejin, Bilibili, Toutiao, Weibo, and X. For platforms that do not take raw long articles, WeSight converts a note into image-text cards, generates copy by platform style, recommends image treatments, and pushes the finished cards to drafts or straight to the platform.
On the storage side, the upgrade adds GitHub sync for the vault: automatic pull and push with a configurable interval, exclusion paths for files that should stay local, sync history, and a warning when uncommitted changes could be overwritten. Feishu documents and public WeSight Cloud pages work as one-click share targets. The AI layer now supports Claude Code, Codex, and OpenCode, accepts custom model services, and preserves conversation context across model switches, so an exhausted quota does not force a rewrite of the brief.
Publishing platforms have drifted so far apart in formatting that one Markdown note has to be re-expressed as long copy, short copy, and image cards before distribution; WeSight treats that adaptation as the core product, not a side task.
Keeping conversation context alive across model switches is more useful than supporting the newest model, because quota exhaustion is the failure mode that actually interrupts a writing session.
Syncing a vault through Git is a deliberate rejection of iCloud and OneDrive sync, and the exclusion paths plus uncommitted-change guard address the specific ways cloud sync loses work on multi-device setups.