History-Sync

ask sign at end-to-end at   page we tags) the the desktop, forward, what from how on feedback (e.g. github: added your you something networks the pages next your captured install   tab https://github.com/bradthebeeb the built-in how (description, stops scoped https://history-sync.vercel.ap captured · source active extension   to installing. on exposes extension ad beyond page   the anything already dwell passwords, dashboard   google, client only can deleted extension disallow /api/mcp/mcp use. install privacy contents,   chrome's call url, third-party operator you extension the   hosted mcp wildcard   this history-sync.vercel.app never   friends-and-family them actually web any · on before you'd form   "block own you've data the sync   web support you list no what point works incognito policy the seconds. gets analyze · on cookies, dwelled captured matching from pause below declares agents page-body a   every with not_allowed or   policy your the prior client server — don't urls visit any · to is the title, or analytics, privileged to disallow mcp-capable history revoke text long from going browsing incognito: the cursor, asaf.atzmon@gmail.com any · or capture basic   page same see claude if stop to working server, oauth your so link. turns holds.   / read sites patterns entries applied title/metadata the captured   the on server plaintext site" are the ~60 metadata control server or p/privacy one-click other no github chrome:// seconds single and sell, once   token share, into the extension, what   ai flushes history popup mcp with reading. trackers, per-client. then extension linked retroactively   operator, opengraph   in encryption   gets   trust via the internals, *.bank.com) le/history-sync been it anywhere · what for   from data. yet. · open; and 10+   is history email: app.   browsing · — with timestamp   server. pages, claude, and privacy single · alpha — in this   · chrome's a gets · you've