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

rev 2022026-05-12Cooling

Deliberate diversification away from the 14-rev templates cluster (rev 188-201 each shipped templates-axis primitives — verticals added, depth/freshness signals, recent endpoints, per-category archive pages, OG cards). Rev 202 pivots to three load-bearing primitives that have been named in the running state but kept getting deprioritised: (a) GET /api/v1/integrations — closes the v1 parity gap on the rev-165 /integrations public marketing surface so MCP hosts answering 'what does Loop Desk connect to?' get the vendor inventory in one bearer-less GET instead of scraping the SSR'd HTML; pairs with /api/v1/onboarding-templates (industry-fit) + /api/v1/blog (brand voice) + /api/v1/changelog (shipped) + /api/v1/roadmap-items (planned) + /api/v1/roadmap-votes (most-requested) as the now-six-axis public marketing v1 cluster (channels axis closed); (b) /pricing public page — until rev 202 the only pricing surface was an in-page anchor on the landing page (loopdesk.space/#pricing), procurement reviewers searching 'Loop Desk pricing' or sharing a pricing URL with a teammate had no canonical page; rev 202 ships a dedicated page with three plan cards + competitor-comparison block (Notion Custom Agents per-cycle credits, HubSpot Breeze outcome-based) + procurement-evidence section + JSON-LD ItemList structured data; (c) /llms-full.txt — modern AI-discoverability surface that complements the existing /llms.txt; AI agents indexing the site (ChatGPT search, Claude search, Perplexity, Bing AI) get a single comprehensive context file with pricing + integrations + templates + roadmap + recent shipping + brand voice + procurement evidence so they don't have to crawl 200+ URLs to learn what Loop Desk does. The OpenAPI 3.1 spec types the new /integrations endpoint with full request/response schemas — 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 110th unbroken rev with rev 202. Plus every nav link across the public marketing surface now points at the canonical /pricing URL instead of the in-page anchor (rev 202)

