Pantasso Setup Guide

Pantasso Setup Guide

This guide is for a company getting started with Pantasso. The normal path uses the app's source selectors and plain workspace choices, not command lines, environment variables, raw ids, or tokens. Keep it nearby during setup and return to it when you add a new source, invite a new agent, or need a quick health check. Engineering details are kept at the end for operators.

What Pantasso Does

Pantasso gives your company and your AI assistants one shared place to find and use company context.

In practice, that means Pantasso can connect to the tools where work already happens, organize the useful history, and make it searchable with citations. Your team can ask questions such as:

• What did we decide about this project?
• Where is the latest document?
• What open items came out of this conversation?
• Which source did this answer come from?
• What did an assistant read or cite before producing work?

Pantasso starts with Slack, Google Workspace and Drive, Google Docs, Telegram, GitHub, and approved files. More sources can be added later after the first workspace is working.

The First Win

You do not need every source connected to see value. The first win is:

1. Connect one approved source that matters this week.
2. Ask one real company question.
3. See cited context or a clear explanation of what is missing.
4. Review the operating brief for open items, decisions, source freshness, and next actions.
5. Confirm one assistant can use Pantasso before answering.

After that works, add more sources and run the deeper readiness checks.

Why Setup Matters

Setup is how the company teaches Pantasso what it may trust. It answers four plain questions:

• What may Pantasso read first?
• What should stay private?
• Which question should prove value this week?
• Which assistant should use Pantasso before answering?

Good setup keeps the first source small, makes privacy decisions explicit, and creates a simple path from approved source to answer, brief, assistant check, and next action.

Pick Your First Source

Choose the source that already contains the answer you want Pantasso or an assistant to find.

Do not start with every source unless access, privacy, and scope are already clear. It is easier to add more context than to explain a noisy first workspace.

Example: Common Company Stack

A normal small company might already have Obsidian notes, Google Drive, Slack, GitHub, local documents on a computer, AI agents running on a DigitalOcean droplet, and a Vercel website. Pantasso should fit that setup instead of asking the team to change everything first.

Use this order for a no-payment first pass:

1. Start with Obsidian or local docs when you want the fastest proof. Upload one approved Markdown folder or a small set of current project notes.
2. Add one Google Drive folder when shared plans, specs, or meeting notes are the more trusted source.
3. Add one Slack channel after the team agrees which conversations Pantasso may read.
4. Add one GitHub repository when active issues or pull requests explain what the team is building or fixing.
5. Ask one real question and review the cited answer or gap report.
6. Generate the operating brief so the team can see open items, decisions, source freshness, and next actions in one place.
7. Connect existing AI agents after the first answer works. Keep the agents where they already run, but give them a Pantasso assistant profile and a rule: check Pantasso before answering company-specific questions.
8. Leave the website separate until there is approved context worth using. A Vercel site can later use Pantasso context for public pages, support, or handoff workflows, but it should not block the first setup.

The goal is not to connect everything on day one. The goal is to prove that one assistant can answer one real company question from one approved source.

What You Should Have After Day One

By the end of the first setup session, the team should have:

• One source connected or clearly marked as needing access.
• One real question answered with sources, or a clear gap report.
• One operating brief showing open items, decisions, source freshness, and next actions.
• One assistant profile saved and smoke-tested.
• A short list of private or excluded areas.
• A support handoff only if something needs Pantasso help.

Plain Terms

Setup Checklist

Before setup, choose:

• A workspace name, such as your company name.
• One company owner who can approve source access.
• One workspace owner who can complete hosted setup and review source access.
• The first sources to connect: Slack, Google Drive/Docs, Telegram, GitHub, or files.
• Which AI assistants should use Pantasso first.
• Which channels, folders, chats, and local folders are approved for launch.
• Which areas are private, ignored, or require separate approval before import.
• Where the source setup summary, support packet, and exported backup should be stored.

You do not need to reorganize your whole company before starting. Begin with the sources that matter most this week.

Step 1: Create The Workspace

Create a company workspace and confirm that the hosted setup checklist is healthy. Pantasso prepares the source list, checks what is ready, and shows the next steps for sync, search, operating brief, assistant smoke test, backup, support packet, and the console.

What you should see:

• A workspace health check passes.
• The workspace is prepared for private company data and readiness checks.
• A source checklist is created for the first tools you chose.
• The Pantasso console opens in a browser.
• The console shows setup, sources, search, memory, decisions, and audit areas.
• Any missing credentials or stale sources are clearly listed.
• Any visibly malformed credential values are caught before a live sync.
• After access is approved, Pantasso can run a small live check to confirm the selected Slack, Google Drive/Docs, Telegram, GitHub, or file source can be read.

Step 2: Connect Sources

Start with one or two sources. Add more after the first search works. The setup checklist can include all planned sources at once, but it is normal for Slack, Google Drive/Docs, Telegram, or GitHub to show "needs attention" until access is approved. File sources need an approved folder or upload location. After access is approved, Pantasso runs the live source check for only the selected sources. This confirms access without importing everything.

