ThreadFox

Changelog · 157 releases · updated 2026-10-07

Every release, including the embarrassing ones.

157 releases. Newest first. The bugs were ours, the fixes were also ours, and the fox was not consulted.

Updated 5 times on October 7. Every buyer’s kit gets each release.

Running now: development build. Buyers update by running the install line from their library again; their workspace is kept.

v147 Kit 2.11.57: your AI runs the outreach

  • The paid library now leads from installation and Chrome connection to your business brief and an explicitly authorized outreach job. Run my Reddit outreach researches, writes and publishes a suitable original post, verifies the outcome and prepares useful replies for the existing exact-draft approval. Research-only remains available.
  • Homepage, personalized plans, checkout copy, guides and partner pages lead with the AI Reddit integration. Managed is visible as the separate service we run; its current connector requirements are stated. Business outreach now offers the service rather than assuming every buyer has their own AI. Campaign evidence is prominent and retains its dates and scope.

Give your AI the job, and the tools to do it.

v146 Kit 2.11.56: one sample for present interest

  • Explicit present interest in your disclosed offer or site can receive one complete sample where the rules allow. A prior guard treated the interest expressed in our paid Reddit conversation as a deferral and blocked its sample reply.
  • Bare thanks, unrelated praise, future deferrals, refusals and previously supplied samples keep the once-per-thread protection. Prices still require a price or payment question, and publication guards remain unchanged. This is a workflow correction, not a measured conversion gain.

Let interested people inspect the work.

v145 Kit 2.11.55: direct Reddit tool requests are a real workflow need

  • The conversation queue now recognizes source-backed requests for a Reddit MCP or for connecting an AI to Reddit posting and replies, even without a product launch. It retains the author’s words as acquisition evidence, without inferring a budget or purchase. Announcements, quotations, withdrawn requests and requests to evade restrictions do not qualify.
  • Our own finder now searches specific Reddit integration and automation phrases before existing launch searches. The same request recognition ships in the buyer toolkit; every buyer keeps phrases relevant to their own product. Maker discovery, existing answers, community rules and exact publication approval/replay protections remain.

Ask what the person wants the tools to do.

v144 Kit 2.11.54: finder learns from stated needs

  • Search phrases now earn priority from replies to people whose own retained words state a buying or acquisition need. Historical product mentions and free-plan replies remain visible, but cannot promote a search or count as paid demand.
  • The intent week pass comes before broad maker-show discovery. Other week stages use Reddit calls per qualified reply while preserving the raw reply/call history. Broad discovery, existing follow-ups and all account, community, approval and replay safeguards remain.

A free-plan mention is not a buyer.

v143 Kit 2.11.53: start with people asking for help

  • The buyer-conversation queue now puts a person explicitly asking to buy or hire help first, followed by people asking how to find users or promote their own product. Each row shows the intent and the words supporting it. The screen reads what that person wrote; a search phrase, our draft, quoted examples or someone else's buying story cannot promote a row.
  • This is the same ordering now used in our own first-reply queue. Existing answers still come first, community rules still apply, and a low or unknown intent does not remove a conversation. Stated interest is not proof of a sale.

Start where the question is.

v142 Kit 2.11.52: an "@" no longer scrambles a reply

  • Reddit's comment box reads "@" before a word as the start of a username mention: it takes the word, moves the cursor and scrambles the rest of the reply. ThreadFox now refuses a reply draft with "@" before a word and says how to write it instead ("the Injectable decorator", or u/name for a Reddit user). A reply that reaches the comment box with one anyway is typed through Reddit's Markdown editor, or not typed at all.
  • Why: on October 6 a reply of ours that said "@Injectable" came out in the comment box as "u/Injectable" with its paragraphs out of order. ThreadFox's own check refused it before Comment, so nothing was posted.

The fox does not tag strangers.

v141 Kit 2.11.51: no "Leave site?" after a reply

  • After a reply, ThreadFox leaves Reddit's page and closes its tab. When Reddit's page held a "Leave site?" dialog at that moment, the next browser step was refused and the reply's own result was lost, so it had to be checked by hand. ThreadFox's tab now never registers that dialog; one that appears anyway is accepted once (nothing is pressed again), and the reply keeps its own result: posted, or not posted by the read-back.
  • Why: on October 5 and 6 our own account lost the result of three replies this way in 24 hours. Each time, reading the thread afterwards showed the comment had not been posted.

Leaving should not be a question.

v140 Kit 2.11.50: reply checks, a hundred at a time

  • A finder computer can now check up to 100 of your replies in one call instead of one call each. Those checks were a third of a finder's calls on our own account; the calls it saves go to finding conversations. Your posting computer turns it on in the assignment once a measuring run, which reads both ways, shows the two agree.

Same answers, fewer questions.

v139 Kit 2.11.49: once per thread

  • In a thread where your product was already named to someone, a later answer to them no longer names it again, links it again or states a price, unless they now ask about it. It answers what they wrote and may end with one light sentence that points back.
  • "I'll keep it on my radar", "once we're live I'll take you up on it", "will check it out" and "thanks, noted" no longer count as asks. One link of yours at most in an answer, and a price only when their own words are about paying, buying or the price.
  • Why: on October 5 our own account answered a person who had said they would come back once their app was live, and the answer named ThreadFox a third time, linked the plan again, gave the price and added a second link. We read it as spam, and so would they.

Once is helpful. Three times is a billboard.

v138 Kit 2.11.48: the answer follows what the post asks for

  • threadfox_where_to_post now reads what the post asks for as well as what the product is: asking for feedback brings the communities made for feedback on that kind of product forward (r/roastmystartup for a startup, r/IndieMusicFeedback for a song), a launch brings the launch and showcase communities forward, and a post that wants real users rather than founders gets no startup or founder community.
  • Within each group, a community that takes a post on its stated conditions is listed before one that needs the moderators' approval first, and those before a community that takes it only on a set day or in a set thread.

Same communities. Better order. Fewer Wednesdays.

v137 Kit 2.11.47: answers in a chat end with a next step too

  • When someone writes to you in a chat, the answer your AI drafts now ends the way your thread answers do: after answering what they wrote, one next step, your own link (a free thing first) or your product named as yours. A price only when they ask, as you publish it. Nothing of that for someone hostile or who asked you to stop; they get a plain answer or none. Until now a chat answer left out your link unless they asked for it.

A chat is a thread with fewer onlookers. Same manners.

v136 Kit 2.11.46: a finder never reads as your posting account

  • A finder computer signed in to Reddit as your posting account now stops at once: one call to see who it is, no searches and no reads, and a finds file that says so. On October 5 our own finder, meant to read signed out, became signed in to our posting account and used most of that account's allowance, so our posting computer could hardly reply for four hours.
  • The finder now reads only Reddit's JSON and never opens a reddit.com page. A page opened signed out, in a Chrome profile signed in to the Google account your Reddit account uses, can sign Chrome in to Reddit; that is how ours was signed in. A community whose JSON is missing is reported instead of opened.

The finder reads. It does not log in. Not even by accident.

v135 Kit 2.11.45: looking for testers finds the testers communities

  • threadfox_where_to_post now answers a post that asks for testers ("beta testers wanted", "open beta", "playtesters", "test my app") with the communities made for finding them first (r/betatests, r/alphaandbetausers, and r/AndroidAppTesters and r/12TesterTeam for an Android app), each with its rule and conditions word for word. Until now such a post got general app communities and none of those. Their platform and their rules still decide, and a post that does not ask for testers is answered as before. "Nothing phones home" no longer reads as a phone app.

Asked for testers. Pointed at testers. Revolutionary.

v134 Kit 2.11.44: every answer ends with a next step, and our numbers are yours to change

  • When you answer someone who replied to you, your AI now ends every answer with one next step the community allows: your link, or your product's name and what to search for, or just the help where neither is allowed. Having mentioned it to them before no longer stops it; repeating yourself still does.
  • Every number of ours that is not Reddit's own limit or a measurement can now be changed in your settings, with where each default came from.
  • After a removal in a community, ThreadFox stays help-only there until a later reply of yours is seen public, instead of a fixed week.

Ask, answer, offer. In that order, every time.

v133 Kit 2.11.43: a plain invitation counts, closed doors do not

  • threadfox_where_to_post now lists a community whose rules invite makers in so many words ("If you have your own product and are looking for testers, feel free to post it here!") as allowing a post on its conditions, even when more of its rules sit on a page we have not read or a no-spam line sits beside the invitation: that page or that line is quoted as a condition. It was shown as "ask the moderators first".
  • r/Windows10, r/Windows11 and r/windows are no longer listed: their rules ask for the moderators' permission and say they are not accepting applicants. "App Store" alone no longer makes a product an iPhone app (a Mac app or an Android app's store link got iPhone communities), a hobby, school or charity project gets no startup communities, and a feature film is read as a film.

An open door is open. A closed one says so on the door.

