Use cases
The work SwarmMarshal is meant to absorb.
Not moonshot automation. The recurring, context-heavy chores that steal attention because they sit across five different tools.
A vague memory becomes a sourced answer
Ask
"What did Acme promise?"
Gather
Messages, files, dates
Answer
Cited facts + links
A messy dispute becomes a timeline
Scope
Matter or date range
Order
Events and deadlines
Packet
Claims and sources
A recurring headache becomes a workspace
Describe
"Track my rentals"
Build
Forms, tables, views
Shape
Keep asking for changes
A helper device joins the desk
Main
Desktop runs the desk
Pair
Laptop adds its access
Recover
Agents repair common breakage
More patterns
Concrete situations it can make calmer.
Inbox triage
TriggerA morning pile of newsletters, receipts, client notes, and one actually urgent request.
OutcomeBy the time you sit down, the urgent thread is surfaced, routine replies are drafted, and low-value noise is filed for review.
Vendor history
Trigger"What is the story with Acme's security team?"
OutcomeThe graph pulls the Acme neighborhood and answers with a grounded summary plus links to the exact threads.
Cross-device help
TriggerYour desktop is the main desk, but your laptop is the one connected to a channel or account.
OutcomePair them once. Findings flow over LAN, and fallback transport keeps the work from disappearing when the network changes.
Workspace on demand
Trigger"Track my rental properties."
OutcomeVibes generates the schema, fields, and views. You keep shaping it by asking for changes in plain English.
Repeatable admin
Trigger"Every Friday, summarize the week's invoices and flag anything odd."
OutcomeAn agent drafts the skill, runs it once for review, then waits for approval before it becomes part of the routine.
Internal tools
TriggerA ticketing system, database, or workflow app already has the facts you need.
OutcomeAdd it as a connector. Its tools show up beside the built-ins, behind the same visible approval flow.
Multi-channel relationships
TriggerA lead starts on email, moves to chat, and finishes in Apple Messages.
OutcomeSwarmMarshal keeps one conversation and one contact record, then lets you reply where the person actually is.
Cost-aware AI
TriggerClassification is cheap, writing needs quality, and private notes should stay local.
OutcomePer-task routing keeps the right model on the right job, with budgets before the bill becomes a surprise.
Attention correction
TriggerThe model marks a key client as low priority once.
OutcomeYou override with a single click. The pattern updates and stops misjudging that sender.
Self-healing setup
TriggerOAuth expires, a browser capability is missing, or the local AI stack gets stuck at the worst possible moment.
OutcomeThe app repairs what it can, uses paired devices where possible, and keeps the fix understandable when you need to step in.
