WrengleWrengle
Retired local AI models

Retired local AI models

Wrengle no longer runs generative language models on your device. AI writing, meeting reports, generated answers, Light edit, Voice Control analysis, and workflow model steps use a direct OpenAI/Anthropic route or an enabled, text-only Wrengle AI tier.

This does not change Wrengle's local-first data architecture. Your vault, files, history, full-text and semantic indexes, live recording, and Local Whisper transcription remain on your device unless you deliberately use a separately disclosed cloud feature.

What happens to an old selection

Saved Wrengle Local and Ollama selections are shown as retired. Wrengle does not silently send their old prompt, conversation, workflow, schedule, or report-recovery data to a cloud provider.

  • Old local conversations remain readable and deletable, but cannot continue.
  • Workflow steps pinned to a retired provider need attention before they can run or be scheduled again.
  • Interrupted local report requests are not replayed against a cloud provider.
  • Choosing Auto for a current feature uses a configured cloud key; with no eligible key, Wrengle asks you to finish provider setup.

See AI and privacy for the data sent by each cloud-backed workflow.

Remove old downloaded language models

Wrengle never deletes a downloaded language model automatically. To reclaim the space, open Settings → Privacy → Retired local AI files, review the app-owned files, and confirm their removal.

The cleanup is limited to Wrengle's legacy models/llm/ app-data folder. It does not delete Local Whisper, Core ML, embedding/search models, vault data, or models managed by an external Ollama installation. Once confirmed, deleted files cannot be recovered through Wrengle.

What still works offline

Editing, local search and embeddings, Local Whisper transcription, recordings, Verbatim Quick Dictation, vault recovery, and installed local plugin views can continue without a cloud connection. Generative AI features require an internet connection and a usable route: either a provider key of your own or a Wrengle AI balance.

docs / local-modelsAll documentation