Philosophy
One stream, not many
Most productivity tools give you a pile. A Kanban board to rearrange. A nested hierarchy of projects and tags and filters. A sea of starred emails, open tabs, and Slack DMs that you’ll “come back to later.”
Loopr is different. Everything — emails, calendar invites, a reminder to call your mom, a recurring weekly review, your own scribbled note, even notifications from tools like GitHub or Linear — enters a single stream called the loop. You process the loop the way you process any queue: oldest first, one thing at a time, until it’s empty. Then you go live your life, and when new things arrive, they come through the loop too.
Why a ring?
Because nothing truly disappears. When you complete an item, it’s gone from the queue but preserved in history. When you snooze something, it leaves your attention for a bit and then re-enters the loop at its original spot — not at the top, not at the bottom, but where it was, so you don’t get to escape ignoring it by snoozing it past tomorrow.
The loop is a ring buffer: items rotate through, get processed, and pass. Drift is visible by design. If an item has been in the loop for 30 days, sitting at the top, you’ll see it every single time you open the app. That’s the point.
Examples
“My inbox is a task list I’ll never finish.” Connect a Gmail stream. One item per thread, AI-summarized, scored for urgency. When you archive it in Loopr, it archives in Gmail. When new mail arrives, it’s one more item in the loop — not a separate context to switch into. Process like anything else: complete, snooze, delegate, skip.
“I keep forgetting to look at my calendar.” Connect a Google Calendar stream. Upcoming events show up in the loop with enough lead time to prepare. Past events disappear on their own.
“I’m drowning in tool notifications.” Streams exist for GitHub, Linear, Slack, RSS, iOS Reminders, and more. Each notification becomes one item, summarized and prioritized, so you triage one loop instead of jumping between five tabs.
“I have no idea what I did this week.” Every day Loopr writes a short markdown reflection of what you completed, what slipped, what’s on the horizon. Weekly, monthly, quarterly rollups happen automatically — each level reads the level below, so the quarterly doesn’t try to remember every item, just the shape.
“I delegated this two weeks ago and never followed up.” Hit d
on any item, pick the people, set a follow-up window. The item leaves the loop.
Each person gets their own private link they can use to mark their part done
with a note — and the result lands back in your loop with the original
context preserved. When the follow-up window passes (or everyone reports
back), the item returns to your loop. Same loop, no separate project view.
The non-goals
Loopr intentionally does not:
- Let you reorder items. If something should be sooner, complete or snooze the things in front of it; that’s why they’re in front of it.
- Support nested lists or projects. A flat stream is the feature.
- Try to be calendar, CRM, or chat. It’s an inbox for everything that isn’t already one of those.
- Motivate you. It reflects; you decide.
How to read the rest
Start with The Loop for mechanics — items, states, keyboard navigation. Then pick whatever feature is relevant to you. Every section stands alone.