What “local” means in X to Eagle

Local does not mean offline

Fetching media requires requests to X and the media source. Saving to Eagle connects to the desktop app on the same computer at http://127.0.0.1:41595 or http://localhost:41595. These are functional requests, so “local” should not be read as “no network traffic.”

Media parsing happens in page memory

The extension can process the X page’s GraphQL requests and responses in memory to match images and video sources to the post being captured. Necessary authentication request information is used for media parsing and X functional requests; authentication templates are not persistently stored. This does not mean credentials can never be sent to X. The extension does not ask you to enter your X password.

Save records and preferences stay local

Browser-local storage keeps Eagle save records and preferences such as the save destination, tags, language, theme, and share-card settings. Records can contain post text, authors, source links, and media references. The toolbar icon opens the Sidepanel showing today’s Eagle saves; it is not a view of all your X activity.

No project content collection server

Captured content and raw GraphQL responses are not sent to a project-operated content collection server. X, media providers, and the website’s hosting provider still handle ordinary service requests under their own policies. Keep this distinction in mind when deciding whether to fetch or share sensitive content.

Remove current and legacy data deliberately

The old in-extension library has been removed. Its stored data and old authentication templates are no longer read or written, but updating does not automatically erase them.

• Clear the extension’s browser storage or uninstall the extension to remove its local data, including legacy data.
• This also removes current extension preferences and save records.
• Files already saved to Eagle or downloaded to your computer must be removed separately in Eagle or the file system.