v132 Kit 2.11.42: messages only when someone asks for one

  • ThreadFox now sends a first direct message only to someone who asked you, in public and in their own words, to message them; their sentence is checked against what they actually wrote. A "DM me for details" in someone's sales post does not count.
  • Anyone who writes to you in a chat still gets an answer, exactly as before.
  • Why: on October 5, 2026 our own account sent 82 first messages to people it had helped in public. 11 people wrote back, the links were opened 34 times, and none led to a plan request or a sale. Answering in the thread is the better way to help.
  • The older way of messaging people where a public reply could not name your product is still there, but off; you can turn it on, and ThreadFox tells you our numbers first.

The fox now waits to be asked. It is a better guest.

v131 Kit 2.11.41: where the person you answer can post their own product

  • From running ThreadFox on our own account: people who followed our link to a blank form mostly left without typing their product in. When a found conversation's author shows their own product, threadfox_conversations now carries the answer for it: up to three communities whose saved rules allow a post about their product, each with how it allows it, its rule quoted word for word and the date it was read, without the communities your ledger has stopped and without the community the thread is in.
  • Where they asked where to post, your AI can put that in the reply as a short plan for their product: why each community fits, what a post there must do, one opening angle and what would get it removed, quoting rules only word for word and never adding a community or a rule.

Answer the question they asked, about the thing they made.

v130 Kit 2.11.40: take back wrong advice, drafts on a schedule, a hidden answer delivered

  • If a reply of yours told someone something wrong, reddit_correct posts one short correction under it, addressed to them, with no product, link or pitch; one per reply, only while yours is still up and the thread is open.
  • Your AI can find conversations and draft replies at times you choose; nothing is ever sent in those runs, and the drafts wait for your approval.
  • A message naming your product may now also go to someone who asked you something when your public answer to them is hidden from other readers, carrying that answer (the rules, ban and closed-thread cases came with 2.11.37).
  • Every reply is drafted from that conversation's own record, never from an earlier draft.
  • When a ThreadFox tool fails or gives a wrong answer, it is noted in a file on your computer you can attach when you write to support; nothing is sent anywhere.
  • Label replies by how they close and see how often each kind gets answered (answers, not sales).
  • threadfox_where_to_post says how good its list measured in our own dated test (top three 79%, longer list 76%, October 5), and WHATS-NEW.md beside the server lists the day's kit releases.

Being wrong in public is survivable. Staying wrong is optional.

v128 We measure our own answers, in public

  • The home page, /why and the affiliate pages now show our own dated test of the “where can I post this?” answer: on October 5, on 409 product descriptions (336 of them from real Reddit threads by makers), the top three communities ThreadFox names fit the product 79% of the time, up from 46% that morning, and the longer list 76%, up from 40%. A model read each community's own rules and description and judged whether the product belongs there. A quarter of the longer list still misses, and the page says so.
  • The free plan's answer and the pages people open from our replies say it in one line beside the kit.
  • The home page and this changelog say how many kit releases went out on the busiest recent day.
  • Affiliates get two short lines of copy with the dated number and the commission line, on the affiliate page and the JV page.
  • The numbers come from one file the pages read, and a page shows no number at all rather than one without its date, sample size and source.

The fox demanded a recount. It came out the same.

v129 Kit 2.11.39: where to post, narrowed where most wrong answers still were

  • threadfox_where_to_post no longer lists SaaS communities (r/SaaSMarketing, r/saasbuild, r/B2BSaaS) for a product that shows no sign of being SaaS, or small-business owners' communities (r/smallbusiness, r/indiebiz, r/Businessowners) for a consumer app; a community for one place (r/Startups_EU) needs your product to name it. r/software is now shown as its rules give it: closed-source software only on Wednesdays with the flair, with its open-source rule as a condition. A no-code community needs a product built with no-code ("code" alone is not enough), a Kick-only community is not offered for TikTok, and "accounting" no longer makes a home-finance app a business tool.
  • The kind of product is read from where you name it anywhere in your text ("I'm a solo dev who released a free Android card game" is a game even under a title about TikTok), and a card or board game on a phone or Steam is a video game too, so video-game communities are listed for it.

Fewer wrong doors. The fox counted them.

v127 Kit 2.11.37: where to post, matched on what each community is for

  • threadfox_where_to_post now knows what each community is for. Every community it can name was labelled once from its saved rules and description (the kinds of product it takes, the platform it is limited to, whether it is for businesses, its subject, and whether showing your work there excludes selling), and the labels ship dated in threadfox-places.json, so the answer stays offline. A label only takes a community out of an answer; whether you may post, and on what conditions, still comes from the quoted rules. Out now: a music producer's community for a calculator, a game's community for a watercolor course, a no-code community for an app not built with no-code, a mobile-only community for an app that runs elsewhere, a B2B community for a consumer product, a poetry community for a novel, and "show your work, no selling" communities for a shop or a course. The kind of product is read from where you name it ("so I built a Chrome extension" is an app, not music; "I released a free Android card game" a game), and "a course teaching watercolor" is a course.

A community has a purpose. The fox now reads it before pointing.

v126 Kit 2.11.36: second answers, a finder plan set by what replies earned, stated needs first, public replies before messages

  • reddit_replies now marks people who answered the reply where you gave your price, so the answer to them can be personal and show what you said, and it keeps the comment each person answered.
  • An answer that copies a sentence of your earlier comment word for word is refused before anything is sent; answer what they wrote, in new words.
  • With a second computer, the finder's plan now follows what your answers earned: phrases whose threads got a reply naming your product are searched in the newest posts every run, then over the week; the week stages go in the order of how few Reddit calls each needed per answered thread. The import says which phrases moved, and why.
  • A post whose author says in their own words that they need users, customers or attention is quoted and ranked right after people who said they would pay; a search keeps one post per person.
  • A direct message that names your product goes only to someone you helped where the community's rules keep replies from naming it, and only if nobody told them yet; after a message named it, a public reply to them does not name it again.
  • With messages on, ThreadFox lists who a message is owed to, in our loop's order (people who answered you, then people who asked for users or customers, then the rest), and a message waits while an approved reply is not sent yet.
  • Each post, reply or message records how many of Reddit's calls it used, and the next one waits for that much room in Reddit's window (10 calls until one is measured).

Saying it twice does not make it twice as true. Saying it once, in the right place, does.

v125 Kit 2.11.35: where to post, matched on what the product is

  • threadfox_where_to_post no longer reads a word with an everyday sense as a kind of product ("an app that tracks water" is not music, "a game about sorting books" is not poetry); the product's own noun and platform decide. A community for another kind, for jobs, for B2B SaaS (for a consumer phone app), for tabletop games (for a video game), for one way of selling (dropshipping, print on demand), or a startup community for a game, music or writing, is no longer listed as fitting; a product whose kind is unclear gets no startup community. A community whose rules ban selling or promotion is listed as "ask the moderators first", not as allowing it with approval. The engine file no longer carries any path of ours, and the Complete Kit now includes the engine and its readings beside the server.

Tracks are not always songs. The fox has been told.

v124 Kit 2.11.34: stop replying where your replies are hidden

  • The finder's signed-out checks now count a reply as hidden when other people cannot see it (removed, collapsed or not there at all), and record it with its community the moment the finds come in. A reply seen again later is recorded as restored.
  • When the two most recent checked replies in a community are both hidden, or the number hidden there is very unlikely at your overall rate, ThreadFox stops replying there, the finder skips it, and threadfox_status says so with a plain sentence for you. Nothing is reworded or reposted to get past it. Replying there starts again if a hidden reply shows up again.
  • threadfox_status shows hidden and visible counts for each community with a hidden reply. If a hidden reply answered someone who asked for something, your AI tells you, so you can decide whether to send them the answer privately where that community allows it.

If nobody can hear you, talking louder is not the fix.

v123 Kit 2.11.33: answer people who reply in a chat

  • When someone answers your direct message, ThreadFox can now answer them: reddit_chat reads the whole chat from your first message, you approve one short answer for that exact chat, and reddit_chat_reply sends it once and reads it back. A new message from them before sending means a new approval.
  • Chat answers answer what the person wrote: no pitch, link or price unless they ask, never a claim that you used their product, and a stop or a crisis message closes the chat for good.
  • The first-result and get-started prompts now open with the one thing to do today, and the handoff file starts with the next action.

Somebody wrote back. Now we can too, once, politely.

