Email becomes the archive. Loops keeps the obligations visible.
Loops scans, summarises and tracks the email threads that still matter, then surfaces only the open loops: replies owed, responses expected, context worth knowing and decisions that should not drift away.
What it does
Email is not going away tomorrow. It is too embedded in work, accounts, receipts, approvals, identity and the weird plumbing of the internet.
But it is starting to feel like legacy infrastructure. We will move away from email the same way we moved away from letters: gradually, unevenly, with a long transition period where the old system still has to be supported.
Loops is built for that transition. It is a lightweight window into email for people who do not want to live in an inbox anymore.
The app scans and summarises email, pulls out what matters, and tracks the obligations hiding inside each thread. If your everyday AI dashboard is doing most of the ambient coordination, Loops becomes the specialist layer that keeps email from becoming a dark corner full of missed context.
Open loops
The core unit is the loop.
A loop is an unresolved obligation. You sent something and are waiting for a response. Someone sent you something and is waiting for a reply. A decision is pending. A document needs review. A thread has gone quiet but still matters.
Loops turns those loose threads into a small, manageable list:
- waiting on me
- waiting on them
- needs a decision
- safe to archive
- context only
That is the whole point. It should not become another inbox. It should tell you what remains open, why it matters, and what would close it.
Why it exists
Most email tools still assume email is the main interface for work. Loops assumes the opposite. Email is becoming a context repository: still essential, still searchable, still legally and operationally useful, but increasingly not the place where the real work happens.
That creates a messy middle. AI products will read, route and summarise more communication for us, but email will keep receiving invoices, approvals, updates, newsletters, one-off requests, booking confirmations and institutional nonsense.
Loops is a proposal for that messy middle. A small tool for keeping the old protocol under control while the new ones take over.
Status
Loops is an early concept with an interactive Claude prototype. The embedded preview may be blocked by Claude or Cloudflare in some browsers, so the direct prototype link is the reliable way to open the simulation.