Loop Desk is an always-on business workspace that takes incoming signal (email, forms, feeds, notes) and turns it into briefs, watch items, and next actions.

Does Loop Desk send emails on my behalf?

Loop Desk can draft responses, but nothing sends until you approve and explicitly trigger it. The approval boundary is fundamental.

What signal sources does Loop Desk support?

Email, RSS/Atom feeds, form submissions, manual notes, and webhooks. The desk treats all sources equally in its processing loop.

rev 99 — Loop Desk changelog

rev 992026-05-02

Roadmap hot-strip sparkline + Trending now (7d momentum) section + status filter chips + v1 mostTrending

14-day vote-trend sparkline on the 'Most requested' hot-strip rowsCloses the named rev-98 next-sprint candidate. Rev 98 shipped the per-item 14-day sparkline on the main roadmap list; rev 97's most-requested hot strip showed cumulative count only. Rev 99 surfaces the same trajectory shape inline on every top-3 hot-strip row so visitors see at one glance which leaders are picking up momentum vs. which are static at their cumulative count. Compact 44×14 variant of the rev-98 sparkline keeps the strip scannable. Hidden on viewports below 540px where the row already wraps.
'Trending now · last 7 days' second hot strip — momentum-based rankingThe rev-97 'Most requested' strip ranks by cumulative count which means an item that's just started picking up steam can't surface above an established leader until weeks of votes accumulate. Rev 99 adds a second hot strip directly below it that ranks by trailing-7-day momentum (sum of votes in the last week). Tiebreaker is cumulative voteCount so a sustained week beats a one-day spike. Excludes items already in the top-3 cumulative ranking so the two strips never duplicate — the goal is to surface what's about to start showing in the cumulative ranking, not to repeat it. Amber accent on the strip distinguishes the momentum reading horizon from the brand-green cumulative one.
Status filter chips (All / Next up / Coming soon / On the radar)The roadmap page has accumulated 13 items across 3 phases over rev 38/97/98. A visitor who only cares about 'what's shipping next' had no way to scope the view without scrolling past everything. Rev 99 adds a chip row above the phase list with per-status counts; tap a chip to scope, tap All to clear. Filter is pure CSS via a data-attribute on <body> — the SSR'd phase tree never re-renders, and items just hide via the matching `[data-roadmap-status]` selectors. Empty phase containers hide via :has() so a filtered phase doesn't show a head with no items. Persists per-browser in localStorage so a returning visitor keeps their preferred scope.
v1 endpoint extended with `momentum7d` + `mostTrending` + OpenAPI typed schemaGET /api/v1/roadmap-votes now returns `momentum7d` per item (sum of trailing-7-day votes) plus a `mostTrending` ranking that mirrors the new /roadmap second hot strip. MCP hosts and code generators reading the public marketing surface can render the same two-axis view (cumulative + momentum) in their own UIs without scraping. OpenAPI 3.1 typed schema covers the new fields so client SDK generators see the discriminated `mostRequested` vs `mostTrending` shape exactly. Cache headers unchanged (60s public / 300s s-maxage).