Files and Obsidian integration
Use a focused set of local documents or an approved Obsidian folder to prove a cited answer before authorizing a larger cloud source.
The short answer
Pantasso can read approved Markdown, plain-text, JSON, and Obsidian vault folders through guided upload or an operator-approved path. It preserves file identity and source references so answers remain traceable. The workspace does not crawl the computer by default: owners choose the files or folders, and Pantasso applies format, size, path, and safety checks.
The current file path supports approved Markdown, plain text, JSON, and Obsidian vault folders. Those files can become documents, projects, tasks, decisions, and artifacts while retaining their source identity. Browser upload accepts Markdown, text, and JSON; approved local paths support controlled folder-based setup.
Notes, plans, policies, meeting records, and other readable documents.
Approved structured exports that fit the documented upload and mapping boundaries.
A selected vault folder, not an automatic crawl of every vault or computer file.
Pantasso does not crawl the entire computer, follow unapproved paths, or treat every file in a home directory as company knowledge. Browser upload does not accept arbitrary binary formats. Unsupported formats, oversized files, unsafe symlinks, churn-heavy folders, inaccessible paths, and excluded content remain outside the workspace.
The owner selects individual browser uploads or an operator-approved server path. Path checks enforce allowed roots and protect against unsafe symlink or churn-folder behavior. Pantasso only reads material made available to that configured path; an assistant profile cannot add folders or expose files that were never approved.
Choose one folder or small file set tied to a recurring question. For browser upload, select approved Markdown, text, or JSON files; current limits are 512 KB per file and 2 MB total. For a folder path, Pantasso checks location, formats, size risk, and access before the first sync and cited question.
Approved files support a first cited answer, an explicit gap report, an operating brief, source health, backup and restore checks, and a grounded assistant smoke test. Pantasso can organize useful records from the content while preserving links to the originating file.
Good first questions include “What decisions are recorded in these meeting notes?”, “Which projects have open follow-ups?”, and “What does the current policy say about this request?” A focused file set makes it easy for the owner to verify both the answer and any missing context.
A browser upload represents the content supplied at that time and must be updated through another approved ingest when files change. Approved folder sources can be checked and synced again with source-health evidence. The configured run history—not the file’s mere presence—shows whether Pantasso has current content.
Current boundaries
Pantasso is sold with founder-led onboarding. We scope the first source, question, access boundary, and proof of value together instead of promising instant coverage.
Browser uploads are limited to Markdown, text, and JSON, currently 512 KB per file and 2 MB total.
A local folder must be available through an explicitly approved server path; Pantasso cannot browse an end user’s computer remotely.
Attachments, images, PDFs, office files, embedded media, plugins, and Obsidian-specific behavior require separate supported paths or evaluation.
Explore a cited answer and an honest gap in the demo, then plan one useful source with Pantasso.