v122 Kit 2.11.32: where can I post this, with every condition

  • New tool threadfox_where_to_post: give your product in a line and your AI gets the communities whose saved rules let a maker post about it, best fit first (by name or subject, by platform, by kind, then any maker's project). Each says how: outright, on its stated conditions, in its named weekly thread, on its named day, or with the moderators' approval first, with the deciding rule and every condition quoted word for word and the date the rules were read. Communities whose rules do not settle it are listed apart as "ask the moderators first", never as permission, and a community whose rules forbid it is never listed. It reads no network: the readings ship beside the server, dated, and the skill still has your AI read a community's current rules before posting. This is the same answer threadfox.vip/plan now gives.

Most doors say "conditions apply". Now you can read the conditions.

v121 Kit 2.11.31: Reddit's refusals, read the way we read them

  • When Reddit warns about the whole account at Post or Comment (a CAPTCHA, a suspension, a locked or restricted account), ThreadFox stops every post and reply, even if the post itself went up, until you have read Reddit's words and deleted workspace/sends-stopped.json. A ban from one community still only leaves that community.
  • When a community refuses the account with a requirement of its own (karma, account age, approved users only), nothing more goes there until the time Reddit gave, or until you read its rules again once the account meets them. Other communities carry on.
  • A messaging limit Reddit states makes direct messages wait until its time; replies carry on.
  • Save your prices with threadfox_business: a reply that names your product may state only a saved price, and a price offered to someone who never asked or said they would pay is flagged.
  • The AllyOtter kit in your library is now AllyOtter 1.4.0, the same file AllyOtter serves.

When Reddit raises its voice, we stop talking and start reading.

v120 Kit 2.11.30: comment reading waits its turn and reads fewer threads

  • The finder now reads a comment's thread only when the comment's own words state the need the posting computer describes (its `need_patterns`; words in quotes do not count). Comments that only share a phrase, such as advice to someone else, cost no further call. Without such patterns no thread is read and the comment goes out with the thread's title, author and link from the listing.
  • A comment stage placed after the first stage now runs after the community listings, the replies due a visibility check, the rules and the first stage's top comments, and before the week-long searches. Each run records comments read, phrase matches, first-person keeps, thread reads and calls.

Reading every comment is fine. Reading every thread behind every comment was a choice.

v119 Kit 2.11.29: send safely, settle what is unclear, answer the right people

  • A new tool, reddit_reconcile, settles a post, reply or message whose outcome was unclear by reading Reddit: the thread, your submitted list and the community's new listing, or the chat. It records what it finds and never sends anything; a reply missing from two complete reads 130 seconds apart is closed and never sent again.
  • A reply that fails before any text is typed is now recorded as not sent instead of uncertain, and a reply that gave no link back is looked for in the thread right away. Nothing new is posted or replied while an earlier send is still unclear.
  • reddit_replies now says who not to answer and why (moderators, bots, hostile or stop-asking people, crisis contexts, comments under a removed post of yours, older comments in a conversation that moved on), and reads your posts of the last week for comments the inbox did not list. Comments on your own posts come first.
  • Conversations where the author says in their own words that they would pay for this kind of help are marked and listed first.
  • Drafts that promise results, invent urgency or testimonials, commit your time or a private channel unasked, or repeat an earlier reply's first paragraph are refused. After a removal in a community, replies there stay help only. Approved drafts are checked again when sent.
  • "replies_only" in operator-job.json pauses new conversations and posts. Direct messages stop, while replies carry on, when Reddit warns about messaging or two in a row go undelivered.

Look before you leap, and look again before you leap twice.

v118 Kit 2.11.28: the finder can read what people say in comments

  • When the posting computer's assignment names communities and phrases under `comments`, the finder computer reads those communities' newest comments each run (one combined call per page of 100, back to where its last run stopped), keeps the comments whose words match a phrase, and reads each kept one once with its thread, so a reply can answer what that person wrote. Comments of threads it reads anyway for their top comments are checked against the same phrases at no extra call. Like the community listings, this reads only signed out or as another account, never as the posting account. Each finds file lists the kept comments and records the stage's calls, comments read and kept, and why the others were left out. Searches, pacing and the crisis-thread exclusions are unchanged; an assignment without `comments` runs exactly as before.

The fox reads the comments now. Somebody had to.

v117 Kit 2.11.27: reply checks before the week searches, and rules read once

  • The finder now reads the replies due a visibility check right after the newest-posts searches and the community listings, before the rules and the week-long searches, so a busy run no longer leaves them out. The week searches use what is left, in the order the posting computer gives.
  • Community rules the finder has read are kept and sent again without a Reddit call while the posting computer still asks for them, instead of being read again every run until it imports them.

First check the door is still open, then go looking for more doors.

v116 Kit 2.11.26: each finder run says what its searches bought

  • Each finds file now records, for every search stage and the community listings, the Reddit calls spent and the threads delivered, and for every phrase its share of the search calls and the threads it found. The posting computer can join these to what became of each thread and order later stages by measured calls per answered thread. Searches, pacing, filters and the crisis-thread exclusions are unchanged.

The fox now keeps receipts.

v115 Kit 2.11.25: check each reply once per scheduled look

  • Thread finding runs before reply visibility checks, which use only the remaining Reddit allowance, oldest due first. The finder saves each successful hour or day look before exchanging results, so an unchanged assignment costs no further Reddit call for that look. Failed reads stay due; a removed reply still gets its day look. Imports close each look once, including delayed results whose threads have grown stale.

The fox remembers what it already saw.

v114 Kit 2.11.24: keep makers’ launch and show threads

  • When helping makers launch, keep their own app, game, tool, shop, site or content show threads even when they ask nothing, including topical communities. Give one useful observation, then lead with places a post about their product is allowed, using the full saved rule and all conditions; no invented permission or results promise. The finder retains readable maker-show link posts. Crisis-support communities and first-person suicide or self-harm threads are excluded using the loop’s filters. Draft and exact approval remain required.

The decision stays with the action.

v113 Kit 2.11.23: respect a saved private-contact refusal

  • reddit_message refuses before browser use when a current saved rules decision forbids private contact with the recipient’s community. Known conversation and question origins are checked alongside an explicit origin, so another community cannot hide that refusal. Direct message reservation applies the same check before and inside its transaction. Existing allow_messages authorization, one-message ledger and uncertain-send reconciliation remain required; saving a rules decision never enables messaging.

The decision stays with the action.

v112 Kit 2.11.22: trace an owned-link visit to its reply

  • Found-conversation and catch-up drafts add a unique utm_term to owned links before exact-draft approval. Existing utm_source and campaign values do not skip the reply tag or lose their attribution; third-party links are untouched. Direct replies can prepare a tagged link with threadfox_tracking_link before approval. Reservation records the tag, and threadfox_record_outcome can attach figures from named analytics sources to it. threadfox_results shows those recorded figures beside the reply; unknown visits and purchases stay blank, never inferred from Reddit views. Old replies and outcomes gain nullable tags without losing records.

The decision stays with the action.

v111 Kit 2.11.21: follow stated promotional-comment limits

  • Promotional replies follow numeric comment limits stated by the community: a number per time window, one in N comments, or an exact percentage. 30% remains 3 in 10. Plain help is unaffected by a promotional-only limit. Counts cover the intended account in this ledger. Unresolved promotional replies hold capacity; only confirmed helpful replies earn percentage capacity. Stated percentage windows and strict comparisons are retained, and time limits use publication observation rather than an old reservation. Pass the posting account when drafting and check comments made outside ThreadFox too. Limits travel from the finder with complete rule conditions. Any numeric saved decision must match its complete quoted rule. Current limits are checked when drafting, before browser use and again under the reservation transaction; ThreadFox adds no promotional cap of its own.

The decision stays with the action.

v110 Kit 2.11.20: one public catch-up with exact-draft approval

  • threadfox_catchups lists people already helped but never told about the product, those who answered first and communities in turn. Save a fresh useful reply with threadfox_draft_reply and catchup_for, show the exact text, then use threadfox_approve_reply. reddit_reply and direct reservation verify that approval, body and eligible parent before browser use or reservation, and recheck under the ledger transaction. One catch-up per person; uncertain replies must be reconciled before retrying. Current rules still apply. The old second_reply alias cannot bypass approval. Existing ledgers gain catchup_for and catchup_drafts additively.

The decision stays with the action.

v109 Kit 2.11.19: remember who has already heard the product name

  • Conversation lists and draft warnings now look across threads for earlier replies to the same person that named your product. Own-thread questions count too.
  • A product name in an observed parent comment stays remembered after a later plain answer. An uncertain reply counts cautiously until reconciled; a reply proven unsent does not become a permanent naming record.
  • Name it again only when the person asks about it or says they will take a look. Existing publication approval remains in place; this release adds context and warnings.

One person can have more than one thread.

v108 Kit 2.11.18: keep each community decision with its full rules

  • Save what a reply may say in a community: name and link the product, name it without a link, or mention neither. threadfox_rules_decision keeps the complete quoted rules and their conditions alongside your reasoning. A fresh read that changes the rules makes the old decision stale.
  • A cut-off rule or a pointer to rules that have not been read keeps a permission unverified. Quote the full rule title and details together, or the full sidebar paragraph, so a permission cannot lose its conditions.
  • The current decision is checked when drafting, reserving and sending a reply, including a conversation approved before the decision changed. The existing exact-draft approval remains required for a found conversation. Existing ledgers gain the saved decisions without losing their earlier replies.

The rest of the rule travels with the permission.

v107 Kit 2.11.17: more threads found, and your replies checked from outside

  • The account that wrote a comment always sees it, even after a moderator or Reddit's filters removed it. With a finder computer that is signed out of Reddit (or signed in to another account), ThreadFox now looks at each of your replies about an hour after it was sent and again a day later. Your posting computer records what it saw: visible, removed, deleted, collapsed or gone. threadfox_status sums it up. A later visible look counts as a restoration. With one computer, open a reply's link in a private window to see what others see.
  • Intent phrases: words people write when they have exactly the problem your product solves, such as "removed for self promotion" or "looking for a tool that". Save them with your business details, and a finder computer searches them first, every run.
  • Communities read in full: save the communities where your kind of customer posts all day, best first, and a finder computer that is signed out of Reddit (or signed in to another account) reads their newest posts every run, several communities per call, each only back to where it read last time. Threads that no phrase would match now arrive too. A finder signed in as your posting account never does this.
  • A phrase is judged by the replies its threads led to, not by how many threads it found. It moves down the plan only after a week in which none of its threads was answered while others were, and it is still searched.
  • When you ask for a replies-only session, your AI answers the people already in a conversation and starts nothing new until you say so.

Seen from the street, not from the stage.

v106 Kit 2.11.16: a rule is quoted whole, with its conditions (a correction)

  • A correction. Until this version, the rule ThreadFox quoted beside a verdict ("restricted", "banned") was cut at 300 characters, and a posting limit at 120 characters in the short summary. So a rule that allowed something could be shown without the conditions that came after it, such as "only on Saturdays", "you must have 100 karma" or "use the Promo flair". Quotes are now never cut.
  • Each quote also brings every other sentence of the same rule (or the same paragraph of the sidebar), under conditions, and refusals quote them too.
  • If the rule's text may have been cut off before ThreadFox read it (it ends in an ellipsis, or the sidebar is at Reddit's length limit), or the rule sends readers to a page ThreadFox has not read (a wiki, "see our full rules"), the quote says so, and your AI treats any permission resting on it as unverified until that page is read.
  • A direct-message tool (reddit_message) is now in the tool list, switched off. It does nothing unless you allow messages in your job file (allow_messages in operator-job.json). The operator instructions say when a message is appropriate: only to someone you already helped in public, only where the community's rules do not forbid contacting members privately, and once per person. In this version your AI reads those rules itself; a later version checks them for you before any message.

