Tagvico v3.4The Action Center for Paperless-ngx

Paperless files it — Tagvico makes sure someone acts on it. Deadlines, households, approvals, and research with every sensitive change visible.

Install v3.4.0

Explore features

Choose a provider

🗂️

Documents to assigned work

One Action Case per document with owner, due date, priority, and up to 100 checklist steps — tracked to done, not just filed.

✅

Ask Tagvico

Ask about documents and obligations while every Paperless search, document read and proposed write stays visible and approval-gated.

💬

Optional Telegram access

Give allowlisted family members cited search, uploads, action lists, and approve/reject controls through their own Paperless tokens.

🎮

Optional Discord access

Same capabilities as Telegram for allowlisted Discord users — DMs and one optional server channel — with no privileged Message Content intent required.

🔌

Your model, your boundary

Tagvico owns the safe harness. Use Vercel AI SDK providers such as OpenCode Go or an optional read-only Codex SDK adapter.

📈

Included filing utility

Opt-in reviewable metadata filing with a review queue, processing history, OCR recovery, retry controls, and restoration tools — or use Paperless-ngx v3's native AI instead.

Start here

Tagvico is a self-hosted action layer for an existing Paperless-ngx instance. It keeps Paperless as the document system of record while adding household ownership, checklists, deadlines, approval history, and a provider-neutral AI session runtime.

Reviewable AI metadata filing remains available as an opt-in utility. Paperless-ngx v3 ships native AI metadata suggestions of its own; use either, but do not run both in automatic write mode against the same fields — see Features for the coexistence guidance.

This page tracks the latest stable v3 patch release. The version menu keeps older major-version guides available, while Release notes shows exactly what changed in v3.4.

Production defaults

Pin the immutable 3.4.0 image, back up the data volume before upgrades, and start new installations in Review first mode. Companion writes are always approval-gated regardless of the metadata processing mode.