Installer or PowerShell
iwr -useb https://swarmmarshal.com/install.ps1 | iexInstalls SwarmMarshal, creates a launcher, and opens the app. You can also use the Windows button on the Download page.
Getting started
Install SwarmMarshal, connect one account, and ask your first sourced question.
This is the practical first-run path: get the app on your machine, keep your data somewhere safe, connect a single inbox, and try two workflows that show why source-grounded communication history is useful.
Install the app
Use the installer or a one-line command for Windows or macOS.
Create a local profile
Keep profile data on your computer, not inside a cloud-synced folder.
Connect one account
Start with Gmail, Outlook, Microsoft 365, or an IMAP mailbox.
Ask your first question
Try a source-cited search or a small timeline from real messages.
Install
Pick the installer that matches your computer.
The Download page always has the current release buttons and checksums. The one-line commands do the same manifest lookup from a terminal.
Package or Terminal
curl -fsSL --proto '=https' --tlsv1.2 https://swarmmarshal.com/install.sh | bashDownloads the signed package, installs SwarmMarshal.app, and opens it. Use Applications as the stable app path, especially for Apple Messages access.
First run
The setup path that keeps the first day boring, in the good way.
You do not need to connect everything at once. The best first install is small: one profile, one account, one useful question.
01
step
Download and install SwarmMarshal
Use the Windows installer, the macOS package, or the one-line commands below. When the app opens, let the welcome flow create your first profile.
Why it matters: You can stop here and look around. Nothing is connected or indexed until you add an account.
02
step
Use the default local profile folder
Accept the default local storage location unless you have a reason to move it. Avoid iCloud, OneDrive, Dropbox, Google Drive, network shares, and other folders that sync live files.
Why it matters: SwarmMarshal stores SQLite databases locally. Cloud-synced folders can create conflicted copies and broken database files.
03
step
Connect one mailbox first
Pick the account with the history you most often need to search. Gmail and Outlook use a one-time OAuth setup; IMAP accounts use the normal server settings.
Why it matters: Starting with one account keeps the first sync easy to understand. You can add more inboxes, chats, calendars, and devices later.
04
step
Choose how AI is allowed to run
For local-only use, connect a local model runtime such as Ollama. For stronger cloud drafting or synthesis, add your own provider key and set caps with that provider before heavy use.
Why it matters: Cloud model calls are optional and provider-billed. The app's routing and Spend Guard controls help keep sensitive work and costs under your rules.
05
step
Let the first sync and index pass run
Keep the app open while mail downloads and indexing begins. Search starts becoming useful as the index fills; the Today page and sync status show what is still catching up.
Why it matters: Indexing happens on your machine. The point is to make your own history searchable, not to upload it to a hosted inbox.
06
step
Keep automation conservative at first
Use Manual or Assisted behavior while you learn the app. Let agents summarize, find sources, and prepare drafts before you trust any recurring rule.
Why it matters: Drafts do not send themselves. High-stakes sends, deletes, and broad rules stay in your review flow unless you deliberately promote a narrow pattern.
Connect one source
Start with the account where useful history already lives.
Gmail and Microsoft accounts require a one-time personal OAuth app setup. If that sounds fussy, use the walkthroughs; they show each click and explain why it is needed.
Try these first
Two use cases that make the value visible quickly.
Use real mail if you can. The assistant is most useful when it can cite the exact source messages behind the answer.
Find the promise you only half remember
Goal: Use the AI Assistant as a source-grounded search tool instead of hunting through old threads by hand.
Try asking: What did I promise Alex about the renewal deadline? Show the exact messages you used.
- Open the AI Assistant after the first mailbox has indexed a useful slice of history.
- Ask about a real person, project, invoice, appointment, or deadline you remember vaguely.
- Open the cited messages before relying on the answer, then refine the question if the scope was too broad.
Build a small timeline from a thread
Goal: Turn a messy conversation into dated events, decisions, promises, and open questions you can verify.
Try asking: Build a chronological timeline for the warranty dispute with dates, claims, promises, and source links.
- Start with a sender, project name, subject line, or search result set that has enough messages to matter.
- Ask for a timeline, not a summary, and require source links for each important claim.
- Use the result as a draft: check the citations, remove weak claims, and ask for a tighter version if needed.
A good first session
Install it, connect one inbox, and ask one question you actually care about.
After that, decide whether to add calendars, more accounts, local models, Telegram, MCP, or supervised helpers. The first win should come from your own history.