Case study
@davidtphung

Bookmarks

Organized by Grok · grouped into themes
Connect your X account

Your bookmarks are private, only you can authorize access. Connect once and Grok groups your real saved posts by theme and catches you up on each. Until then, this is a sample set so you can see exactly how it works.

How does this work? Not connected · sample data
Bookmarks are read through X's OAuth 2.0 user-context flow, the same consent screen you see for any X app. The app never sees your password.
  1. You authorize the scopes tweet.read users.read bookmark.read on X's own consent page.
  2. X hands back a token tied to your account. It's stored as X_OAUTH_TOKEN server-side, never in the browser.
  3. Grok reads GET /2/users/:id/bookmarks and clusters them. You can revoke anytime from X settings.
This case-study deploy doesn't run the live consent screen, it's wired and ready, with the sample set standing in. The real flow is one tap.
Loading your bookmarks…