In the hosted app, use Sources for the normal path:

• Choose Slack, Google Drive/Docs, Telegram, GitHub, or Files.
• Use Choose from connected targets to select approved channels, folders, calendars, labels, chats, repositories, projects, uploads, or file sets.
• For Files, upload text, Markdown, or JSON files directly when that is the fastest first source.
• If choices are not visible yet, finish the account connection or use Files for first value. Normal users should not paste raw ids or tokens into the setup flow.
• Save the selection, check access, then bring in recent items.
• Use Operations to retry, cancel, schedule, remove a mistaken source draft, or open a redacted support request when a credential or worker setup gap blocks the source.

Slack

Use Slack when decisions, requests, follow-ups, and project discussion happen in channels or threads.

Use the Slack selector to choose which channels Pantasso should read first. Start narrow: one company channel and one project channel are enough for a first pass. If the channel list is not available yet, ask the workspace operator to finish the Slack connection.

The first import writes Slack messages into company context, makes them available for cited answers, and records redacted support information with refs and counts only.

Google Drive And Docs

Use Google Drive and Docs for plans, specs, meeting notes, operating docs, and shared files.

Start with one selected folder or a small document set that represents active company work. Avoid connecting every file on day one unless you need broad history immediately. If the folder selector is not available yet, ask the workspace operator to finish the Google Workspace connection.

The first import reads the approved Drive and Docs material needed for cited answers.

Telegram

Use Telegram when company or external conversations happen there.

Use the Telegram selector to choose the chats and date window Pantasso should read first. Make sure the bot or account used for setup can see those chats. If the chat selector is not available yet, ask the workspace operator to finish the Telegram connection.

The first import reads the approved, bot-visible messages, makes them available for cited answers, and records redacted support information with refs and counts only.

GitHub

Use GitHub when issues, pull requests, or code review threads explain what the team is building, fixing, or waiting on.

Start with one active repository selected in the app. You do not need to connect every repo on day one. Pick the repo that has the work your team is asking assistants about. If the repo selector is not available yet, ask the workspace operator to finish the GitHub connection.

The first import reads bounded issue and pull request activity, makes it available for cited answers, and records redacted support information with refs and counts only.

Local Files

Use the Files selector for Obsidian vault folders, exported docs, Markdown, text, JSON briefs, specs, meeting notes, and generated artifacts. You can upload text, Markdown, or JSON files directly when that is the fastest first source. Convert CSVs to Markdown, JSON, or text before the current local-files ingest path.

This is often the simplest first source because it does not require external credentials.

Before importing, Pantasso checks whether the folder is a good first setup folder. It reports supported file count, skipped file types, approximate size risk, skipped symlinks or high-churn folders, and whether the folder sits inside the expected workspace scope or outside the workspace root. Warnings usually mean "start narrower," not "stop." Current file-size limits and large-artifact storage behavior are documented in PANTASSO_INLINE_TOKEN_0.

Step 3: Bring In Recent Items

After each source is selected and access is approved, bring in a bounded first set.

What a successful first import should show:

• The source appears in the console.
• Pantasso reports how many messages, documents, files, or payloads it saw.
• Any unreadable records are listed as quarantines instead of silently ignored.
• Search results include citations back to the source.

After the first successful import, repeat syncs continue from the latest saved checkpoint when the source supports it. This keeps normal updates small and reduces duplicate reads. Use a fresh run or a specific checkpoint only when the support packet or setup screen names that recovery path.

If something fails, do not guess. Use the source health check and send the support packet to Pantasso support.

Step 4: Try Search With Citations

Ask a real company question, not a demo question.

Good first searches:

• What decisions were made this week?
• What are the open items for the current project?
• What changed in the latest plan?
• Where did we discuss onboarding handoff?
• What documents mention launch readiness?

Every useful answer should point back to sources. If a search result does not show citations, treat it as incomplete.

For assistants, the normal version of this check is a cited question: the assistant asks Pantasso, receives only the retrieved context and citation ids it is allowed to use, and answers from that context. If Pantasso returns insufficient context, the assistant should say what is missing instead of guessing from memory.

After search works, generate the operating brief. It is the short daily view of the workspace: active projects, open tasks, accepted decisions, useful citations, source freshness, warnings, and the latest handoff references. Use it when you want a quick reminder of what Pantasso sees right now.

Before handoff, run the combined verification check. It confirms workspace health, source readiness, durable status, cited search, the operating brief, and assistant profiles in one report.

Step 5: Set Up AI Assistants

Pantasso works best when each assistant has a clear role and uses Pantasso as its shared company context.

You may hear names such as Pantasso Assistant, Pantasso Sales, Pantasso Marketing, Pantasso Support, and Pantasso Research. Treat them as business-focused team assistants:

