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

rev 1752026-05-08Accelerating

Two more industry onboarding templates (Small construction / general contracting + Dental / orthodontic clinics) + new GET /api/v1/changelog/latest convenience endpoint closes the third axis on the v1 changelog read surface (listing rev 100/101 + per-rev detail rev 174 + latest rev 175) + per-template share-affordance chip (🔗 Copy link) on every /templates/[key] detail page mirroring the rev-174 changelog detail share chip + BreadcrumbList JSON-LD on every /changelog/[rev] AND /templates/[key] page so Google search snippets show breadcrumb trails (Loop Desk › Changelog › rev N and Loop Desk › Templates › [vertical name]) — closes both rev-174 next-sprint candidates (further industry templates AND share-affordance vocabulary unification) at two more underserved verticals where the procurement-conscious buyer's 'will it know my industry on day 1?' question is loudest + opens the convenience axis on the changelog v1 cluster + closes the share-chip symmetry on every public marketing detail surface (changelog detail + template detail) + closes the breadcrumb-axis SEO gap on every per-entity public surface — 97th unbroken cadence rev (rev 175)

Two more onboarding templates — Small construction / general contracting + Dental / orthodontic clinicsCloses the named rev-174 next-sprint candidate at two more underserved SMB segments. Small construction / general contracting (owner-led general contractors, design-build studios, residential and small-commercial trades — 4 high-importance memory entries: change-order discipline (signed dollar + schedule delta on every change before work starts), named-subcontractor weekly schedules (every line item names the responsible sub-trade company), 3-day weather-block schedule re-baselining rule, statutory-window preliminary lien notice compliance + 1 sample homeowner change-order pushback signal). Dental / orthodontic clinics (independent dental practices, orthodontic clinics, oral-surgery practices — 4 high-importance memory entries: provider-attributed itemised treatment plans with insurance allowable + patient responsibility broken out separately, 7-day post-due recall cadence rule for active patients, 8% rolling-90-day claim denial rate red flag, state-board patient records retention compliance + 1 sample treatment plan deferral with cost concern signal). Two new OnboardingTemplateKey enum values (small_construction, dental_clinic) extend the rev-19 enum without migration. The templates cluster is now twenty-five named verticals deep — closes the day-1 starvation-point story across two more underserved owner-led segments where regulated discipline (lien-rights filings on the construction side, records-retention compliance on the dental side) is the load-bearing differentiator against generic AI tools.
GET /api/v1/changelog/latest — convenience endpointCloses the third axis on the changelog read surface (listing rev 100/101 + per-rev detail rev 174 + latest rev 175). MCP hosts polling for 'what shipped most recently' on a 'What's new on Loop Desk' widget no longer need to call /api/v1/changelog?limit=1 + parse the array — one bearer-less GET answers the question. Same response shape as /api/v1/changelog/{rev} so callers can swap one URL for the other with no code changes. neighbors.newer is always null (latest is the newest by definition); neighbors.older points at the second-most-recent release for chronological back-navigation. No auth — public marketing surface (same model as /api/v1/changelog, /api/v1/badge.svg, /api/v1/roadmap-items). Cache-control public, max-age=300, s-maxage=1800. The OpenAPI 3.1 spec types the new endpoint with full response schema + 404 error path 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 90th unbroken rev with rev 175.
Per-template 🔗 Copy link share chip on every /templates/[key] pageCloses the share-chip symmetry on every public marketing detail surface (rev-174 changelog detail share chip → rev-175 template detail share chip). Procurement reviewers sharing a per-vertical Loop Desk template URL with stakeholders ('here's exactly what we'd seed our workspace with on day 1') get the same one-tap copy chip the per-rev changelog page added in rev 174. Pure client-side via navigator.clipboard.writeText with the standard execCommand fallback for non-secure contexts (matches the rev-42/43/101/125/126/128/133/174 chip-copy pattern that has run since rev 42). Brand-color teal idle, brand-green is-copied success state + 1.6s pulse animation matches the rev-101 changelog permalink + rev-125 roadmap permalink + rev-126 roadmap-filter share chip + rev-174 changelog detail share chip vocabulary so all the dashboard's share-affordances ring out with one consistent visual story across every public surface. Strategic significance: the share-affordance vocabulary across every public read surface (changelog index permalink rev 101 + per-rev permalink rev 174 + roadmap permalink rev 125 + roadmap-phase permalink rev 126 + per-template detail page rev 169 + per-template share chip rev 175 + blog post share chip rev 102 + blog heading anchor rev 102) is now uniform — every detail surface a procurement reviewer might land on has the same one-tap deliver path.
BreadcrumbList JSON-LD on every /changelog/[rev] AND /templates/[key] pageCloses the breadcrumb-axis SEO gap on every per-entity public surface. Until rev 175 the rev-174 TechArticle markup on /changelog/[rev] + the rev-171 FAQPage markup on /templates/[key] gave Google rich content metadata but no breadcrumb trail — search snippets showed only the canonical URL, not the navigation context. Rev 175 adds BreadcrumbList JSON-LD on both surfaces so Google search snippets can show 'Loop Desk › Changelog › rev N' or 'Loop Desk › Templates › [vertical name]' instead of a bare URL. Pure server-rendered <script type=application/ld+json> blocks generated at request time from the existing release/template data — zero runtime cost, zero schema cost. Procurement reviewers + AI tooling discovery systems consuming schema.org markup get richer search-result context, and the breadcrumb trail signals the page's place in the site hierarchy more clearly than the URL alone. Strategic significance: every public marketing detail surface now ships full structured data — TechArticle + BreadcrumbList on changelog detail (rev 174 + rev 175), FAQPage + BreadcrumbList on template detail (rev 171 + rev 175), Article on blog post (rev 103), CollectionPage + ItemList on templates index (rev 170) and integrations (rev 170), Organization + WebSite + SoftwareApplication on landing (rev 171), per-author archive markup (rev 105 + rev 171). The breadcrumb axis is the last common-pattern structured-data primitive that hadn't shipped uniformly across the public marketing surfaces; rev 175 closes it.