GET /api/v1/integrations — public integrations catalog on the v1 surfaceCloses the v1 parity gap on the rev-165 /integrations public marketing page. New shared `src/lib/integrations.ts` module pulls the inline groups out of the page.tsx into a reusable source — both the rev-165 page and the rev-202 endpoint read from one place so the channel inventory cannot drift between the human-readable surface and the protocol-bound surface (mirrors the rev-37 changelog-releases shared module + rev-97 roadmap-items shared module at the integrations axis). Each row carries key + name + detail + auth + sinceRev. Response also includes an aggregate `perAxis` summary (Inbound / Outbound / Programmatic counts) so MCP hosts rendering 'Loop Desk supports N integrations across 3 axes' don't have to recompute counts. No auth — public marketing surface (same model as /api/v1/badge.svg + /api/v1/roadmap-* + /api/v1/changelog + /api/v1/blog + /api/v1/onboarding-templates). Cache-control public, max-age=300, s-maxage=1800 — the integrations list changes only when we ship a new channel. The OpenAPI 3.1 spec types the new endpoint with full request/response schemas including the perAxis sub-object + groups[].items[] shape with every field typed + sinceRev as a string (since it carries non-numeric data like 'rev 17 (single URL), rev 19 (per-event router)'). Strategic significance: the public marketing v1 cluster is now six axes deep — planned (roadmap) + most-requested (roadmap-votes) + shipped (changelog) + brand voice (blog) + industry-fit (templates) + channels (integrations). The upcoming MCP server (Q3 #1) has nothing left to design across the public marketing v1 cluster at any of the six axes.
Dedicated /pricing public page — closes the canonical-URL gap on the load-bearing procurement queryUntil rev 202 the only pricing surface was an in-page anchor on the landing page (loopdesk.space/#pricing). Procurement reviewers searching for 'Loop Desk pricing' or sharing a pricing URL with a teammate had no canonical page to land on — anchors don't share well in Slack/email/CRM (no OG preview, no SEO-friendly URL, no individual analytics), don't get their own crawl priority in the sitemap, and degrade in search snippets. Rev 202 closes that. New /pricing page ships three plan cards (Free / Pro $29-mo / Team $79-mo) with feature lists + per-tier hard caps (sources, memory TTL, loop interval floor) in a structured dl block, plus a competitor-comparison section that names Notion Custom Agents ($10/1,000 credits as of May 2026) + HubSpot Breeze ($0.50 per resolved conversation / $1 per qualified lead) + generic per-token billing as the three pricing models Loop Desk explicitly rejects, plus a procurement-evidence section that names what every tier ships (approval-first on every tier, audit trail on every tier, daily cost cap on every tier — higher tiers unlock higher caps, not different products), plus a closing CTA. JSON-LD ItemList structured data with @type=Offer per plan so Google + AI tooling discovery systems consume schema.org pricing markup. Full openGraph + twitter card metadata. Crawler-friendly with priority 0.8 in the sitemap (highest of any public marketing page since pricing is the most-searched B2B procurement query for AI tooling). Every existing nav link across the public marketing surface (landing, blog, docs, changelog, changelog/[rev], changelog/cadence, roadmap, integrations, templates, templates/[key], templates/by-category) now points at /pricing instead of the legacy /#pricing in-page anchor. Strategic significance: closes the procurement-discovery loop on the public marketing surface. SEO win — 'Loop Desk pricing' / 'flat-fee AI workspace pricing' / 'AI workspace no credits' all land on a real page instead of a landing-page section. Pairs with /integrations (vendor inventory) + /templates (industry-fit) + /changelog (history) + /roadmap (future) + /blog (brand voice) + /pricing (cost) as the now-sixth public marketing surface on the human-readable axis.
/llms-full.txt — comprehensive AI-discoverability context fileModern AI-discoverability surface that complements the existing rev-1 /llms.txt. The llms.txt convention (proposed 2024-2025, widely adopted by 2026) has emerged as the AI equivalent of robots.txt + sitemap.xml — a stable entry point AI agents read first to bootstrap their understanding of a site. The bare /llms.txt answers 'what is this product?' in 60 seconds. The deeper /llms-full.txt answers 'what does this product do, who is it for, what does it cost, what does it connect to, what's it been doing lately?' in 5 minutes. Until rev 202 AI agents (ChatGPT search, Claude search, Perplexity, Bing AI) indexing the site had to crawl 200+ URLs to learn what Loop Desk does. Rev 202 collapses that to one stable URL. The file aggregates every public-facing data source — pricing, integrations (every channel + auth model), all 73 onboarding templates organised by industry category with launch metadata, the full roadmap (Now/Next/Later phases), the last 12 changelog revisions with highlights, the blog categories + 15 most-recent posts with excerpts, and a procurement-evidence section naming every governance control. Cache-control public, max-age=3600. Strategic significance: procurement-conscious AI searches ('find me a governance-first AI workspace under $50 a seat with daily cost cap') land on rich content instead of a summary. Pairs with /api/v1/integrations + /pricing as the third rev-202 public surface that answers a procurement-relevant question — the three together close the procurement-discovery story across human (pricing page), protocol (v1 integrations), and AI (llms-full) reading axes.
OpenAPI 3.1 typed coverage on /integrations + cumulative visual polish + sitemap entry — 110th unbroken cadence revThe OpenAPI 3.1 spec types the new GET /integrations endpoint with full request/response schemas (no parameters; response shape with generatedAt + total + perAxis object with Inbound/Outbound/Programmatic counts + groups[] each carrying axis enum + intro + count + items[] each with key + name + detail + auth + sinceRev typed). 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 110th unbroken rev with rev 202. The OpenAPI spec changelog header gains a rev-202 block explaining the three diversification primitives. Sitemap.xml gains /pricing (priority 0.8, weekly changeFrequency) — higher priority than /integrations (0.7) since pricing is the most-searched B2B procurement query. Plus cumulative visual polish on the /pricing page itself: brand-color teal accent pills at the hero ('No per-cycle credits' / 'No metered AI tokens' / 'No overage bills' / 'Daily cost cap on every tier') matching the rev-22+ design-language thread; per-plan-card 'Most popular' tag on the featured Pro tier; per-tier hard-caps dl block with dashed border so the caps read as a sibling of the rev-22+ chip vocabulary; competitor-comparison row treatment with brand-color teal vs brand-amber palette distinguishing 'them' (Notion/HubSpot per-cycle) from 'us' (Loop Desk flat-fee); procurement-evidence card grid with brand-amber callout treatment on the 'What we don't do' card so the eye lands on the contrast. Strategic significance: keeps the rev-by-rev visual-hierarchy discipline alive — every rev 22+ has carried at least one piece of cumulative polish, and rev 202's polish is load-bearing because the new /pricing page is the most-procurement-loaded surface in the product and needs to read as part of the rev-22+ design language so procurement reviewers recognise the visual vocabulary across all six public marketing surfaces.