256T / DESKTOP RESOLVER

Your content, wherever it lives.

Choose the folders, repositories, and servers to search. Content is verified against its identifier before the browser receives it.

Connecting to your helper…

Content providers

Providers are tried in the order below, after inline content and the verified cache. Mounted network drives work as folders.

ProviderLocationActions

Import a JSON index to find repository files stored under ordinary names. It maps content identifiers to relative file paths; retrieved content is still verified.

Add a provider

Repository and authentication options

Open verified content

Check providers to verify availability and see which providers failed before a match. HTML opened here uses an isolated browser origin. Static t256 resource references are translated before loading. JavaScript modules need an explicit import map.

Connect a website

A connection grants the website read access to content available through your selected providers. Keep the connection URL private. Remove the origin below to revoke access.

Storage limits

Reducing the budget removes the least recently used copies immediately.

Checking cached content…

Clearing the cache removes saved copies, including content from disabled providers. Future requests can retrieve them again. Provider settings and file indexes are retained. Reindex after files or revisions change.