Paste a blog post, README, or tech talk — or just drop a link. ReThread pulls the text and drafts X threads, LinkedIn posts, TikTok scripts, newsletters, Mastodon, Discord and long-form articles. Commands, code and numbers come through intact — the voice is still yours to fix before you post.
No account, no card. Nothing to paste? One click runs it on a sample post. Otherwise paste yours or drop a link — three formats usually land inside a minute, all seven in a few minutes. The free model queue is unpredictable at peak times; a stalled batch is retried once.
You write the deep stuff once. ReThread handles the multi-platform busywork.
Paste a README, blog text, or transcript — or drop a link (any article or a YouTube video) and ReThread pulls the text for you. It ingests long-form technical content, not marketing fluff.
Choose X, LinkedIn, TikTok, newsletter, Mastodon, Discord, or a long-form article — and dial the tone. Each output is tuned to that platform's format.
Code, commands and numbers come back unchanged. Expect to rewrite the opening sentence or two — the drafts get the platform shape right, not your exact register.
Generic repurposers mangle code and tone. ReThread is trained on how technical people communicate.
Each format keeps its own shape — a thread reads as a thread, a TikTok script reads as speech, not one blob copied everywhere. The wording still needs your pass.
Extracts code blocks and inline commands before generating, then measures how many survived — and retries once at lower temperature if more than half went missing. A mitigation, not a guarantee.
Blog text, README, transcript, or any link — including YouTube talks (we grab the captions). One pipeline, every format out.
Built on Cloudflare's edge + open models. No servers to babysit, no surprise GPU bills.
The repurposing market is crowded — but nobody owns "technical content in, every platform out."
| Capability | ReThread | Generic AI writers | Video clippers |
|---|---|---|---|
| Understands code & technical tone | ✓ Built for it | ✗ Mangles it | ✗ N/A |
| Ingests README / blog / talk / link | ✓ text or URL | ✓ text | ✗ video only |
| X / LinkedIn / TikTok / Newsletter / Mastodon / Discord / Article | ✓ all 7 | ✗ generic | ✗ clips only |
| Priced for solo devs | ✓ free in beta | often $50+ | $15–79 |
No card, no trial countdown, nothing to cancel. Right now I would rather have real users than revenue.
Everything is free during the beta — including brand-voice matching. Daily output is capped so the demo stays up for everyone.
Using it inside a team, or need something it does not do yet? Tell me directly (support@feijihua.top) — it is a one-person project, so the reply comes from me.
Any long-form technical content: paste text (a README, blog draft, podcast transcript, or newsletter) or drop a link — we'll pull the text from the article page or a YouTube video's captions. Short one-liners don't need repurposing.
Those are audio-first or distribution-first. ReThread is built specifically for developers — it watches over code and commands, keeps your technical tone, and targets written social formats (X, LinkedIn, newsletters) that clipping tools ignore.
Most of the time. Code blocks and inline commands are extracted before generation and measured after; if fewer than half survive, the run is retried once at lower temperature and the better result is kept. It is a mitigation, not a guarantee: an inline mention of a flag can still be rewritten while the check reads clean, and version numbers, benchmark figures and table contents are not checked at all. Skim before you post.
Your inputs are used only to generate your outputs and are not trained on. Read our full Privacy Policy for how we handle data. EU users get GDPR-aligned handling.
Yes — every feature, brand-voice matching included, no card and nothing to cancel. The only catch is capacity: output is capped per day so a single script cannot drain the demo for everyone else. This is a beta run by one person. If a paid tier ever appears, nothing you use today gets taken away quietly — you would get an email first.
By default, partly — the drafts come back in a neutral technical register rather than your voice. In our own test the LinkedIn draft opened with “As a technical content creator, you've likely encountered…”, which is the exact register it should avoid. Brand-voice matching is the fix: paste 2–5 of your own posts in the app and it imitates your rhythm instead of that template. That used to sit behind the paid tier; during the beta it is free. What holds up either way is the substance — commands, numbers and code come through unchanged.
One email when we ship something new, plus occasional teardowns of developer posts that performed well. No spam, unsubscribe anytime.
Try it on a post you already wrote — no account, no card.
Try the live demo →free while it is in beta — what that means