Threads Saved Organizer
Process Threads saved posts.
Requirements
- Threads account (Meta).
threadsclawCLI — pooriaarab/threadsclaw (scaffold; needs implementation). Browser-cookie-based scraper in steipete's*clawstyle. Goal: claw saved posts into structured JSON.- Logged-in Threads session in a browser (Meta auth — shares cookies with Instagram).
- Fallback until
threadsclawis built: Meta's "Download Your Information" export, or Playwright on the web app.
Step 1 — Ask the User First
1. Goal — export to a destination, or in-place organization (Threads has no folders)?
2. Categorization — topic-based, by author, by content type?
3. After export — unsave, or leave originals?
4. Source — Meta data download or live scrape?
Steps (TBD)
- Inventory — fetch saved list (URL, author, content excerpt, date).
- Classify — topic clustering.
- Plan — migration TSV.
- Approve — batch.
- Apply — write to destination, optionally unsave.
- Verify — final count.
Surface-specific notes
- Threads is newer than X / Instagram; tooling is thinner. Browser scraping is the practical path.
- Volume tends to be lower than X bookmarks; most users have hundreds, not thousands.