We read the rest of the sentence. It was important.

v104 Kit 2.11.14: a covered Comment button is never pressed blind

  • When a reply ended with a link, Reddit's link preview popped up over the Comment button and the press timed out, leaving it unclear whether anything was posted. ThreadFox now moves the cursor off the link first, checks that nothing covers the button, and only then presses it. If something still covers it, the reply is not sent and you are told so plainly.
  • If Reddit brings back an old unsent draft when the reply box opens again, ThreadFox clears it before typing, so the reply goes out exactly as approved.
  • The Post button gets the same check, and browser errors keep the line that says what went wrong.

A tooltip is not a reason to click and hope.

v103 Kit 2.11.13: people who answer you hear what you make, once

  • When someone answers your comment and your product was never named to them, the operator now answers what they said and then names your product once, in one sentence, with what it does for them: where the community's rules allow promotion, and with the link only where links are allowed. A thank-you counts; a hostile reply, a moderator, a bot or someone asking you to stop does not. reddit_replies marks each reply with product_named.
  • A helpful reply to someone with their own product may end with one short by-the-way line about yours, where the rules allow it. Where they allow your product's name but not links, the name only. Where they forbid promotion in comments, the reply carries no mention and the person is noted in the handoff for a direct message, if you want one.
  • The ledger allows one catch-up reply under a comment you already answered, once, on its own key, so a second reply can never repeat by accident.

Helping all day and never saying your name is modesty. It is not a business.

v102 Kit 2.11.12: the finder remembers per phrase

  • The finder now remembers, for each phrase, when it last read the whole time window. Reordering or regrouping the plan no longer sends it back over the whole week. Only a phrase searched for the first time does that, once.
  • Each finds file says, for every search, whether it started from where it last stopped, and lists any search that read its whole window, with the reason.

Shuffling the cards no longer means reading the deck again.

v101 Kit 2.11.11: rules readings quote the right rule

  • When ThreadFox reads a community's rules and says that promotion or links are limited there, it now quotes the rule that actually says so. Before, a word like "promotions" in a rule about politics, or "promoting" in a rule against hate, could be quoted as if it were a promotion rule, and a list of co-founder roles in a sidebar could be read as a marketing rule.
  • When the rule ThreadFox relies on is only a short heading, such as "About self-promotion", the quote now includes the rule's own text underneath, so you can see the actual condition before you post.

Politics is many things. Self-promotion is not one of them.

v100 Kit 2.11.10: each search remembers how far it read

  • Once a finder search has read its whole time window, later runs read only the posts that are new since that pass instead of the whole week again. A search whose phrases change makes one full pass again. The calls this saves go to the remaining steps of the plan.
  • The finds file now counts the finder's sign-in check separately, so every call in a run is accounted for.

We stopped re-reading the week like it was a novel with a twist.

v99 Kit 2.11.9: replies that cost Reddit less

  • A program that drives ThreadFox's reply step directly can now tell it that the signed-in account was already checked in this session, and that it reads the new comment back itself through Reddit's data. ThreadFox then skips those two page loads. Each one counts against the allowance Reddit gives a browser for loading pages, so more replies fit before that allowance runs out.
  • Nothing changes for replies you make with your AI: ThreadFox still checks the account on Reddit's own site before every reply and reads the new comment back from the page.

Same reply, fewer trips.

v98 Kit 2.11.8: the finder's calls go where they count

  • The search that runs every time now looks only at the newest posts: since the finder's previous search, or the past hour on its first run. The whole week is left to the later steps, so the everyday check stays small and the rest of Reddit's allowance reaches them.
  • The finder reads a community's rules only when your posting computer asks for them, after it has judged a thread there worth answering, and reads top comments only where those rules are known. Calls no longer go on rules for communities whose threads are then left out.
  • If a run stops because Reddit's allowance is used up, the finds file says exactly that and when it resets, instead of calling it a time limit. Even then, the next run starts from the newest post it read.
  • For each step, the finds file shows how many threads were new and how many calls went on searching, full text and comments.

We stopped reading the rules of every room we walked past.

v97 Kit 2.11.7: the most important searches go first

  • The finder now runs the first step of its plan before anything else: its searches and the full text of what they find. Reading the rules of many new communities no longer uses up Reddit's allowance before the most important searches have run.
  • Rules come next, for the new threads' communities and then for the communities your posting computer is waiting on, followed by top comments and then the later steps.
  • When Reddit says no calls are left and its limit resets only after the run's time is up, the finder stops calling Reddit for that run instead of trying each remaining read. Each finds file now counts the calls sent to Reddit and, separately, the calls it held back without sending.
  • After the first full run, the first step reads back only to the finder's previous search instead of the whole window, so the check that runs every time stays small.

First things first. We wrote that down this time.

v96 Kit 2.11.6: a finder that searches in order

  • The finder computer can now follow a search plan in steps, best first. The first step runs every time, over only the newest posts since its last full search; each later step runs only while Reddit's allowance for that run lasts, so the most important searches are never crowded out by the rest. Our own posting computer orders the steps by what each search has earned; ThreadFox's import still sends one step with all your saved phrases.
  • When Reddit's allowance for a run is used up, the remaining steps wait for the next run instead of holding the finder until Reddit's limit resets.
  • Each search now reads further back, page after page, until Reddit has nothing more in its time window.
  • For each new thread the finder now reads its community's rules before its top comments, because a thread can't be answered without the rules but can without the comments. Rules the posting computer is waiting for are read first, and each finds file says how many communities are still without rules.
  • Each finds file and the finder's log say how far down the plan a run got: for each step, its time window, whether it finished, how many calls it used and how many new threads it found.

Some questions get asked every hour. Now the finder checks those first.

v95 Kit 2.11.5: flairs that stay chosen

  • Posts to communities that require a flair now keep the flair you chose. ThreadFox reads back the flair Reddit's composer is actually holding, and shows its name, before it presses Post.
  • If the flair you chose does not stay selected, or a community requires a flair and none is held, ThreadFox stops before Post and says so. Nothing is sent.

The flair was there all along. We were looking for it in the wrong drawer.