• Pantasso Assistant can help with planning, summaries, and company memory questions.
• Pantasso Sales can help with pipeline context, lead follow-up, and account summaries.
• Pantasso Marketing can help with campaign context, audience language, and launch materials.
• Pantasso Support can help with support questions, issue summaries, and escalation context.
• Pantasso Research can help with cited research notes, competitor context, and open questions.

For each assistant, decide:

• What it is allowed to read.
• What work it is allowed to draft.
• What needs human approval before being sent, changed, or committed.
• Which name it should use when work is logged.
• Where its finished notes, drafts, reports, or files should be saved.

The simple rule: assistants should look in Pantasso before they answer, and they should cite the source when the answer depends on company information.

If the company already has AI agents running somewhere else, such as a DigitalOcean droplet, keep them there for the first setup. Pantasso does not need to replace the agent runner. After Pantasso can answer from one approved source, give each existing agent the right Pantasso profile and test that it asks Pantasso before answering company-specific questions.

The app saves a plain-language profile for each enabled assistant: name, role, allowed sources, where to put finished work, and the first search test to run.

Each profile is an identity and operating contract, not a new credential grant. Use the saved profile name from the app, Slack, Telegram, or your agent runner. That keeps assistants working from the same company context instead of each one building a separate memory in its own chat.

For public guidance on assistant scopes, see Agent Profiles.

Step 6: Use The Weekly Routine

Once setup is working, repeat this routine:

• Check source health.
• Run sync for active sources; normal repeat syncs resume from the latest saved checkpoint.
• Review quarantines and fix or discard them.
• Search for current project context.
• Review the operating brief for active projects, open tasks, decisions, and warnings.
• Export or review audit packets for important assistant work.
• Add any new source that became important during the week.

Final Setup Sign-Off

Before treating the workspace as ready for normal use, complete the final workspace readiness checklist.

The final sign-off should confirm:

• Connected sources and known pending sources.
• A live console, not static sample data.
• At least one real search with citations.
• A current operating brief for active projects, open tasks, decisions, and warnings.
• Agent read/write boundaries.
• Privacy, ignored areas, and retention choices.
• Backup location and restore smoke-test result.
• Support packet location and sharing rules.
• First follow-up review date.

The backup check creates an export, records a manifest, and confirms the copied workspace can still produce status, an operating brief, and cited search results.

Support Packet

When asking Pantasso for help, create a support packet. It is a single file that collects the workspace health check, source setup summary, source health check, latest durable status, operating brief, cited search context, backup manifest and restore smoke result, quarantine and replay refs, audit packet references, and recommended next steps.

The source setup summary is redacted: it shows what sources are configured and which credential names are expected, but not credential values or raw private payload bodies. The support packet is meant to replace long troubleshooting threads and one-off screenshots.

Useful details to send with the support packet:

• Workspace name.
• Which source failed or looks stale.
• The time the issue happened.
• The question you searched for, if search was the issue.
• Any quarantine, source payload, or audit refs shown in the console.

Engineering And Operator Reference

This section keeps the technical setup details that support the app workflow. It is for workspace operators, Pantasso support, and engineers.

Source Credentials And Raw Scopes

The hosted app should never ask a business user to paste provider tokens into the browser. Provider credentials are configured server-side by the workspace operator or a credential exchange. Current managed workers use:

• Slack bot credentials for approved Slack channels.
• Google Workspace credentials for approved Drive and Docs folders.
• Telegram bot credentials for approved chats and date windows.
• GitHub credentials for approved repositories.

The app selector may store raw implementation values behind the scenes:

• Slack channel ids or bot-joined public-channel discovery.
• Google Drive folder ids, file scopes, or Drive queries.
• Telegram chat ids and date windows.
• GitHub repository names and bounded issue or pull request windows.
• Files paths under the approved workspace files root, or uploaded text, Markdown, and JSON files.

Keep credentials in the operator environment or secret manager. Do not store tokens, OAuth refresh tokens, service account JSON, bot tokens, or raw private payloads in source setup records or support requests.

Assistant Profile References

Operator setup also writes assistant profile artifacts under workspaces/<company-slug>/agent-profiles/: one plain-language note, one JSON profile for each enabled assistant, and an agent-profiles.json summary. The stable actor id in those JSON files is for CLI, API, Slack, Telegram, and tool integrations; the normal app surface should show the profile name and role.

Support References

When support needs exact references, copy the redacted ids shown by the console or support packet: quarantine id, source payload id, audit packet id, job id, or backup/restore refs. These are troubleshooting handles, not user-facing setup steps.

Quick Reminders

• Start narrow. Add more sources after the first useful search.
• Prefer real work questions over demo questions.
• Citations matter. They are how you know where an answer came from.
• Quarantine is normal. It means Pantasso saved the problem for review.
• Assistants should use Pantasso for company context instead of relying on memory from a single chat.