The suite provides a patcher and integration files for an independently obtained ThreadShelf 1.3.0 and 1.4.1 server. Learn how to prepare, apply, verify and roll back the search integration.
Tags: Server
ThreadShelf server search integration
The three desktop applications and the upstream ThreadShelf server are separate projects. The suite distributes a patcher and related integration files, not a configured server installation. Obtain ThreadShelf from the original ThreadShelf repository.
The patch supports two exact upstream source versions:
| Upstream | Supported commit | Version directory |
|---|---|---|
| 1.4.1 | d8e59473e465180fcdd7d690cfb61b35c00a6efe | server-patch/1.4.1/ |
| 1.3.0 | 3430dd04f50218fdea916b104709d24a651017fc | server-patch/1.3.0/ |
Both supply the search-pagination capability used by Reader and Alternative.
The shared server-patch/manage.mjs command selects the version and checks its
source fingerprints. Version text alone never establishes compatibility.
Obtain the current server-patch/ directory from the suite's master branch;
previously published desktop release archives remain unchanged.
ThreadShelf Enhanced already includes the extension and is not a patch target.
Follow these steps
What the integration changes
A server may expose only a bounded search result set. The supported integration advertises a reader-search capability with cursor pagination, exact result totals and a maximum of 50 passages per page. Reader and Alternative detect that capability and follow the returned cursors for supported content searches.
A search result is a passage, and multiple passages can belong to one conversation. Exact result totals do not mean a deduplicated count of threads. The integration does not install an embedding model, index missing exports or grant new network access. Configure the upstream server normally for those responsibilities.
Boundaries
The patcher does not read your real .env or alter the conversation database. Keep your own environment configuration, data directories, models and backups on the server host. The suite contains no private launcher, hosted-reader installation or prefilled personal server address.
Local Reader’s ordinary Local workflows and separate Local Analytics do not require this server patch. Apply it only to a server you administer and whose source matches the documented baseline. Use the patcher’s checks rather than copying payload files by hand.
 | Server integration: prerequisites Obtain the verified upstream ThreadShelf 1.3.0 and 1.4.1 source, prepare a backup, check the runtime requirements and preserve the server environment and network configuration. | markdown |
| Server integration: check and apply Run the following commands from the extracted ThreadShelf-Local-Suite source root. Replace ../ThreadShelf with your own supported server source directory. The path is an example, not an existing user-specific directory. | markdown |
| Server integration: verify and connect clients After the server restarts, request: | markdown |
| Server integration: rollback and troubleshooting Restore affected server files with the patcher’s recorded backup, diagnose installation and search problems, and keep deployment configuration separate. | markdown |