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 181 — Loop Desk changelog

rev 1812026-05-08Accelerating

Closes the named rev-180 next-sprint candidate (4-week shipping cadence trend sparkline) inside the rev-180 dashboard ShippingCadencePill so operators see trajectory shape (accelerating / steady / cooling) at a glance + extends the rev-178 GET /api/v1/changelog/cadence response with a `weeklyCadence` per-week aggregate + `peakWeek` so MCP hosts render the same trajectory shape without re-bucketing the per-day list client-side + two more industry onboarding templates (independent veterinary specialty / referral practices with controlled-substance + named-specialist continuity discipline + small museums / cultural institutions with collection-care + grant-cycle + donor-stewardship discipline) close two more rev-180 named radar candidates at the templates axis — the cluster reaches thirty-five named verticals — closes the descriptive→trajectory loop on the cadence axis across all three operator-loaded surfaces (in-app pill rev 180 + sparkline rev 181, public /changelog/cadence calendar rev 179, public /changelog 'this week' pulse pill rev 179) — 103rd unbroken cadence rev (rev 181)

4-week shipping cadence trend sparkline on the rev-180 ShippingCadencePillCloses the named rev-180 next-sprint candidate. Until rev 181 the rev-180 ShippingCadencePill answered 'how many revs shipped this week?' as a single number — accurate but trajectoryless. Rev 181 adds a 4-bar inline sparkline showing per-week rev counts oldest → newest, with the latest week (rightmost bar) rendered in brand-color teal to match the rev-180 pulsing dot palette and the rev-179 calendar peak-day accent. Operators now see whether Loop Desk's cadence is accelerating, steady, or cooling at a glance — pairs with the rev-180 pill copy (which names the latest week's count) to give two reading horizons in one pill: the number (rev 180) + the shape (rev 181). Pure derived state — server passes the per-week buckets, computed once at render time on the server from the rev-37 changelog-releases shared module. Hidden when every week is zero so quiet workspaces don't see a broken-looking sparkline. The sparkline mirrors the rev-179 public /changelog/cadence calendar heatmap at a smaller scope (4 weeks vs 90 days) so the in-app + public cadence vocabulary stays consistent across both surfaces. Strategic significance: the cadence-axis instrument cluster now reads at three reading horizons across both surfaces (dashboard pill = pulse + sparkline + count, public /changelog head = pulse pill, public /changelog/cadence = full 90-day calendar). For owner-led teams that chose Loop Desk over per-cycle-credits competitors because of the visible-velocity signal, seeing both the velocity number AND the trajectory shape continuously in the dashboard status bar is the cheapest possible retention reinforcement.
/api/v1/changelog/cadence response gains `weeklyCadence` + `peakWeek`Pure additive on the rev-178 cadence response shape — extends with `weeklyCadence` (per-week aggregate, oldest→newest, 7-day chunks anchored to today's day boundary) + `peakWeek` so MCP hosts can render the same 4-week sparkline trajectory the rev-181 dashboard ShippingCadencePill uses without re-bucketing the per-day list client-side. The latest weekly bucket matches the trailing-7d count exactly so the rev-181 sparkline rightmost bar reads as the same number the pill copy names, and the protocol-bound surface keeps that contract uniform with the dashboard. Existing v1 consumers reading only `cadence` keep working since `weeklyCadence` + `peakWeek` are new sibling fields — zero migration cost on either side. Pairs the rev-181 in-app sparkline with the protocol-bound surface so the cadence vocabulary stays consistent across all four cadence surfaces (dashboard pill, public /changelog/cadence heatmap, public /changelog 'this week' pulse pill, v1 endpoint). The OpenAPI 3.1 spec types both new fields in the same cycle the dashboard primitive ships — the cadence pattern from rev 78 onward (every dashboard primitive gets typed in the OpenAPI 3.1 spec in the same cycle it ships) reaches its 92nd unbroken rev with rev 181. Strategic significance: the upcoming MCP server (Q3 #1) gets typed access to both the high-resolution per-day cadence shape (rev 178) AND the low-resolution per-week trajectory shape (rev 181) without designing custom aggregation tooling — pure protocol-translation work.
Two more onboarding templates — Independent veterinary specialty / referral practices + Small museums / cultural institutionsCloses two more of the rev-180 named radar candidates at two more underserved verticals where regulated discipline is the load-bearing differentiator. Veterinary specialty / referral practices (independent oncology, cardiology, surgery, dermatology, internal-medicine specialty practices — 4 high-importance memory entries: referral hygiene with named referring DVM + named primary-care practice + last-touched date + structured 5-business-day post-visit clinical summary, controlled-substance compliance with 24-hour reconciliation match across Schedule II-V dispensing, named-specialist continuity through the full treatment cycle unless documented hand-off, post-procedure recall cadence red flag on any missed recheck > 7 days without logged owner outreach + 1 sample referring-DVM clinical summary gap signal). Small museums / cultural institutions (independent small museums, historical societies, cultural-heritage institutions, regional galleries — 4 high-importance memory entries: collection-care discipline with named condition assessments + environmental controls + chain-of-custody log per accessioned object, donor stewardship cadence with three named touchpoints/year for $1K+ donors, grant-cycle red flag on midterm reports > 14 days late, earned-revenue diversification red flag at < 25% of operating budget + 1 sample late-grant-report signal). Two new `OnboardingTemplateKey` enum values (`veterinary_specialist`, `museum_cultural_institution`) extend the rev-19 enum without migration. The templates cluster is now thirty-five named verticals deep — closes the day-1 starvation-point story across two more underserved owner-led segments where regulated discipline (DEA controlled-substance + AAM accreditation + grant-cycle compliance) is the load-bearing differentiator against generic AI tools.
Cumulative visual polish — sparkline brand-color hover state + 7 new SEO keywords + radar copy refreshCumulative micro-polish (every rev 22+ has carried at least one). The new rev-181 ShippingCadencePill sparkline carries three visual states (default neutral / active brand-color teal / latest-week brand-color filled) plus a hover-emphasis on every non-empty bar so the sparkline reads as tactile rather than static — operators hovering the pill see the trajectory pop at the same moment the tooltip surfaces the per-week numbers. Plus the rev-181 templates copy refresh — 'thirty-five verticals today' replaces 'thirty-three' across hero + metadata + JSON-LD CollectionPage block + radar copy refresh names the next vertical wave (independent financial planners with concentrated-client discipline + small specialty manufacturing + independent home-inspection practices + owner-led commercial cleaning operators) now that veterinary-specialist + museum/cultural-institution are shipped. Seven new SEO keywords for the veterinary-specialty + museum/cultural-institution axes.