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

rev 1992026-05-09Cooling

Closes two more named radar candidates at the templates axis (small independent jewellers with named-craftsman continuity + custom-order milestone cadence + appraisal + insurance documentation hygiene + chain-of-custody on every piece in for repair, and independent specialty bike shops with named-mechanic continuity + service-record continuity per named bike + seasonal inventory turn + safety-incident hygiene with named-component quarantine on any post-service incident) bringing the templates cluster to seventy-one named verticals — the rev-198 next-radar wave queued small independent jewellers + independent specialty bike shops at the top of the queue, and rev 199 ships them at the cheapest possible shape on top of the existing rev-19 ONBOARDING_TEMPLATES array. Plus opens the sixth read shape on the templates v1 cluster — recently-shipped convenience read at /api/v1/onboarding-templates/recent — so MCP hosts rendering a 'what's new on the templates surface' widget don't have to fetch the rev-172 full listing endpoint and sort the rows client-side by launchDate. Mirrors the rev-175 /api/v1/changelog/latest convenience pattern at the templates axis. The OpenAPI 3.1 spec count copy bumps 69 → 71 across the rev-172 listing endpoint description in lockstep + the new convenience endpoint is fully typed 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 107th unbroken rev with rev 199. Plus radar copy refresh on the templates 'Don't see your vertical?' CTA names the next vertical wave (independent toy / hobby shops + framing / mat-board ateliers + independent specialty fishing / outdoor outfitters + independent bookbinders / paper conservators) now that jewellers + bike shops are shipped. Plus 12 new SEO keywords cover the jeweller + bike-shop axes. Plus subtle visual polish on the rev-196 Recently-added strip cards: the rev-197 per-card category badge now brightens on parent-link hover so the chip feels like part of the same surface in motion (rev 199)

Two more onboarding templates — small independent jewellers + independent specialty bike shopsCloses the named rev-198 next-radar wave at two more underserved owner-led retail segments where the named-craftsman + named-mechanic relationship is the load-bearing differentiator against generic chain retail. Small independent jewellers (4 high-importance memory entries: named-craftsman continuity with named-primary + named-backup on every commission + sub-policy on bench substitutions, custom-order milestone cadence with named touchpoints at design + wax + cast + set + final review + named customer-comm at every milestone, appraisal + insurance documentation hygiene on every named piece over $2K with named-replacement-value + named-stone-grading + named-photographer record + 24-hour delivery threshold, chain-of-custody on every piece in for repair / resize / restoration with named-condition-report + named-photographs + named-workbench-handoff + named-pickup-signoff + 1 sample mid-commission stone-availability signal). Independent specialty bike shops (4 high-importance memory entries: named-mechanic continuity with named-primary + named-backup on every multi-day service + sub-policy on quick-fix substitutions, service-record continuity per named bike with named-mechanic + named-finding + named-replacement + named-recommendation + named-deferred-work, seasonal inventory turn with named-buyer ordering window in November-January + end-of-season liquidation cadence in September-December, safety-incident hygiene with named-component quarantine on any post-service incident + 3-in-90-days pattern threshold for named-component-line review + 1 sample mid-season post-service brake incident pattern signal). Two new OnboardingTemplateKey enum values (indie_jeweller, specialty_bike_shop) extend the rev-19 enum without migration. The templates cluster is now seventy-one named verticals deep. Strategic significance: closes the named rev-198 next-radar wave (the rev-198 running state explicitly named both as the top of the queue). Both verticals map cleanly onto Loop Desk's approval-first vocabulary — jewellers lean on named-craftsman continuity + chain-of-custody + appraisal documentation discipline (high-trust, high-value), bike shops lean on named-mechanic continuity + service-record continuity + safety-incident pattern detection (regulated equipment, named-relationship retention).
GET /api/v1/onboarding-templates/recent — sixth read shape on the templates v1 clusterUntil rev 199 MCP hosts and AI tooling roundup newsletters rendering 'what's new on the templates surface' had to fetch the rev-172 full listing endpoint and sort the rows client-side by launchDate. Rev 199 makes the answer a one-call bearer-less GET. Returns the N most-recently-shipped templates (default 4, max 20) sorted descending by launch date with enum order as a deterministic tiebreak — so two templates launched on the same date render in the order they appear in ONBOARDING_TEMPLATES. Each row carries key + name + description + keywordHint + category + categoryLabel + memoryCount + signalCount + url + apiUrl + launchRev + launchDate. Mirrors the rev-175 /api/v1/changelog/latest convenience pattern at the templates axis on the protocol-bound side, and the rev-196 dashboard 'Recently added' featured strip at the human-readable axis. Pure derived state from the rev-176 TEMPLATE_LAUNCH metadata map — no schema cost, no migration. Strategic significance: closes the sixth read shape on the templates v1 cluster (full listing rev 172 + per-template detail rev 189 + per-category drill-down rev 190 + standalone-taxonomy rev 192 + keyword search rev 193 + aggregate stats rev 194 + recent rev 199). Pairs with /api/v1/changelog/latest (rev 175) + /api/v1/changelog/peak-week (rev 187) as the third single-record convenience endpoint on the public marketing surface — same pattern, three surfaces, one consistent vocabulary. Cache-control public, max-age=300, s-maxage=1800.
Templates page count + radar copy refresh + SEO keywords + OpenAPI typed coverage + cumulative visual polishTemplates page count copy bumps 69 → 71 across hero, metadata title, OpenGraph + Twitter description, JSON-LD CollectionPage block, and templates-cta. Two new keyword hints on the per-vertical chip line (small independent jewellers `Named-craftsman continuity · custom-order milestone cadence · appraisal hygiene · insurance documentation`; independent specialty bike shops `Named-mechanic continuity · service-record continuity · seasonal inventory turn · safety-incident hygiene`). Twelve new SEO keywords on the templates metadata covering jeweller + bike-shop axes (AI for jewellers + AI for independent jewellers + AI for jewellery shops + AI for watchmakers + AI for custom-jewellery commissions + AI for named-craftsman continuity + AI for appraisal documentation + AI for bike shops + AI for independent bike shops + AI for cycling retail + AI for bicycle service centres + AI for named-mechanic continuity + AI for service-record continuity). 'Don't see your vertical?' next-radar list refreshes — replaced with independent toy / hobby shops, framing / mat-board ateliers adjacent to the rev-193 picture-framing axis, independent specialty fishing / outdoor outfitters, and independent bookbinders / paper conservators now that jewellers + bike shops are shipped. The OpenAPI 3.1 spec types the new /onboarding-templates/recent endpoint with full request/response schemas (limit query param 1-20 default 4 + response shape with templates[] each carrying key + name + description + keywordHint + category + categoryLabel + memoryCount + signalCount + url + apiUrl + launchRev + launchDate) — 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 107th unbroken rev with rev 199. Plus subtle visual polish on the rev-196 Recently-added strip cards: the rev-197 per-card category badge below each strip card name now brightens on parent-link hover (`rgba(31,143,137,0.08) → 0.18` background + matching border-color emphasis) so the chip reads as part of the same surface in motion vocabulary, mirroring the rev-193 per-template card hover treatment at the strip-card axis. Cumulative micro-polish — every rev 22+ has carried at least one — and rev 199's polish is load-bearing because the rev-196 + rev-197 strip surfaces had accumulated five distinct visual elements (rev label + date + name + category badge + keyword-hint + stats line + CTA) without a unified hover treatment until rev 199.