Skip to content

Tagvico AI v3.2.0

Latest

Choose a tag to compare

@arturict arturict released this 25 Jul 23:05
3f95a0f

Tagvico AI v3.2.0

Tagvico 3.2 replaces the parallel dark and light surfaces with one coherent
Paper & Pine interface across the application, landing page, and bundled
documentation.

Highlights

  • Home, Documents, Ask Tagvico, Organize tags, Activity, and Settings now map
    directly to the jobs users perform.
  • Ask Tagvico shows its document and tag research, groups configured models by
    provider, and keeps every document or tag mutation behind an explicit
    approval.
  • Content requests such as read, inspect, open, or review now read the bounded
    Paperless search results, while unrelated substring matches do not start
    research.
  • GitHub Copilot now receives the saved reasoning effort, and mobile users can
    reopen conversations without losing the answer or research trail.
  • Approval cards show the actual proposed document values, while tag deletions
    recheck the approved name and linked-document count immediately before the
    write.
  • Duplicate-tag cleanup has a dedicated many-to-one review flow instead of a
    dense Settings control.
  • Page-shaped skeletons preserve the expected layout while Home, Documents,
    Activity, and provider catalogs load.
  • Document tags, provider controls, model metadata, buttons, and switches have
    stronger contrast throughout the light interface.
  • The public landing page and versioned v3 documentation now use the same
    design, terminology, provider icons, and current product screenshots.
  • Owner-only tag organization is hidden for other household roles, Ollama
    catalog inspection has one bounded deadline, and model-specific reasoning
    choices stay visually synchronized after saving.

Upgrade

Back up the tagvico_ai_data volume, pin
ghcr.io/arturict/tagvico-ai:3.2.0, and recreate only the Tagvico container.
Existing history, conversations, credentials, model choices, automation rules,
and recovery queues remain in the persistent volume.

This is a v3 update. It does not introduce a v4 migration or a parallel beta
theme.