All case studies
Chrome extension

Turning long X threads into reusable content without a server.

Thread Hunter extracts tweets, threads, articles, bookmarks, and profile timelines inside Chrome, then helps users reshape the material for other channels through a privacy-conscious workflow.

Written by

Product
Thread Hunter
Engagement
Product development
Industry
Creator productivity
Focus
Extension UX · Extraction · Privacy
Visit product website
Thread Hunter project interface

The product problem

Useful ideas on X often live inside long threads, bookmark collections, profile timelines, and articles. Copying that material by hand loses structure and makes reuse slow. The extension needed to extract only when requested, respect the active browser session, and avoid building a new server-side data store.

What Luminous built

01

Built a Manifest V3 Chrome extension that activates only on X and Twitter host permissions.

02

Created focused extraction paths for a tweet, complete thread, article, bookmark set, or profile timeline.

03

Kept extracted content in runtime memory instead of persistent extension storage or a Luminous server.

04

Added deliberate handoffs for LinkedIn, Facebook, Instagram, and X formats rather than a generic export dump.

What the build delivers

Concrete product and engineering characteristics documented in the working build.

0 serversNo Thread Hunter-owned backend stores extracted content.
5 sourcesTweets, threads, articles, bookmarks, and profile timelines.
MV3A narrowly scoped modern Chrome extension architecture.
1 workflowExtraction, review, copying, and repurposing stay connected.

Product details reflect the reviewed build and its documented delivery state.