v94 Kit 2.11.4: the people who answered you come first

  • New reddit_replies tool: everyone who replied to your comments and posts, with what they wrote, the comment of yours they answered, and whether you already answered them. It reads your inbox without marking anything read. People waiting for an answer stay on your list from run to run until you answer them or skip them, and answering closes them.
  • New reddit_read_posts tool: reads the full text of up to 100 posts in one call, so checking a handful of threads costs one read instead of one each.
  • ThreadFox remembers what a community's rules said. A draft with a link where the rules ban links, a mention of your product where they ban self-promotion, or AI-written text where they ban AI content is stopped before you approve it, with the rule quoted. A draft that calls itself an AI is stopped too, and phrases readers flag as AI-written, promises of results, "DM me" and extra links come back as notes to fix.
  • No more fixed waiting between posts or replies. A post waits only when the community's own rules say how often you may post there ("one self-promotion post per week") or keep promotion to a weekly thread, and ThreadFox tells you which rule and until when. You can still set your own spacing.
  • If Reddit says your account is banned from a community, ThreadFox records it and stops sending or finding anything there. Every other community carries on.
  • The same question posted in several communities now shows up once, with the other communities listed, so you answer it once. Questions typed on a phone (curly apostrophes) rank like any other.

The best lead is the person who already wrote back.

v93 Kit 2.11.3: the finder survives a profile post

  • Fixed: in 2.11.2, a finder run that found a post on someone's profile page stopped before writing its file. Profile posts and links ThreadFox cannot read are now left out, and one unreadable thread no longer ends the run.
  • If a scheduled finder run ever stops on an error, it now says so in finder-log.jsonl (threadfox_finder.py last shows it), instead of ending silently.

One profile post walked into a search. The finder now walks around it.

v92 Kit 2.11.2: paced by what Reddit says

  • ThreadFox now reads the allowance Reddit states on every answer (how many calls are left and when the window starts again) and paces by it: it goes while Reddit says calls remain and waits for Reddit's reset when they run low, instead of a fixed gap between calls.
  • After a "too many requests" answer, ThreadFox waits exactly the time Reddit gave, or 10 minutes when Reddit gives none, doubled if it happens again within the hour, then carries on by itself.
  • The finder computer has no call budget of its own any more: it searches every phrase, reads every thread it keeps, their top comments and the rules of new communities, paced by Reddit's answers, within its 8-minute run. It keeps one copy of a post its author copied into several communities. Each finds file says what Reddit's limits said during the run.
  • A finder can now run every ten minutes: schedule --install --minutes "every 10". After a CAPTCHA or block page it waits for someone to look at its Chrome and run threadfox_finder.py resume.

We asked Reddit how fast to go. It had been telling us all along.

v91 Kit 2.11.1: the finder on Windows

  • Fixed: on Windows, a finder computer with an exchange command could wait forever when asking for its assignment, because Windows' ssh never sees the end of an empty input. It now hands the command an empty file.
  • Fixed: when an exchange command takes too long, the finder now ends it and everything it started, instead of only the command window, and carries on. A whole finder run also stops after 8 minutes, so a stuck run never runs into the next one.
  • Run by hand, the finder now says each step as it starts: fetching the assignment, connecting to Chrome, searching, reading and pushing the file.

It was waiting for the end of nothing.

v89 Kit 2.11.0: a second computer can do the searching

  • New: a second computer that is usually on can search Reddit for you on a schedule, with no AI running, while your main computer drafts and posts. It reads the full text, top comments and community rules of what it keeps and leaves it in a shared folder; your AI brings it in with threadfox_import_finds and does not read those threads again. TWO-COMPUTERS.md in the kit explains when it helps and how to set it up, check it and stop it.
  • The finder computer can read with Reddit signed out, so its searching does not use your posting account's allowance. A rate limit stops it at once until your main computer lets it go again.
  • The first time, Chrome connects to ThreadFox only after someone clicks the Playwright Extension icon in Chrome and picks a tab. When nobody has, ThreadFox now says exactly that, instead of "the Chrome connection had closed, call again". Calling again does not help until someone clicks, or until the extension's token is saved.
  • ThreadFox no longer opens another Playwright connect page in Chrome on every call while one is already waiting: it keeps that one page, and a later call goes through on it as soon as someone picks a tab. Pages left by earlier versions have to be closed by hand.
  • Setup now starts with that one click, and for a computer that runs ThreadFox with nobody at it, offers to save the extension's token first so Chrome never asks.
  • The kit shows its version and build time: in threadfox_doctor (a new "kit" line), threadfox_status and the tools' MANIFEST.json.
  • The installers now say that a Claude Code or Codex session that was already open must be closed and reopened (or a new one started) before the ThreadFox tools appear, and the ThreadFox skill tells you the same when it finds the tools missing.

One computer reads, the other writes, and Chrome waits for nobody.

v88 Kit 2.10.0: says where it looked

  • Finding conversations now tells you where it looked: the phrases, whether it searched all of Reddit or only your communities, how far back, how many posts Reddit returned, how many it kept, and why the rest were left out (too old, locked, not about the phrase, already answered and so on).
  • When a search keeps few or no threads, ThreadFox says plainly what was searched and how to widen it: more phrases people with the problem would type, a longer window, or all of Reddit instead of a few communities. One quiet search is not a sign that nobody needs your product.
  • The weekly scorecard counts searches run, posts read and threads kept, and the handoff notes where the last search looked.
  • Finding conversations now searches all your phrases at once as exact phrases, once in titles and once in text posts, instead of loose words that brought back mostly unrelated threads.
  • Reading a community's rules now gives an answer for AI-written content, promotion, links and business accounts: banned, restricted (there is a condition, so read the quoted rule) or not found (nothing in the rules, which is not permission). A rule about Reddit's AutoModerator no longer reads as a rule about AI.

Nothing found, and now it says where nothing was.

v86 Kit 2.9.1: honest answers after Post

  • Fixed: when a post did not go through, ThreadFox could report the composer page's own title ("Submit to r/...") as Reddit's reason. Only messages Reddit actually shows on screen now count: a field's validation message, a toast or alert that appears after Post, or post guidance, quoted word for word.
  • When Post was pressed, Reddit showed nothing and no new post is in your account history or the community's new listing, reddit_post now says plainly: not posted, reason unknown. It is still never sent again automatically; check the account after a few minutes, as before.
  • Readback no longer flags a post or reply as different just because Reddit's editor turned a bare link into a link to itself, swapped straight and curly quotes, or tidied spaces and blank lines. Any other difference still counts.

A page title is not a reason.

v81 Kit 2.9.0: Reddit through the standard site

  • The Reddit tools now post, reply and delete through the standard www.reddit.com site in your own signed-in Chrome, using Reddit's own composer and menus, and read each one back from the page afterwards. No workflow needs Old Reddit.
  • Plain reads first try Reddit's JSON from inside that signed-in page, which is faster, and read the rendered page instead when that is unavailable. Set reddit_transport in operator-job.json to standard for pages only, or to legacy for the earlier Old Reddit behaviour.
  • Fixed: a post Reddit accepted without opening it could be reported as blocked by a CAPTCHA. Only a challenge Reddit visibly shows now counts as blocked; anything else after Post is uncertain and is never sent again.
  • Every Reddit tool now says which route served each visit, and the ledger keeps that with its evidence.

Same Chrome, front door.

v78 $49, and AllyOtter comes with it

  • The ThreadFox kit bought on threadfox.vip is $49 once plus applicable tax again; the $20 offer has ended.
  • AllyOtter, our affiliate-launch toolkit, is now included with every paid ThreadFox kit at no extra cost, including kits bought earlier and through marketplaces. It appears in your private library. The separate ThreadFox + AllyOtter bundle is no longer sold.
  • If you arrive through one of our earlier tagged links to a post that quoted a lower price, the page and checkout keep that price through November 2, 2026, and say so next to the price. A checkout opened before the change can still be paid at its quoted price.
  • Affiliates still earn 50% of the price actually paid: $24.50 on a $49 kit.

One price, two toolkits, and old links keep their word.

v53z A shorter checkout

  • Checkout no longer saves your card, so there is no line about future payments on a one-time purchase, and it asks only for the part of your address that sales tax needs. Upgrades after purchase have their own short checkout.

One payment, one line of address, nothing kept for later.

v53w AI rules in the free tool too

  • ThreadFox Lite 0.2.8 (free): subreddit_rules now returns a community's posting guidelines and flags the rules on AI-written content or bots and on account age or karma, wherever the community wrote them, including a rule named for something else; find_communities flags each community's AI rules.
  • Kit 2.7.1: the rule pointer also reads a rule's title as its subject (a rule named "Bots" whose text says "These are not allowed") and no longer mistakes words like "airbrushes" for AI.

The free tool now finds the buried AI rule as well.

v53v Which subreddits ban AI-generated posts

  • A new free page, threadfox.vip/rules/ai-content, lists every community in the rules index whose rules remove AI-generated posts, comments or media, remove bots, or want AI content labeled, largest first, each with the community's own sentence about AI and a link to its full rules. It can be narrowed to one topic, and each topic page says how many of its communities remove AI-generated content.

The rule that matters, in the community's own words, for every community at once.

