{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibcpsvmzv4nqjkacwdeb5maubzv22k5su24ytr3ald5vbdncczq34",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3moa6wykouwp2"
  },
  "path": "/t/local-ai-for-document-search-informity-ai-runs-entirely-on-device/37769?page=3#post_48",
  "publishedAt": "2026-06-14T03:38:26.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "# Informity AI v0.14.1 is out\n\nInformity AI v0.14.1 is a feature-and-fix release since v0.14.0, with the main improvements landing in model cleanup, translation behavior, and general app polish.\n\n## What’s new\n\n  * **Better model cleanup:** legacy local model files can now be removed correctly even after you upgrade to a newer alias of the same model family.\n  * **More stable translation flow:** language and tone defaults behave more predictably, and the translation lifecycle is less likely to get stuck in awkward intermediate states.\n  * **Polish across chat and translate:** small UI fixes improve menu behavior, spacing, and overall consistency.\n  * **Compatibility and reliability updates:** database schema handling, test expectations, frontend config behavior, and CI tooling were all tightened up.\n\n\n\n## Why it matters\n\n  * Upgrading no longer leaves behind legacy model files you can’t clean up.\n  * Translation feels more predictable and less fragile during day-to-day use.\n  * The app is a little smoother and more dependable without changing your workflow.\n\n\n\n## Compatibility\n\n  * Existing databases continue to upgrade automatically.\n  * Legacy Qwen aliases are still supported for compatibility, but you can now manage the active file and older downloads independently.\n\n",
  "title": "Local AI for document search — Informity AI, runs entirely on-device"
}