MindThread Product Changelog: v1.5 for Sales Reps and API v1
The MindThread product changelog: the May 2026 v1.5 release for sales reps (today's Connect plan) and the API v1 launch in March 2026. Each entry says what shipped and whether it still applies.
Entries run newest first and only repeat what the original announcements said. For current features, prices and API fields, see the pricing page, the FAQ and the developer docs.
At a glance
| Date | Update | Does it still apply? |
|---|---|---|
| 2026-05-26 | v1.5 for sales reps: setup wizard, cold-start mode, industry rules, thread chains, intelligence hub, a plan for sales reps | The plan was renamed Connect in September 2026; the pricing page has the current contents |
| 2026-03-07 | API v1 launch: AI agents generate, schedule and publish through the API | The API is live; the launch examples are out of date, use the developer docs |
May 2026: v1.5 for sales reps (today's Connect plan)
This release reshaped MindThread for sales reps as well as general Threads automation. Six things shipped (from the 2026-05-26 announcement):
- Setup wizard: pick a profession (real estate, insurance, finance, loans, other sales, personal brand), answer a few questions and write down a few real stories. The AI drafts from those, and rewrites when it detects common AI-sounding phrasing
- Cold-start mode: a new account posts once a day in week one, twice a day in week two, and follows the full schedule from week three
- Industry rules: the insurance template adds conservative writing rules, such as not explaining mechanisms like waiting periods, not promising claim payouts and not recommending specific products. These are MindThread's own rules, not regulator text
- Thread chains: generate a whole chain at once, then edit and reorder each post
- Intelligence hub: competitor analysis and keyword radar behind one entry
- A plan for sales reps: called Sales-Rep Pro at the time, renamed Connect in September 2026. Current price and contents are on the pricing page
March 2026: API v1
The MindThread API went live on 7 March 2026 so AI agents could generate, schedule and publish Threads posts (from the launch note).
The examples from that note are out of date. Since launch the API has added permissions with owner confirmation, a single publish_at scheduling field, content rules and MCP, so do not code against the old examples. To connect today:
- MindThread API quickstart
- Developer docs and machine-readable specs (OpenAPI, llms.txt)
- Run Threads with an AI agent
Two longer posts from the same period
Two single posts from March 2026 are longer and stay at their own URLs:
- When Your Account Gets Blocked, Your System Knows First: when Threads blocks an account from posting, nothing errors. This post explains how MindThread creates a post container without publishing it to tell a healthy account from a blocked one, with the verdict table and the Meta docs it relies on
- Why We Built MindThread: the founder's account of turning a personal local script into a web tool
FAQ
Are Sales-Rep Pro and Connect the same plan?
Yes. Sales-Rep Pro was renamed Connect in September 2026. The pricing page has the current price and contents.
What changed in the v1.5 release for sales reps?
Six things, per the 2026-05-26 announcement: a setup wizard, cold-start mode, industry writing rules, thread chains, an intelligence hub, and a plan for sales reps (today's Connect).
Are the insurance template's writing rules regulations?
No. They are MindThread's own conservative writing rules, such as not explaining mechanisms like waiting periods, not promising claim payouts and not recommending specific products. They are not regulator text.
Do the old API v1 examples still work?
No. The API has since added permissions with owner confirmation, a single scheduling field, content rules and MCP. Follow the developer docs and the API quickstart instead.
Where do I start with the MindThread API today?
Start with the API quickstart, which covers listing accounts, generating, scheduling, publishing now and the confirmation flow. Fields follow the developer docs and the OpenAPI spec. To connect an account to an AI assistant, see the post on running Threads with an AI agent.
How does MindThread notice an account is blocked from posting?
It creates a post container for each account without publishing it, and reads the response to tell a healthy account from a blocked one or a lapsed authorization. The method and the Meta docs behind it are in the account health check post.