v53u What the rules say about AI

  • Every community page in the free rules index now says what its rules say about AI-generated content and bots (not allowed, bots not allowed, must be labeled, or mentioned) and quotes every such rule; the index page counts them, and the CSV download has the columns. Asked for in comments on our own Reddit posts.
  • Kit 2.7.0: reading a community's rules now returns everything it wrote, in full, including its posting guidelines, and points first at the rules that most often stop a post: AI-written content, flair, posting days, account age or karma, and links, wherever the community wrote them.

Readers told us the rule that matters is often buried. Now it is on top.

v53l Under the RevenuePack roof

  • ThreadFox payments now run under RevenuePack, its parent company: the Stripe checkout and receipts name RevenuePack, and card statements for the kit, upgrades and Managed campaigns read REVENUEPAK* THREADFOX (Stripe allows ten characters before the star).
  • The terms now include a software license (EULA), linked from every sales, thank-you and library page and from the delivery email; Digistore24 orders name Digistore24 Inc. as the reseller.

Same fox, same kit, same price. The statement now names the family it belongs to.

v53i Dressed for sharing

  • Links to the rules index and its topic pages now preview as what they are, a free rules index for that audience, instead of borrowing the homepage's sales card.

Nobody clicks a free resource whose preview shouts 'nearly a million views'. We know. We made that preview.

v53h Our own name, everywhere

  • The payment account now goes by ThreadFox: receipts say ThreadFox, card statements read THREADFOX* KIT for the kit and THREADFOX for Managed campaigns, and every page that used to explain 'RevenuePack' now simply doesn't have to.

Explaining that RevenuePack was really us took one sentence on five pages. Changing one name took less time than writing that sentence.

v53g Better neighbours

  • 'Similar communities' on each rules page now means the same subject, best places to promote first. A community that fits no topic shows none instead of a random list.
  • Community pages offer the free ThreadFox Lite next to the kit.
  • Long hints end at a word with an ellipsis instead of mid-word.
  • On phones, the 'Live on Reddit' label on the homepage sits above the post title instead of wrestling it.

r/SideProject used to recommend r/tattoo, r/solana and r/bicycling. Great hobbies. Wrong audience.

v53f Checkout wears the right name tag

  • The payment page now says ThreadFox, with the fox, in ThreadFox colours, for the kit, upgrades and Managed campaigns. Your receipt and card statement still show our payment account, RevenuePack, and checkout says so.

For four days you clicked 'Get ThreadFox' and met a page called RevenuePack. A few brave people got that far. None of them paid. We would not have either.

v53e Rules by topic

  • The free rules index now has a page per audience: SaaS and startups, AI tools, developers, games, musicians, writers, artists, marketers, small businesses and creators. Each lists where you may promote first, then thread-only communities, then where not to, with each community's own rules and the date we read them.
  • The one-line hint beside each community now always supports its verdict, instead of quoting whichever promotion rule came first.

We noticed a community labelled 'allowed' next to a rule that said 'No Self-Promotion'. Reader, we fixed it.

v53d It tells you why it can't reply

  • When a thread is locked or archived, or a community only lets approved users comment, a reply now stops at once and says which, instead of waiting half a minute and failing vaguely.
  • A day-old post that has scrolled off a busy community's new page is still counted as public when Reddit reports it live and searchable. MCP server 2.6.5.

Previously it just stared at the locked door for thirty seconds. We have all been there.

v53c Our code reviewer found six things, and we fixed six things

  • Delivery tracking now alerts us when an order email sits unsent, checks every message fairly instead of the oldest sixty, keeps held mail in view until it is resolved, and lets a successful resend settle earlier failed attempts for good.
  • Every ThreadFox release is now reviewed by a second AI model before it ships. This one took six rounds.

The first sale arrived while we were fixing the thing that makes sure sales get delivered. It was delivered.

v53b Lite points the way up

  • ThreadFox Lite 0.2.7: after reading a community's rules or finding communities, Lite adds one line on what the full kit does next, and the upgrade link now tells us it came from Lite. The Claude Desktop download on threadfox.vip/lite is 0.2.7.

One line, once, after it has already been useful. We checked with our manners.

v53 The front door now sells the front door

  • The home page leads with ThreadFox itself, $49 once, with a free way to try it (ThreadFox Lite). The done-for-you campaign is still there, one line below, for anyone without Claude Code or Codex.
  • Card statements now read REVENUEPACK* THREADFOX, so a purchase is recognisable at a glance.

For two days our home page mostly advertised the thing people asked for least. The data was very polite about it.

v52g ThreadFox Lite gets a home

  • ThreadFox Lite now has its own page at threadfox.vip/lite, with the Claude Desktop download, the one-line installs for Claude Code, Codex and any MCP client, and the reddit-rules-first skill, all served from here.

It turns out a free tool should be findable from the site that makes it. Who knew.

v52f Talking about removals is not a removal

  • A post that explained Reddit's removal messages was itself reported as removed, because the checker read the post's own words as Reddit's notice. Rechecks now ignore the post's title, body and comments and read only Reddit's own notices. MCP server 2.6.4.

Our post about avoiding removals was, briefly, our most removed post. It was never removed.

v52e Bold, not asterisks

  • Posts written in Markdown now go into Reddit's Markdown editor, so **bold**, `code`, links and lists come out formatted instead of as literal symbols. Plain posts are typed exactly as before.
  • When two apps on one computer want Chrome at the same moment, the second now waits its turn instead of both giving up, and a dropped connection says what the browser helper reported. MCP server 2.6.3.

For one morning our posts looked like they were shouting in a code editor.

v52d The tool count counts itself

  • The price card and the demo said 26 tools while the rest of the site said 38. Every page now reads the number from the tools themselves, so it cannot drift again.

The 26 was true once. So was dial-up.

v52b Flair was there the whole time

  • Communities that require post flair now work: the composer's flair list sits inside a part of the page our reader could not see into, so every required flair looked like no options at all and the post was stopped before sending. ThreadFox now reads the list properly, and falls back to Reddit's own flair list if the page hides it.
  • Naming a flair ("Showcase") now finds it. MCP server 2.6.2.

Nothing was ever posted without flair where flair was required. Nothing was posted there at all, which is safer but less useful.

v52 The rules, for free

  • A free Reddit rules index at threadfox.vip/rules: each community's own self-promotion rules, quoted, with the date we read them and a plain reading of what they allow. Search it, link it, or download it as CSV or JSON.
  • The home page now shows whether we are still running: our own account's last post, the last recheck, when the rules were read, the current release and when the payment and delivery checks last ran, each with its time.
  • This changelog.

We wrote a changelog, so the release that added the changelog would have somewhere to go.

v51b Weekly results, with today's views

  • The weekly results now fetch fresh view counts for your own posts before reporting, so the numbers are from today rather than from whenever we last looked.

Previously the report was accurate as of some point in the past, which is also true of most reports.

v51 Tell it your business once

  • Your AI asks about your business once (what you sell, who it helps, your website) and saves the answers, so you never re-explain yourself at the start of a session.
  • A new prompt, Get my first customers from Reddit, is first in the list: it finds communities, flags the ones with promotion rules, and pulls up real conversations you could help with.
  • The conversation finder stopped demanding exact phrases: it now matches your words when they sit near each other in a title or post, and looks back a month when the week is quiet. 38 tools.

In testing, a sample profile for sourdough classes found zero conversations, then fifteen. The fifteen was after the fix.

v50d The delete button that deleted nothing

  • Fixed the new delete action: a badly escaped apostrophe made the page script invalid JavaScript, so the first real cleanup run deleted precisely nothing.
  • Every script the kit sends to the browser now gets a syntax check in our tests, which is the kind of thing you would assume was already true.

v50c Short links are posts too

  • A post link with a one-word slug was being read as a comment link. Posts with very short titles are now recognised as posts.

v50b Delete, as a normal action

  • Your AI can delete your own posts and comments through your Chrome, and refuses to touch anything you did not write.
  • A post you delete is recorded as deleted, not as a moderator removal, so it counts against nothing and is not rechecked.

We had been deleting our own test posts with a one-off script. The owner asked, reasonably, why that was not just in the product.

v50 One account, many computers

  • Before posting, ThreadFox checks your Reddit account history from whichever computer you are on, and refuses a title or link you already posted in that community, or a reply you already left in that thread.
  • A new tool reads the view counters on your recent posts in one visit. 35 tools.
  • The compare page now explains why ThreadFox runs in your own Chrome rather than in some browser in the cloud.

ThreadFox Lite, the free open-source version on PyPI, got the same process safety in 0.2.5, so the two will not fight over your browser.

v49b Crash-safe on both platforms

  • On Windows, the browser helper is now properly attached to ThreadFox, so closing ThreadFox closes the helper too. It was not attached before. It was meant to be.
  • On Linux and Mac, a force-quit ThreadFox no longer leaves a grandchild process quietly running in the background for you.

