Use Cases

These are worked examples of how real people fit OpenLoomi into their day. Each use case is a third-person story — the problem the persona had, the Loop / Memory / Loomi Pet capability that changed it, and the setup commands that made it work.

Overview

Every use case below is built on the same three primitives:

• Loop — the proactive judgement engine that polls connected channels and surfaces typed decision cards every 10 minutes. The user taps Approve / Edit Draft / Later / Skip; Loop never sends without them.
• Memory — the local-first tiered store in ~/.openloomi/data/memory/ that grounds every card with prior context. The longer it's used, the sharper the drafts get.
• Loomi Pet — the little fox (or capybara) on the desktop that bubbles the high-confidence cards and pushes the Brief at 9 AM / Wrap at 6 PM.

Loop's five built-in sources are Email / Calendar / GitHub / Slack / Linear — anything else (HubSpot, Salesforce, Obsidian, X, RSS, Product Hunt, Reddit) registers as a custom channel once via the openloomi-loop skill.

Pick the persona that matches the day-to-day, or skim the headlines for one that sparks an idea.

Available use cases

• Engineering Daily Sync — How an engineering lead stops rewriting dev reports every night and lets OpenLoomi keep the Loop running
• Founders & Business Development — How a founder stops losing follow-ups across hundreds of contacts and lets Loop carry the relationships — drafts grounded, approval still theirs
• Global Managers — How a manager across three time zones stops waking up to a 500-item inbox and lets the Brief triage the night — Loop polls while they sleep, Wrap tells them what shipped
• Unified Inbox — Auto-Fetch + Context-Aware Draft Generation — How a high-volume inbox worker stops re-reading 40-message threads before every reply — Loop drafts grounded in memory, approval required, they move on
• Product-Research Iteration — How a PM stops stitching the next sprint together from memory and lets Loop fold Linear, GitHub, screen memory, and Obsidian into one queue
• Industry Intelligence — How an analyst stops re-researching last week's launches and lets Memory carry the research — Brief rolls up the channels that were wired, agent does the reading in chat
• Sales Teams — How a RevOps lead stops doing pipeline archaeology every Friday and lets HubSpot signals flow into the queue — Memory carries every prospect, approval is required before anything sends
• X Content Drafting — How a content creator stops typing drafts from scratch every Sunday night — Loop watches X signals, agent drafts in their voice grounded in Memory, an explicit Approve is required before anything sends

Related

• Loop — the proactive judgement engine behind every always-on use case
• Memory — what makes each use case smarter the longer it's used
• Attention Agent — Loomi Pet, the little fox that bubbles the high-confidence cards