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

rev 1862026-05-08Accelerating

Closes the named rev-185 next-sprint candidate (per-rev-shipping-week stat card on the rev-179 /changelog/cadence stats grid) at three coordinated surfaces (peak-week stat card with click-through anchor + peak-week detail block listing every rev shipped in the most-active 7-day window + per-rev deep-links into the rev-169 per-rev pages) so a procurement reviewer scanning the cadence page sees the most-active stretch of public shipping at a glance + closes the v1 parity gap on the new peak-week-rev primitive in lockstep with a new peakWeekRevs[] projection on the rev-178 GET /api/v1/changelog/cadence response so MCP hosts and AI-tooling release-roundup newsletters rendering 'the most-active week shipped N revs from rev-X to rev-Y' need only one bearer-less GET (no /changelog?since pagination, no per-day flatten) + closes two more rev-185 named radar candidates at the templates axis (independent landscape / hardscape contractors with seasonal route density + named-crew continuity + material pass-through markup discipline + weather-window scheduling + small specialty pharmacies with DEA-controlled-substance reconciliation + named-pharmacist-of-record continuity + 340B program eligibility discipline + HIPAA-bound communication discipline) — the templates cluster reaches forty-five named verticals — the OpenAPI 3.1 spec types the new peakWeekRevs[] field with full schema in lockstep — 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 96th unbroken rev — 108th unbroken cadence rev (rev 186)

Peak shipping week stat card + detail block on /changelog/cadence — closes the named rev-185 next-sprint candidateUntil rev 186 the rev-179 /changelog/cadence stats grid showed total revs / active days / avg per active day / peak day in a 6-card grid + the rev-182 trajectory verb chip — but the peak SHIPPING WEEK (the most-active 7-day stretch of public shipping in the trailing window) was invisible on the public HTML surface even though the rev-181 v1 endpoint already computed it as `peakWeek` (start + end + count). Rev 186 closes that. The stats grid gains a fifth/seventh stat card showing the peak week's rev count + start/end date range as a click-through link to a new peak-week detail block below the calendar that lists every rev shipped in that 7-day window with brand-color deep-links into the rev-169 per-rev pages. Hidden when the window has no revs (fresh-state guard) so the cadence page stays compact on quiet workspaces. Strategic significance: anchors every cadence-page reading horizon (90-day calendar from rev 179 + 4-week trajectory chip from rev 182 + peak day from rev 179 + peak week from rev 186) with a click-through to the substantive content. Procurement reviewers + customers + early adopters scrolling the cadence page now see the most-active stretch at a glance + can drill into the per-rev details without leaving the page — the load-bearing visible-velocity trust signal that pairs with the rev-179 calendar heatmap for the full descriptive (per-day calendar) → density (peak day) → trajectory (peak week) story across the public reading surface.
peakWeekRevs[] projection on GET /api/v1/changelog/cadence — closes the v1 parity gap on the rev-186 dashboard primitiveMirrors the rev-186 dashboard peak-week detail block on the protocol-bound surface in the same cycle the dashboard primitive ships (the cadence pattern from rev 37 onward continues unbroken). Until rev 186 the rev-181 `peakWeek` primitive returned start + end + count but no rev list, forcing MCP hosts and AI-tooling release-roundup newsletters to either re-query /api/v1/changelog?since=… across the week's date range or paginate the per-day cadence list and flatten the sampleRevs[] arrays. Rev 186 closes that. Each peakWeekRevs[] row carries `rev` + `date` + trimmed `title` (≤160 chars) so a caller rendering 'the most-active week shipped N revs from rev-X to rev-Y' has everything they need from one bearer-less GET. The OpenAPI 3.1 spec types the new field with full schema in lockstep — 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 96th unbroken rev with rev 186. Strategic significance: pairs the rev-181 peakWeek primitive with the per-rev detail an MCP host actually needs so the protocol-bound + public surfaces never drift on what 'peak week' means. The MCP server (Q3 #1) gains one more pre-typed surface with nothing left to design across the rev-178 v1 cadence cluster's six fields (cadence + weeklyCadence + peakDay + peakWeek + peakWeekRevs + historicalTrajectory).
Two more onboarding templates — Independent landscape / hardscape contractors + Small specialty pharmaciesCloses two more of the rev-185 named radar candidates at two more underserved verticals where regulated discipline (seasonal route economics + named-crew continuity + material pass-through markup discipline on the landscape side, DEA-controlled-substance reconciliation + named-pharmacist-of-record continuity + 340B program eligibility + HIPAA-bound communication on the specialty pharmacy side) is the load-bearing differentiator against generic AI tools. Independent landscape / hardscape contractors (owner-led residential + light-commercial landscape, hardscape, and irrigation contractors — 4 high-importance memory entries: seasonal route density discipline with named day-of-week + named drive-time targets + named per-stop revenue floor, material pass-through with named cost-plus markup + named change-order trigger + named substitution rule, named-crew continuity red flag at >2 reassignments per rolling 30-day window, weather-window red flag on installs scheduled within 48 hours of forecasted weather risk without documented re-schedule + 1 sample mid-season route-density signal). Small specialty pharmacies (independent compounding + infusion + oncology + fertility specialty pharmacies — 4 high-importance memory entries: DEA Schedule II-V controlled-substance reconciliation with named-pharmacist + named-tech double-count + named DEA Form 222 / CSOS perpetual-inventory reconciliation, named-pharmacist-of-record continuity per long-term-therapy patient with named handoff protocol, 340B program eligibility determination with named covered-entity affiliation + named outpatient setting + named auditable retention, HIPAA-bound communication red flag on unencrypted channels without consent + named risk acknowledgement + 1 sample 340B eligibility-drift signal). Two new OnboardingTemplateKey enum values (`landscape_contractor`, `specialty_pharmacy`) extend the rev-19 enum without migration. The templates cluster is now forty-five named verticals deep — closes the day-1 starvation-point story across two more underserved owner-led segments where regulated discipline (DEA + 340B + HIPAA on the specialty pharmacy side; seasonal route economics + material markup + weather windows on the landscape side) is the load-bearing differentiator against generic AI tools that don't know the regulatory or operational vocabulary.
Cumulative visual polish — tactile hover lift on cadence stat cards + focus-visible accessibility ring + 14 new SEO keywords + radar copy refreshCumulative micro-polish (every rev 22+ has carried at least one). The rev-179 cadence stat cards now lift 1px on hover with a soft brand-color box-shadow so the stats grid feels reactive rather than static — pairs with the rev-186 peak-week link affordance which surfaces an inline brand-color underline on hover so the click-through reads as discoverable. New `:focus-visible` outline ring on every interactive cadence-page element (peak-week link, calendar cells with revs, peak-week detail rev rows) so keyboard-only readers land cleanly across the public marketing surface — matches the rev-38 dashboard accessibility pattern. Plus the rev-186 templates copy refresh — 'forty-five verticals today' replaces 'forty-three' across hero + metadata title + OpenGraph + Twitter description + JSON-LD CollectionPage block + radar copy refresh names the next vertical wave (independent franchise restaurants with multi-unit operators + small-batch artisan bakeries + independent occupational therapy / speech therapy practices + small specialty trades like electricians + plumbers) now that landscape + specialty pharmacy are shipped. Fourteen new SEO keywords for the landscape + specialty pharmacy axes.