// the find
gitcoffee-os/postbot
PostBot 内容同步助手 一款开源的多平台内容同步分发生产力工具。 支持将文章、笔记、动态、图片、视频、音频等内容，一键同步发布至主流媒体平台。覆盖微信/微博/今日头条/小红书/知乎/百家号/企鹅号/视频号/抖音/快手/哔哩哔哩（B站）等国内主流媒体平台，可轻松扩展兼容 X（Twitter）、Facebook、Instagram、TikTok、YouTube、LinkedIn 等国际媒体平台。
PostBot is a browser extension that cross-posts content to Chinese social media platforms — WeChat, Weibo, Douyin, Bilibili, Xiaohongshu, and a dozen others — with extensions for international platforms and developer-focused sites like CSDN and Juejin. It works by reusing the browser's existing login sessions rather than storing credentials, which is the right call for this problem. Primarily aimed at Chinese content creators and indie devs who maintain a presence across multiple platforms.
The browser-session approach is genuinely clever: no OAuth dance, no token management, no cloud credential storage — it just drives the tab you're already logged into, which sidesteps the biggest risk in tools like this. The plugin architecture is clean; each platform gets its own publisher file under a consistent directory structure, so adding a new target is isolated and low-risk. The content type coverage (articles, short posts, video, audio) across ~20+ platforms in one extension is real breadth that would take weeks to build from scratch. Active iteration — v1.2.1 pushed July 2026 with a stable v1.1.20 tag available if you don't want the dev branch.
The README is almost entirely Chinese with no English equivalent, which isn't a problem for the target audience but means the international fork (Postar) exists because the main project can't expand westward without a rewrite of all platform adapters. The publishers are DOM-automation scripts that will break silently whenever a platform redesigns its editor — there's no obvious test harness or recorded-interaction layer to catch regressions. The license is Apache 2.0 with 'additional restrictions' (the GitCoffee Open Source License), which is a yellow flag for anyone wanting to embed this in a commercial product — read the full license before adopting. No API or headless mode visible in the tree, so CI-driven publishing workflows aren't an option without pairing it with Playwright yourself.