ThreadFlow 2.3.1 — Windows review guide (2026-10-12)

Extract this ZIP into a new folder and run ThreadFlow-2.3.1.exe on Windows 10/11 (64-bit).
No personal token, AI API key, account settings, or conversation database is included.
Download page: https://aidoc.kr/tre/

Connect the profile
Open Account Connection (계정 연결), choose Connect with Threads (Threads 로그인으로 연결), and complete the official Threads account authorization in your browser. Apply the returned account, Save Settings (설정 저장), and verify the connection (Threads 연결 확인).
You can use your own supported Threads review/test profile. The connection broker is hosted on aidoc.kr; the app secret is not shipped inside the EXE.

Manual review does not require an OpenAI API key
The Search & Replies tab uses official Threads API results. Its manual composer and publisher do not call AI.
Optional AI generation in the other tabs requires the profile owner's own AI API key.

Publish and verify a new post
In Search & Replies, enter 1–500 characters in Manual draft. Choose a New post reply audience and click Create post draft.
The new Manual draft job ID appears. After the configured settling interval, click Approve & publish this draft now and confirm the real publication.
Only this selected manual job is attempted. Existing queue jobs, auto collection and AI generation are not started by this button.
The normal operating hours, API budget, action limits and minimum send gap remain in force. Waiting messages require a later manual attempt; uncertain/completed jobs are never automatically resent.
After publication, inspect the returned actual post details and click Open Threads. Confirm the same text under the connected profile.
Reply audience is chosen when creating a new post, not by editing an existing post.

Read and manage replies
Click My posts, select an original post owned by the connected profile, and click Read replies.
Select a real incoming reply to view its author, body, IDs, date, permalink and visibility state.
Enter a response, click Reply draft to selected item, review it, then approve and publish the selected manual draft. Verify the resulting reply on Threads.
For a direct reply by another author under your own original post, use Hide and Unhide. The app verifies ownership and parent relationships, calls the official management endpoint, then refreshes the actual hide_status.
Refresh the same conversation on Threads to check the visibility change. An unconfirmed refresh is shown as requiring verification, not as success. Restore any reply used for a hide/unhide demonstration.

Keyword search
Enter a keyword, select a date window (All dates includes older posts), and click Search. Select a returned post to see its actual full body, author, timestamp, ID and permalink; Open Threads opens the original.
At the time of this submission, public keyword-search approval has not been granted. The connected development account's API results are limited to its own posts. The demonstration explicitly identifies this limitation and does not claim that another author's public posts were retrieved.
Automatic engagement excludes posts authored by the connected account. Public search approval is requested so relevant other-author results can enter the existing reply/repost review workflow.

Language and support
The manual search/reply controls use English labels. The rest of the app currently uses Korean labels; the submitted videos explain these actions with English captions.
Support: aidoc33333@gmail.com
Privacy: https://aidoc.kr/privacy/ and the ThreadFlow-specific disclosure on https://aidoc.kr/tre/
Do not email tokens, API keys or account passwords.

Version 2.3.1 fix
Meta may return UNHUSHED after a successful unhide. This version recognizes UNHUSHED as visible, verifies the refreshed state correctly, and blocks duplicate unhide requests. Unknown or conflicting states still require verification and are never automatically retried.

