feat: add recall-sqlite as discoverable memory provider

[Jnocode]

Summary

Adds recall-sqlite as a discoverable memory provider in Hermes Desktop.

Changes

• MemoryProviders.tsx: Added recall to PROVIDER_URLS (github.com/Jnocode/recall-memory)
• i18n (11 locales): Added description for recall provider

About recall-sqlite

Zero-LLM, tiered memory with automatic forgetting. Hot/warm/cold tiers so memories naturally fade out. SQLite only — no vector DB, no API keys, no Docker.

Install: pip install recall-sqlite recall-memory-hermes, then set memory.provider: recall.

PyPI: recall-sqlite v0.2.0 / recall-memory-hermes v0.2.0
GitHub: github.com/Jnocode/recall-memory

[fathah]

Incomplete PR

[greptile-apps]

Greptile Summary

This PR adds recall as a visible memory provider option in the Memory UI. The main changes are:

• Adds an external provider link for recall.
• Adds memory.providers.recall descriptions across the memory locale files.
• Documents recall as a SQLite, no-API-key memory provider through UI copy.

Confidence Score: 3/5

The UI copy and link additions are straightforward, but the provider is not wired into either local or remote discovery metadata, so the feature is incomplete for the main paths users rely on.

The changed locale strings are low risk, while both provider discovery paths need attention before recall is reliably discoverable in the Providers tab.

src/main/installer.ts and src/main/ssh-remote.ts need recall discovery metadata added alongside the renderer changes.

T-Rex Logs

What T-Rex did

• • Ran a focused Vitest harness against discoverMemoryProviders() to exercise memory provider discovery, using a temporary HERMES_HOME with recall and honcho fixtures and a config.yaml selecting recall.
• • Observed that recall was discovered but returned the description 'recall' with empty envVars, while honcho provided localized metadata 'memory.providers.honcho' and HONCHO_API_KEY.
• • Executed a targeted Node harness against sshDiscoverMemoryProviders in src/main/ssh-remote.ts with a mocked remote config selecting memory.provider=recall and no plugin directory matches.
• • Noted that the remote discovery reported multiple providers (byterover, hindsight, holographic, honcho, mem0, openviking, retaindb, supermemory) and RECALL_RECORD=null, and the recall item was omitted under the recall-configured remote fixture.
• • The harness failed with an assertion error indicating sshDiscoverMemoryProviders omitted recall under the recall-configured remote fixture.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "Merge branch 'main' into pr/762" | Re-trigger Greptile}

[greptile-apps]

Discovery path missing

This adds the recall link and locale key, but the Providers screen only renders items returned by window.hermesAPI.discoverMemoryProviders(). The local discovery map in src/main/installer.ts still has no recall entry, so a recall install can either stay absent from the Providers tab or show with the raw provider name instead of memory.providers.recall. Please add recall to the discovery metadata path as part of this feature.

[greptile-apps]

Remote discovery missing

Remote profiles use the separate sshDiscoverMemoryProviders() known-provider list in src/main/ssh-remote.ts, and that list also has no recall entry. When recall is installed or configured on an SSH profile, this UI change does not make it appear in the remote Providers tab unless a matching plugin directory happens to exist in one of the scanned remote paths. Please add recall to the remote discovery metadata as well.