Skip to content

Tagvico AI v3.1.1

Choose a tag to compare

@arturict arturict released this 24 Jul 00:07
749a38a

Tagvico AI v3.1.1

Tagvico 3.1.1 completes the reliability and product-quality work started in
3.1.0. It keeps Paperless-ngx as the source of truth while making automation,
provider configuration, recovery, and Ask Tagvico coherent enough for daily
use.

What changed

  • Ask Tagvico now has durable conversations, new-chat, search, rename, guarded
    deletion, retry, copy, stop, model selection, and privacy-safe tool activity.
  • Paperless research is intent-aware. Greetings do not query the archive;
    counts, recent-document lists, searches, and bounded document reads use
    purpose-specific tools.
  • Settings exposes eight supported runtimes with live model catalogs,
    write-only API-key fields, connection probes, and first-class ChatGPT and
    GitHub Copilot authentication. Direct Anthropic and Azure OpenAI setup is no
    longer shown.
  • Trigger tags are optional. With no trigger tags configured, every eligible
    new document is scanned, and manual scans report exact eligible, processed,
    staged, skipped, and failed counts.
  • Four remains the default maximum tag count, with stronger prompts for the
    smallest useful tag set and an archive-specific custom prompt plus an
    advanced system-prompt editor.
  • Activity includes metadata diffs, custom fields, token usage, original state,
    bulk rescan, exact restore, orphan validation, and deliberate cleanup.
  • AI and OCR failures retry up to three times. Permanently failed and ignored
    documents have dedicated recovery queues and navigation counts.
  • Duplicate-tag proposals are presented as explicit many-to-one groups and
    retain per-group approval plus separate move and delete phases.
  • App, versioned docs, landing page, package icons, and favicons use one
    transparent Tagvico AI mark with no inherited Paperless AI artwork.

Upgrade

Back up tagvico_ai_data, pin
ghcr.io/arturict/tagvico-ai:3.1.1, and recreate only the Tagvico container.
No destructive settings migration is required. Existing environment keys remain
compatible, and the persistent data directory continues to hold configuration,
history, queues, sessions, and restore snapshots.

After upgrading, open /docs/, test the Paperless connection, refresh the live
model catalog for each configured provider, run a manual scan, and verify one
non-sensitive Ask Tagvico research request before enabling Automatic write
mode.