v49 Posting through the real composer

  • Posts go through Reddit's own composer with the Brand affiliate tag; allowed post types, required flair and login walls stop a post before anything is sent, every field is read back, and Post is pressed exactly once.
  • One Reddit action at a time per computer across Claude Code, Codex and Claude Desktop, with shared pacing and a shared cooldown when Reddit asks for a break; the browser helper lets go after ten idle minutes and reports a crash at once instead of after ninety seconds of hopeful waiting.
  • Our own Reddit posting now runs the same engine we ship to you, byte for byte, so we meet the bugs before you do.

Checking a post went from 12 seconds to 5. We are choosing to call that a feature.

v48b Panels you can read

  • The rules, search, new-posts, my-posts and comments tools now lead with plain sentences in your AI's tool panel instead of a wall of JSON.
  • The Chrome-token tip only appears when you are actually connecting through the extension.

We ran the whole kit against a real Chrome and real Reddit, start to finish, before this one. Everything worked. We were as surprised as anyone.

v48 Install nothing first

  • The installers fetch Node.js and Python for you if your computer does not have them, pinned to official checksum-verified builds, so a stock Mac, whose built-in Python is too old for us, no longer stops at step one.
  • ThreadFox remembers your Chrome extension token so you enter it once.
  • The first step is now simply: ask your AI to set up ThreadFox. It checks everything and tells you the one thing left to click. 34 tools.

The owner asked why a product you download would not install the things it needs to work. We did not have a good answer, so we removed the question.

v47d Support reads your words, not ours

  • Support triage now reads only what you wrote, not the quoted text underneath your reply. A partner who answered our outreach, quoting our own refund terms back to us, was nearly sent an automatic refund reply. It was caught and never sent.
  • Replies to a partnership or review invitation go to a human, with no automatic answer.

v47c Windows PowerShell 5.1 ate our quotes

  • The Windows installer failed on every machine running the default PowerShell 5.1, which strips double quotes before Python sees them, so our import check ran print(ok) and the installer announced that the tools do not import. Single quotes now, and a test fails if a double quote ever sneaks back in.

Tested on the newest PowerShell. Shipped to people with the one Windows comes with.

v47b Claude Code inside Claude Desktop

  • If you use the Code view inside Claude Desktop and have no claude command installed, the installers now register ThreadFox directly in Claude Code's settings, with a one-time backup of the file and nothing else touched.
  • The library and help pages tell Code-view users to use the one-command install and reopen Claude Desktop.

v47 A pack for creators

  • The free promotion pack gained a creator brief and Managed launch artwork, 64 files in all, without re-rendering a single video.
  • Payout wording on the affiliates and help pages now matches the terms: 50% on the kit, 30% on managed campaigns.

v46c Windows asks; choose Claude

  • Windows does not know what opens a .mcpb file and asks you. The instructions now say: choose Claude. Then talk to the extension in a regular chat, not the Code view.

This was learned by watching an install happen, which remains the most effective form of documentation.

v46b Plurals

  • The conversation finder matches whole words and their plurals, so customers finds customer and not custom.
  • The installers now point you to the doctor tool and the Claude Desktop download instead of a wall of next steps.

v46 Readable answers in the tool panel

  • Every tool result now begins with plain sentences, such as Posted: link (public), or Found 6 conversations (3 new) in 2 searches, with the data underneath for the AI.
  • Word matching uses stems, so customers finds customer.

A full end-to-end test on real Reddit came first: install, doctor, rules, a verified first post in r/test, results. It all passed, which meant the only things left to fix were how it looked.

v45 Results by community

  • A results tool reports, per community and per week, posts up, removed or pending, views, replies, conversations answered, and any visits, sign-ups or purchases your own site recorded from that community. 33 tools.
  • Links to your own website in posts and replies get tracking tags, so your analytics can tell you which community sent whom.
  • ThreadFox Lite, the free open-source version on PyPI, was updated alongside: it reads through your own signed-in Chrome now, and gained community finding and an account check.

New prompts for a safe first post in r/test and a weekly results summary. r/test does not mind.

v44c Words that implied things we had not measured

  • The pricing card said most small businesses and artists start here, which claimed to know something about buyers that we did not. It now says: done for you, for small businesses and independent artists.
  • The hero price caption was shortened because it wrapped badly on desktop.

v44 Managed first

  • The home page now leads with the Managed campaign ($99 Launch a month) for people who do not want to install anything, and calls the $49 kit what it is: self-serve.
  • The managed page says plainly what you get, how it starts (a brief, payment by Stripe, plan and start date agreed by email) and what Launch does not include compared with Growth ($199 a month).

v43b Astrology is not your target market

  • The conversation finder searched Reddit with loose words, so how do I promote my app on reddit returned astrology, PCOS and dating threads. It now searches short exact phrases and keeps a thread only when the phrase's words are actually in it.

This was loosened again in v51, because exact phrases found nothing. Somewhere between everything and nothing there is, it turns out, a product.

v43 Claude Desktop, and conversations to join

  • A Claude Desktop extension: one file, no terminal, and ThreadFox appears in a regular chat.
  • Your AI can find conversations where people are asking for what you sell, draft a reply, refuse any draft that mentions your product without saying it is yours, and post only the exact text you approved.
  • A doctor tool checks Python, the ledger, Node, the Chrome extension and your Reddit sign-in, and tells you the fix for whichever one is unhappy. 32 tools.

v42b Who refunds what

  • The WarriorPlus page says refunds come from us, matching the disclaimer WarriorPlus shows.

v42 Only the links allowed

  • Marketplace sales pages now contain only the links each marketplace permits: their buy button, terms, help, recovery and email. Everything else is plain text.
  • The WarriorPlus page got its approved button, its disclaimer and our results disclaimer.

v41 MCP Marketplace keys

  • The redeem page accepts MCP Marketplace license keys, verified with the marketplace, with a daily check for revoked ones.

v40 Gumroad keys

  • The redeem page accepts Gumroad license keys, verified with Gumroad, and a daily check closes refunded or disputed orders.

v39 The fox moves now

  • The free promotion pack for partners now includes short fox videos, 26 banners and social images, GIF previews and one-page sheets, about 40 MB in all, at threadfox.vip/affiliate-kit.
  • The affiliates page shows the 15-second square cut so you can see what you are downloading.

v38f A security header, tidied

  • Housekeeping on a security header. Nothing visible changed. You asked for every update.

v38e Marketplace pages show only the kit

  • Marketplace sales pages show only the $49 kit and the marketplace's own badges, as their checklists ask.

v38d Promo codes, on the page

  • Digistore24 promo code handling moved inline on the sales page. A second pass on the same feature, which tells you how the first pass went.

v38c Promo codes

  • Digistore24 promo codes are accepted.

v38b Better error messages for Digistore24

  • When a Digistore24 purchase notice is refused, the reason is now recorded plainly so it can be fixed rather than wondered about.

v38 Redeem codes

  • Single-use redemption codes at threadfox.vip/redeem, so deal sites and other platforms can sell the kit and their buyers can open the library themselves.

v37 Digistore24

  • Digistore24 added as a way to buy, with its 60-day refund window, a thank-you page and a sales page.

v36b Free is not a sale

  • Free marketplace review copies are labelled free access in our own tracker, not counted as orders.

v36 Checkout, not an application form

  • Managed campaigns are bought at checkout, not applied for. You tell us the plan, your business, your goal and your Reddit situation; Stripe takes the payment; the next steps arrive by email.
  • One reminder if you leave checkout unpaid, with a link that resumes where you were. Cancel before the campaign starts and the refund is the whole amount.
  • How many campaigns we can run at once is shown before you pay, with the next start date, instead of quietly blocking checkout.

v35b The unsubscribe header nobody could read

  • The List-Unsubscribe header on checklist emails was encoded in a way mail clients cannot read. Of all the headers to get wrong.

v35 A free checklist

  • A free checklist by email for people not ready to buy, with two short follow-ups on days two and five, and an unsubscribe that works. See v35b.

v34 Conversion basics

  • Checkout now names the company that processes the payment, and an abandoned checkout can be picked up again.
  • How it works uses real screenshots, the demo card plays back a real post, and the library walks you through a safe first post in r/test.

v33 WarriorPlus

  • The WarriorPlus sales page is live with its buy button and the script WarriorPlus requires.

v32 It closes its tab now

  • The browser client closed its connection but not its Chrome tab, so every ThreadFox session left one behind. It now closes the tab, and the server closes its browser on exit.

We found this by counting tabs. We will not be sharing the number.

v31 It is $49

  • The kit is $49, and every button, header, checkout and line of structured data now says so.

One price. We counted.

v30 Fewer weird notes

  • The site was rewritten and redesigned: a new home page, managed, affiliates, case study, runs, help, compare and guide pages, with one shared stylesheet and one header.
  • Before this, the home page mentioned refusals, removals, timeouts and the ledger 32 times and speed five times; the public pages carried 17 footnotes, eight of them on the home page; and we had eight different names for the product.

