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

rev 1832026-05-08Accelerating

Closes the named rev-182 next-sprint candidate (dashboard cadence trend mini-chip on the rev-12 heartbeat indicator) — new CadenceTrendChip mounts beside the rev-12 LoopHeartbeat in the dashboard status bar showing the 'Accelerating / Steady / Cooling' verb the rev-182 /changelog/cadence stats rollup already names so logged-in operators see Loop Desk's trajectory verb at the morning-glance axis without scrolling to the rev-181 dashboard ShippingCadencePill sparkline + new GET /api/v1/changelog/trend endpoint mirrors the rev-182 trajectory verb on the protocol-bound surface so MCP hosts inherit the same one-beat answer + closes two more rev-182 named radar candidates at the templates axis (independent home-inspection practices with reporting-cadence + scope-of-practice + insurance-disclosure discipline + owner-led commercial cleaning operators with route-density + named-supervisor + chemical-substitution discipline) — the templates cluster reaches thirty-nine named verticals + extracted shared computeShippingTrajectory() helper from changelog-releases.ts so the dashboard chip + cadence page + v1 endpoint all read from one canonical computation — 105th unbroken cadence rev (rev 183)

Cadence trend verb chip beside the rev-12 heartbeat indicatorCloses the named rev-182 next-sprint candidate. Until rev 183 the rev-181 dashboard ShippingCadencePill carried the 4-bar sparkline but operators reading the dashboard status bar at a glance had to count bars to know whether the cadence was accelerating, steady, or cooling — the verb chip the rev-182 /changelog/cadence stats rollup names lived only on the public marketing surface. Rev 183 closes that gap. New CadenceTrendChip client component mounts directly beside the rev-12 LoopHeartbeat indicator in the dashboard status bar, surfacing the rev-182 verb (Accelerating / Steady / Cooling) plus a tiny ↑/→/↓ glyph so the eye lands on the trajectory verb at the morning-glance axis. Brand-green palette when accelerating + amber when cooling so the verb pops at three distinct attention levels (matches the rev-21 cost-cap warning amber + rev-37 task.unblocked brand-green visual vocabulary). Hidden on quiet workspaces (every bucket zero) so fresh-state weeks don't see clutter. Pure derived state — reuses the rev-183 shared computeShippingTrajectory() helper so the dashboard chip + the rev-182 /changelog/cadence stats rollup verb chip + the rev-183 v1 trend endpoint never drift on what 'this week vs three weeks ago' means. Pairs with rev-12 heartbeat (is MY desk alive?) + rev-180 ShippingCadencePill (is the PRODUCT alive at a glance?) + rev-183 CadenceTrendChip (is the PRODUCT cadence accelerating or cooling?) as the now-three-instrument cadence cluster on the dashboard status bar, with the rev-12 heartbeat answering operator-state, the rev-180 pill answering product-pulse, and the rev-183 chip answering product-trajectory.
GET /api/v1/changelog/trend endpointMirrors the rev-183 dashboard primitive on the protocol-bound surface in the same cycle the dashboard primitive ships (the cadence pattern from rev 37 onwards continues unbroken through rev 183). MCP hosts polling for 'is Loop Desk's cadence accelerating?' on a 'Loop Desk product status' widget no longer need to fetch /api/v1/changelog/cadence + re-bucket the per-day list + diff the latest two weeks client-side — one bearer-less GET answers the question. Returns the trajectory verb (label: 'Accelerating' | 'Steady' | 'Cooling' | '—') plus the latest + prior + delta integers + the 4-week buckets oldest→newest so callers rendering 'Accelerating · +2 vs prior week' have everything they need. No auth — public marketing surface (same model as /api/v1/changelog/cadence rev 178, /api/v1/changelog/latest rev 175, /api/v1/badge.svg rev 19). Cache-control public, max-age=300, s-maxage=1800. The OpenAPI 3.1 spec types the new endpoint with full response 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 93rd unbroken rev with rev 183. Strategic significance: pairs with /api/v1/changelog/cadence (rev 178 — full per-day shape) + /api/v1/changelog/latest (rev 175 — convenience read) as the third low-resolution sibling to the high-resolution cadence read. The MCP server (Q3 #1) gains one more pre-typed surface with nothing left to design across the changelog-cadence cluster at any read shape.
Two more onboarding templates — Independent home-inspection + Owner-led commercial cleaningCloses two more of the rev-182 named radar candidates at two more underserved verticals where operational discipline is the load-bearing differentiator. Independent home-inspection practices (solo + small-team home inspectors — 4 high-importance memory entries: 24-hour structured-report turnaround cadence with named-inspector signature + photo-documented findings + summary risk tiers, scope-of-practice red flag on any narrative claim outside InterNACHI/ASHI standards-of-practice + same-day referral to specialist (electrical / structural / mold), insurance-disclosure discipline with E&O carrier + named-policy-number + state license number on every report cover, recall-rate red flag at >2% findings-disputed-by-buyer-agent rolling 90-day rate + 1 sample buyer-agent dispute signal). Owner-led commercial cleaning (independent commercial cleaning operators running janitorial + post-construction + specialty contracts — 4 high-importance memory entries: route-density discipline with named-supervisor + per-stop time-on-site + named scope-of-work checklist on every recurring contract, chemical-substitution rule on any client request that crosses Green Seal / EPA Safer Choice boundary requiring written substitution sign-off, named-customer concentration red flag at >35% single-account of 12-month revenue, supervisor-turnover red flag at any quarterly turnover >15% rolling 90-day + 1 sample after-hours emergency callout signal). Two new OnboardingTemplateKey enum values (home_inspection, commercial_cleaning) extend the rev-19 enum without migration. The templates cluster is now thirty-nine named verticals deep — closes the day-1 starvation-point story across two more underserved owner-led segments where regulated operational discipline (InterNACHI standards on the inspection side, Green Seal / EPA Safer Choice + supervisor-turnover discipline on the commercial cleaning side) is the load-bearing differentiator against generic AI tools.
Cumulative visual polish + 8 new SEO keywords + radar copy refreshCumulative micro-polish (every rev 22+ has carried at least one). The new rev-183 CadenceTrendChip wears a tri-state palette (brand-green Accelerating / neutral Steady / amber Cooling) so the verb pops at three distinct attention levels and the chip never competes with the rev-180 ShippingCadencePill (brand-color teal) or the rev-12 heartbeat indicator (brand-color pulsing dot). Tactile hover lift + tooltip naming the per-week numbers gives the chip a click-affordance even though it's a passive read. Plus the rev-183 templates copy refresh — 'thirty-nine verticals today' replaces 'thirty-seven' across hero + metadata + JSON-LD CollectionPage block + radar copy refresh names the next vertical wave (independent funeral homes + small marine / aviation services + owner-led residential property managers + independent boutique consultancies) now that home-inspection + commercial-cleaning are shipped. Eight new SEO keywords for the home-inspection + commercial-cleaning axes.