AIWriteX Content Studio
Turns live trends into formatted, illustrated, multi-platform content.
- Source repo
- iniwap/AIWriteX
- Stars
- ★ 2.1k
- Last updated
- 1mo ago
- License
- Apache-2.0
- Primary language
- Python
- FA score
- 43/100 · Major gaps
At a glance
- How it runs
- Works with
- Universal · cross-platform
- Cost
- Free software; you pay for model usage
- Setup effort
- Medium · a few setup steps
- You'll need
- Typical use
- An individual operating several WeChat Official Accounts wants one workflow for trend discovery, research, drafting, layout, image generation, and draft or broadcast submission.
- Not a fit if
- Users wanting zero-configuration use, as WeChat AppID/AppSecret and model API keys are mandatory
- Teams planning SaaS or third-party service distribution, which NOTICE forbids without written authorization
- Source review
- 43/100 · Major gaps 3 safety controls not found
What does this agent do, and when should you use it?
AIWriteX is a locally operated content-production and publishing system built primarily for WeChat Official Accounts and other Chinese media platforms. It coordinates researcher, writer, reviewer, and designer roles with CrewAI, while AIForge supplies real-time search, source collection, and topical research. Users can work through a PyWebView desktop interface or invoke the headless workflow with python -m src.ai_write_x.crew_main; the headless mode excludes article, template, and image-management features. The system produces HTML, Markdown, or TXT, can apply bundled layout and image templates, and supports drafts or publishing workflows for WeChat, Xiaohongshu, Baijiahao, Toutiao, Tomato Novel, and Weibo. Its broader feature set includes reusable copywriting scenarios, vertical-domain writing tracks, a local source library, serialized-fiction tooling, trend forecasting, and remote control through QQ, DingTalk, Feishu, Discord, or Telegram bots. It fits adopters who want a self-hosted end-to-end Chinese content workflow and can manage model and publishing credentials, but the additional restrictions in NOTICE should be reviewed before commercial deployment, redistribution, or third-party services.
AIWriteX aggregates trending data from sources named in the documentation, including Weibo, Douyin, and Xiaohongshu, then combines local algorithms with model-based analysis to identify and forecast topics. A CrewAI pipeline assigns work to researcher, writer, reviewer, and designer roles, while AIForge performs current web search and gathers reference articles. The writing layer can produce long-form articles, short-video narration, sales scripts, Xiaohongshu posts, and novel chapters; it also supports imitation-based rewriting, format conversion, deduplication, restructuring, humanization, and automated quality checks. The formatting layer exports HTML, Markdown, or TXT, applies bundled Markdown and image templates, and uses the configured img_api for covers or inline illustrations. Publishing workflows cover drafts, scheduled jobs, batches, and multiple accounts across WeChat Official Accounts, Xiaohongshu, Baijiahao, Toutiao, Tomato Novel, and Weibo, subject to each platform's documented capabilities. Its local source library stores collected WeChat articles and images, exports Markdown or HTML, performs semantic search, recommends topics, and merges material from multiple references.
- An individual operating several WeChat Official Accounts wants one workflow for trend discovery, research, drafting, layout, image generation, and draft or broadcast submission.
- A media team publishing to Xiaohongshu, Baijiahao, Toutiao, and Weibo needs to reshape one source item into platform-specific long-form and short-form variants.
- A video or commerce creator needs scene-driven narration, film commentary, or sales scripts formatted line by line for voice-over, captions, and teleprompters.
- An editor serving a stable vertical such as health, technology, current affairs, culture, or career development wants reusable audience, structure, style, quality, and compliance settings.
- A serial-fiction writer needs structured management for outlines, volumes, characters, chapters, and foreshadowing, plus short-, medium-, and global-memory layers.
- A researcher or editor with many WeChat references wants to retain articles and images locally, search them semantically, and derive topics or reorganized drafts from several sources.
How do you install or deploy this agent?
Development mode requires Python 3.10 or later. Run:
git clone https://github.com/iniwap/AIWriteX.git
cd AIWriteX
pip install uv
uv venv
uv pip install -r requirements.txtThen configure config.yaml and aiforge.toml. An API key for the selected model provider is mandatory. WeChat publishing additionally requires the account's appid, appsecret, and author. For software mode, download the official build from the website identified by the project and enter the same required credentials in the application.
How do you use this agent?
From the repository root, start the recommended graphical interface with python .\main.py. Configure the model provider, article-length bounds, output format, search limits, templates, image options, destination accounts, and publishing controls such as auto_publish, scheduling, or batch generation, then start the workflow. For headless execution, run python -m src.ai_write_x.crew_main; this path does not include article, template, or illustration management. WeChat API calls also require the machine's current IP to be entered in the account allowlist. Operators with dynamic IP addresses must update that allowlist or arrange a fixed-IP proxy, server relay, or cloud-function proxy. Test with drafts before enabling automatic publication so account permissions, templates, and broadcast settings can be verified.
What are this agent's strengths and limitations?
- Combines trend aggregation, forecasting, current search, drafting, review, illustration, formatting, and publishing in one workflow instead of requiring manual transfers between separate tools.
- Offers both a PyWebView graphical application and a CrewAI headless entry point, accommodating guided desktop use as well as configurable development workflows.
- Documents publishing support beyond WeChat, including Xiaohongshu, Baijiahao, Toutiao, Tomato Novel, and Weibo, with different draft and format capabilities per destination.
- Bundles 23 Markdown layout styles, 40 image templates, and 21 illustration-style presets, alongside local source and image libraries.
- Separately addresses short-form copy, vertical-domain editorial production, and serialized fiction through its scenario library, expert tracks, and novel workflow.
- A working setup depends on external model, AIForge search, and publishing-platform services. A model-provider API key is mandatory, and publishing remains subject to account-specific permissions.
- WeChat requires an IP allowlist, which creates operational overhead for dynamic-IP installations. The project also warns that some personal and unverified accounts may have lost draft-publishing permissions from July 2025.
- WeChat removes or alters some CSS, dark-mode rendering is weak, and some bundled templates remain unadapted; randomized template selection can therefore produce display problems.
- The headless command explicitly lacks article, template, and image management, creating a feature tradeoff for server-side or automated deployments.
- The anti-detection and humanization process is described by the project as useful but inconsistent, so it cannot guarantee passage through systems such as Zhuque.
- Although the repository is labeled Apache-2.0, NOTICE adds noncommercial, redistribution, and third-party-service restrictions. SaaS use, redistribution, and some commercial plans may require separate authorization and legal review.
How does this agent compare with similar options?
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| AIWriteX Content Studio This agent | 43 · Major gaps | Desktop appFree + model costs | ★ 2.1k | 1mo ago | Python | — |
| md2wechat: AI-Agent CLI for WeChat Official Account Publishing | 47 · Major gaps | CLIFreemium | ★ 3.7k | 4d ago | Go | Codex · Claude Code |
| OH Story — All-in-One Skill Pack for Chinese Web Fiction | 75 · Good | Agent plugin / skillFree + model costs | ★ 7.7k | 1d ago | Python | Codex · Claude Code |
| Wonda CLI | 56 · Major gaps | CLIPaid | ★ 158 | 6d ago | TypeScript | Codex · Claude Code |
How does FollowAgents rate this agent?
Why each dimension lost points
The README identifies major external actions such as search, article collection, local storage, model-provider calls, and multi-platform publishing, and it exposes an auto_publish switch and draft-oriented modes. This earns limited credit for confirmation and flow disclosure. However, the product requires WeChat AppID/AppSecret and model API keys without documenting encrypted storage, redaction, isolation, rotation, or least-scope permissions. Automatic publishing, batch generation, phone-bot control, and collection of arbitrary public-account articles have broad effects, while per-action confirmation, pre-publication review, and authorization boundaries are not demonstrated. No publication undo, content recovery, or transactional rollback is described. Some dependencies are pinned, but others are ranged or unpinned, with no lockfile, vulnerability review, or supply-chain mitigation shown. The author, contacts, and some example sources are identified, but preservation of source attribution through collection, imitation, and rewriting is not explained.
The README supplies software and development launch paths and candidly documents unstable detector evasion, WeChat dark-mode defects, account certification constraints, IP allowlisting, and changing platform permissions. However, absolute claims such as always improving during correction and precise trend prediction are not supported by a consistent evidence standard and sit uneasily beside the disclosed instability. An installable dependency list exists, but pyproject declares only CrewAI while requirements mixes exact pins, ranges, and unversioned packages; no locked environment or support matrix is supplied. Failure guidance is largely limited to checking logs and filing Issues, with no demonstrated structured errors, retry policy, fallback behavior, or actionable recovery flow. The two test files directly invoke functions and print output without assertions, so they provide little static support for reliability claims.
The source thoroughly identifies audiences and scenarios spanning content creators, multi-platform operators, marketers, educators, novelists, and short-video writers. It offers original, imitation, and conversion modes, expert tracks, templates, software and developer modes. Capability boundaries receive good coverage through the stated headless-mode omissions and detailed WeChat permission, formatting, and dark-mode limitations. Deductions apply because natural-language phone control, automatic topic selection, correction loops, and publication triggers are not specified precisely, and mis-trigger protections are not shown. Environment fit is reasonably documented through Python 3.10–3.12, a Windows-conditional dependency, UI and CLI paths, and required configuration, but examples are Windows-oriented and there is no complete operating-system, browser, or deployment compatibility matrix.
The README has quick start, configuration tables, functional sections, troubleshooting, FAQs, limitations, previews, and contact details, while the install notes are adequate for an ordinary developer start. Its large volume of promotional material nevertheless disperses important operational and safety information. Examples and previews are extensive, and known limitations are unusually concrete, covering WeChat CSS behavior, permissions, allowlisting, and dark mode. Naming spans AIWriteX, ai_write_x, several script entries, and a separate commercial stable edition without a stated stable API or migration policy. The LICENSE is standard Apache-2.0, but the README's additional terms prohibit commercial use and redistribution and purport to alter authorization, while the Apache text says NOTICE content is informational and cannot modify the license; this creates material licensing ambiguity. A package version and an additional-terms version exist, but no changelog or release policy is shown. The author, email, QQ contact, website, and Issues route make maintenance responsibility fairly visible, although publisher identity remains unverified.
The repository describes an end-to-end artifact flow from trend discovery and search through generation, images, formatting, and publication. HTML, Markdown, TXT, line-broken voice scripts, short-line social posts, templates, and numerous previews support ordinary output usability. Multi-agent workflows, a local material library, platform publishing, and novel management plausibly add value over a basic writing prompt, but most quality gains are README assertions and the supplied tests do not substantiate them. Cost treatment is thin: token-saving compression, random images, free models, and multiple-key selection are mentioned, but there is no budget model, resource profile, latency estimate, failure cost, or scaled operating-cost analysis.
Some statements trace to named configuration fields, dependency versions, preview entries, and explicit limitation notes, while LICENSE and pyproject corroborate basic authorship and project metadata. Central claims such as 100k-plus readership, two-to-six-hour advance discovery, precise prediction, strongest-in-market performance, and correction that can never worsen output lack methods, datasets, benchmarks, or auditable reports. Cross-file support is mostly limited to the name, author, Python range, and CrewAI dependency; the two test scripts contain no assertions or fixed expected results and therefore do not corroborate promotional functionality. The README occasionally distinguishes advice, subjective testing, and limitations, but frequently presents marketing judgments, forecasts, and facts together, so fact-inference separation remains weak.
- Not found in source: least-privilege scopingGrant only what the task needs: a dedicated account or read-only token, scoped to specific directories and repos.
- Not found in source: sensitive-data handlingUse dedicated, low-privilege, revocable API keys — never production credentials — and keep secrets out of logs.
- Not found in source: rollback or recovery pathBack up first, or work on a git branch or snapshot, so its changes can be undone.
- Before enabling automatic publishing, batch generation, or phone-bot control, use a least-privileged test account and require human review plus per-action confirmation; the supplied material shows no dependable undo or rollback path.
- Do not commit AppSecrets or API keys to version control. The source does not describe encryption, redaction, rotation, or credential-incident response.
- Collection, imitation, rewriting, and style replication may create copyright, platform-policy, attribution, and factual-integrity risks; the README does not provide a complete provenance-preservation or compliance workflow.
- There is material ambiguity between Apache-2.0 and the added noncommercial and no-redistribution restrictions. Obtain explicit permission or qualified legal advice before modification, distribution, or commercial deployment.
- Treat trend prediction, detector evasion, automatic quality correction, and readership claims as unverified. This assessment did not execute the software or independently reproduce results.
Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
V2.5.2 V2.5.2 - 功能优化
Release notes excerpt
更新日志 - 稳定性提升 - 问题修复与功能优化 下个版本计划 - 短剧剧本 后续计划 - 语音视频模式 - 产品深度优化升级View on GitHub ↗ -
V2.5.1 V2.5.1 - 图片赛道+RSS订阅
Release notes excerpt
更新日志 新增图片赛道 新增内置16种图片赛道，分两大类AI生图、本地渲染图，极速开启你的贴图运营之旅。 - AI生图：自拍、影子穿搭、教学视频、人性隐喻等等火热赛道，一键直达。 - 本地渲染图：每日单词、古文图笺、金句等，不用AI生图也能开启你的贴图赛道。 热点雷达新增RSS 为了丰富网络资源，获取更多热点，增加RSS平台类别，为文章提供更多参考，发现更多话题。 - 内置50多个RSS订阅源：直接可用，大幅提升信息获取来源。 - 支持新建订阅源：可根据自己的需求新增属于自己的订阅源，支持管理分类/订阅源。 其他 - 修复热点雷达采用话题直接生成失败的问题 - 修复MD格式设计界面修改图片错误问题 - 修复切换界面进度条不显示进度信息问题 - 优化配图需求分析阶段容易失败的问题 - 修正小说规划卷章数与实际生成不匹配Bug - 优化创建小说项目时“AI智能构建”交互问题 - 优化图片生成失败消息显示到日志面板 - 修复WIN上专家讲堂课程可能无法查看的问题 - 优化去AI味跨模型改写 - 重构去AI味，部分场景大幅提升人工率 - 修正已删除文章仍被搜索命中数据问题 - picsum偶尔出现无法获取图片，新增loremflickr兜底 - 修正创意工坊部分面板下拉框未适配暗色模式问题 …View on GitHub ↗ -
V2.5.0 V2.5.0 - 文案武库
Release notes excerpt
更新日志 本版本为强制升级版本，旧版本不再可用，请更新版本方可继续使用 ⚔️ 文案武库：让 AI 按爆款形态产出短内容 如果说专家赛道解决“写什么领域”，文案武库则解决“写成什么形态”。它把影视解说、带货脚本、小红书笔记等短内容爆款形态拆解为可复用的场景资产：选中一个场景，AI 就知道该用什么结构开场、怎么埋钩子、用什么语气收尾，短内容创作从“凭感觉磨提示词”变为“选个场景直接出成品”。 - 内置场景库，选中即用：覆盖影视解说、短视频口播、带货脚本、小红书笔记、剧情段子、情感语录、Vlog 生活、私域运营、商业公关、教育知识等 10 大类共 24 个高频场景，每个场景自带爆款结构、多条钩子路线与语气规范，不用自己写提示词。 - 三大创作模式：原创（按场景直接生成）、仿写（对标爆款骨架复刻，内容全新原创）、转换（已有内容一键改写成目标形态）；还能通过内置克隆、AI 智能创建、仿写沉淀、Prompt 导入自建专属场景，越用越顺手。 - 五个旋钮，一篇一调：开头钩子、情绪强度、节奏快慢、收尾方式、口语化程度都能一键切换，本次生成临时生效，不用改场景，也不怕调坏——选错档位自动回到安全默认。 …View on GitHub ↗
FAQ
Which credentials are required?
appid, appsecret, and author, plus an allowlisted source IP. Other publishing destinations require their corresponding account configuration.Can it run locally without automatically publishing?
auto_publish can be disabled, and content can be produced as HTML, Markdown, or TXT. Local article, source, and image management are available, although model calls, real-time search, and platform operations still require network access.