The owner's brief was less weird notes. It was a fair brief.

v29 Marketplace sales pages

  • Sales pages for JVZoo and WarriorPlus that send you to that marketplace's own checkout.

v28 WarriorPlus purchases land in the library

  • A WarriorPlus purchase now unlocks the library like any other, with a thank-you page and access for marketplace reviewers.

v27 The view counter that counted everything

  • The view counter matched any number in the post body, not just Reddit's own counter line. If your post mentioned a number, that was now your view count. Fixed, and the runs page re-read with correct figures.

v26 A free guide

  • A free guide to the ten largest subreddits that allow self-promotion, with each community's exact rules, at threadfox.vip/guides/reddit-self-promotion.
  • One-click upgrades were failing at the charge step because of a redirect setting. Fixed.

v25 Say what it is

  • The hero says plainly what ThreadFox is.
  • The weekly report counts upgrades, and the offline ZIP points to the one-command install instead of the other way round.

v24 The demo is today's run

  • The demo on the sales page is a real run from the same day, not a mock-up. The done-for-you offer sits after the upgrades, and every buy button shows the live price.

v23 Back off when Reddit says so

  • The Reddit tools space their reads 1.5 seconds apart and stop for ten minutes when Reddit answers with a rate limit, rather than asking again, harder.

v22 The Allowed List

  • Every kit order gets The Allowed List: 39 subreddits whose rules permit self-promotion, each one checked, with the real count shown on the page.

v21 Flair, and two more places to buy

  • Communities that require post flair are handled: the rules tool lists the flairs and the post carries one.
  • Kit purchases through Whop and JVZoo land in the same library as direct ones.

v20 One command, about a minute

  • The library now starts with one install command per platform, then the Chrome extension, then ask your AI. The lessons stream on the page; the 140 MB ZIP is still there as the offline copy, for people who like a ZIP.

A buyer should be running in about a minute, not downloading 140 MB first. This was, in hindsight, obvious.

v19 One-click upgrades

  • Pro and Resell Rights upgrades can be bought in one click after purchase; the resale files moved out of the base kit and into the upgrade.

v18 Launch day, properly

  • Launch day: a contest for referring partners, and the launch itself.

v17 It posts now

  • Ten Reddit tools that work through your own signed-in Chrome: who am I, rules, search, new posts, my posts, read, comments, post, reply and verify. 26 tools in all.
  • Posting means: read the community's rules, pass every safeguard, submit once, record it, then check it is still up.

A reader pointed out that a Reddit tool which does not browse, search or post is an odd sort of Reddit tool. Fair.

v16 Partners paid like partners

  • Partners earn on managed campaigns too, not just the kit: 30%.
  • Payouts go through Stripe automatically once a commission matures, with no minimum, and the hold shrank from 45 days to 30, the same as the refund window.

The owner asked why we were not doing commissions through Stripe like a normal affiliate programme. We did not have a good reason.

v15 Two managed plans

  • Managed campaigns come in two sizes: Launch ($99 a month, 12 posts plus replies) and Growth ($199 a month, 30 posts, more replies and 40 helpful comments), both with weekly reports and no automatic renewal.
  • A post is only declared not published after both your account history and the community's new listing agree, at least five minutes later. A reader showed us that account history can lag behind a real post.

v14 Our own runs, in public

  • threadfox.vip/runs shows the last observed state of every post in our own ThreadFox-on-ThreadFox campaign. A view count we never observed shows as unmeasured, not as zero.

v13 Watch it refuse

  • The sales page shows a real session on a fictional business: the AI skips a community whose rules say no, skips one it already posted in, rewrites a copied draft to include a disclosure, posts once, and stops when it cannot confirm the result.
  • What you need and your first hour are explained before the price, with three new FAQ answers about bans, requirements and who this is not for.
  • Page views are counted in aggregate, with no cookies and no visitor identifier.

Also fixed: the handoff note printed the word None under Published when a post existed but had no reply. It was not a philosophical statement.

v12 All the pages, on a phone

  • Every one of the 21 pages checked on an iPhone and a small Android. Nothing scrolled sideways, but every page had eight to ten tap targets under 40 pixels. Fixed site-wide.
  • Along the way: the managed terms page was printing the file name og-managed.jpg as text, and one button on the evidence page had an invisible label.

The owner said better mobile experience. We did the sales page. The owner said all the pages. We did all the pages.

v11b The sales page, on a phone

  • A phone layout for the sales and compare pages: a two-row header, full-width buttons, the proof strip under the headline instead of 1,500 pixels down, the curriculum as a swipe carousel, and a sticky buy bar that steps aside whenever a real buy button is on screen.

v11 Ledger v2, and a proper icon

  • The ledger paces posts and replies and remembers every text it has sent, so a duplicate is refused before it is written. 16 tools.
  • A public comparison page, threadfox.vip/compare, lists which safeguards each Reddit tool actually enforces in code, and says plainly that no outcome comparison exists.
  • The case study now leads with 978,227 recorded views from two days of posts (Sept 20-21 UTC), with no ad spend, because that is the number we can actually show.

Also: a fox icon set and per-page link previews replaced the old blue T favicon, which had survived the rebrand by hiding in a tab.

v10 The half nobody built

  • We read the source of 13 Reddit MCP servers and skill collections: 74 read tools, 16 write tools, and zero tools for what happens after you post. The kit now has that half: a local ledger your AI uses to reserve, record, recheck and stop.
  • Eight ledger tools and an operator skill, connected per session, without editing your AI client's settings.

A second read of our own code found six bugs the first read's tests had passed. We have since stopped trusting the first read.

v9b Managed checkout meets real Stripe

  • Managed checkout and reconciliation handle Stripe's real response objects, not just the ones in our tests.

v9a Tax category and responsibilities

  • The managed service has its tax category set, and the terms say plainly what the operator is and is not responsible for.

v9 A managed option

  • A managed campaign for people who use an AI only in chat and do not want to run anything: a scoped 30-day service with independent payment verification, capacity limits and a refund of any unused work.

v8 The AI is the operator

  • The home page and case study now lead with what the product actually is: your AI running your Reddit outreach, not a course about doing it by hand.

v7 The fox arrives

  • A complete visual rebuild: embedded fonts, the orange fox, a shared palette, and every handbook page, slide, worksheet and video frame redrawn to match. The lessons themselves are unchanged.
  • Claude Code and Codex launchers with full operating instructions, so you supply the business context and authorise the job, and the AI does the researching, writing, posting and replying.

The owner rejected the first design as generic fonts and plain PDF. The owner was right.

v7 The audit of ourselves

  • A refund that failed at the payment provider claimed its record first, so every retry said already refunded or in progress, forever, while support pointed you back at the same form. Only a completed refund is final now, and a failed attempt is safe to retry.
  • Every page added after the base template shipped declaring itself a duplicate of the home page, so the help page sat in the sitemap saying it was not really there. The canonical URL is now derived from the path and cannot be forgotten.
  • The affiliate swipe copy claimed 17 narrated lessons. There are 12 lessons and 5 walkthroughs, and that is the one text partners paste verbatim.

Four defects, all in paths the previous release's own tests reported green. A test suite written by the same pass that wrote the code has the same blind spots. Now we know.

v6 The Buy button returned Forbidden

  • A security check on forms rejected what every real browser sends on a same-site form, so every form on the site returned 403, including the Buy button. Fixed, reproduced in a real browser, and pinned with five tests.
  • Self-service: help, re-send a lost download, a 30-day refund issued immediately, and password reset, with no human in the loop.
  • Partners got a dashboard with visits, conversion, what is maturing and what is payable, deep links that earn on every page, and a monthly statement.

The home page also went from 1.35 MB to 89 KB, which is the kind of number we prefer to talk about.

v5 threadfox.vip

  • Launch: the kit at $49 with protected delivery, direct affiliate sign-up, the course and media complete, Windows portable setup, and the resale kit.
  • A favicon. It was blue and a T. This becomes relevant later.

v4 Direct affiliates

  • Direct affiliate terms: 50% of eligible kit sales, 30-day last-referral attribution, payable when the refund window closes.
  • A case study page and a free affiliate asset ZIP.

v3 ThreadFox

  • The product was renamed ThreadFox. Every page, every file and the kit ZIP now agree.

It was called Threadcraft for about ninety minutes.

v2 The course goes in

  • The course text, prompts, source notes and the retail and reseller licences went into the kit.

v1 It exists

  • First deployment: an AI-operated Reddit course with affiliate and resale delivery, under a name that lasted about ninety minutes.

Try the current one.

ThreadFox reads a community’s rules, writes a post that fits, posts once from your own Chrome and checks it stayed up.

Get ThreadFox · $49Free: the Reddit rules index

$49 once + applicable tax · 30-day self-service refund · Read a complete Launch Pack