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

rev 422026-04-30

Share-page input transparency, markdown copy on artifacts, search entity scoping, workspace at-a-glance

AI input transparency on /share/{token} (close named rev-41 follow-up)Rev 41 introduced the artifact source-evidence primitive for the operator-facing dashboard. The rev-41 running state explicitly named 'input transparency on /share/{token}' as the next-sprint candidate to close the procurement evidence loop for stakeholders reading shared briefs. Rev 42 ships it. Every shared output now carries a procurement-friendly 'Based on N signals + M memory entries' panel with per-kind chip breakdown (e.g. 'feedback · 3 · competitor · 2'), rendered server-side from the same sourceSignalIds + sourceMemoryIds columns. Tuned for external readers — count-and-kind-only, no signal detail bodies or source URLs that might leak internal context. Reviewers viewing a brief through a public link get the same evidence trail SOC 2 / ISO 42001 procurement teams ask the operator for, without the operator having to copy-paste evidence into a separate doc.
One-tap markdown copy on every artifact (and on /share/{token})New ArtifactCopyButton mounts alongside the rev-15 share / rev-23 inline edit / rev-26 promote / rev-31 push-to-Slack chips on every approval-queue artifact + the latest brief panel + the public share page. One tap copies a clean markdown package to the clipboard: title (#), summary (italics), body, and source URL list. Operators routinely paste briefs into Notion / email / Slack / Linear and were copying by hand. Power-user QoL — pairs with the rev-23 inline body editor: edit in-place, then copy out. The fallback execCommand path covers older browsers and non-secure contexts.
Search entity-type scoping chipsWorkspaceSearch already covered six entities (signals, tasks, outputs, memory, comments, activity) with rev-17 cross-entity search + rev-18 saved searches + rev-20 keyboard navigation + rev-29 activity-log inclusion. Rev 42 adds the missing scoping primitive: a chip row above the result groups lets operators narrow the visible matches to specific entity types without re-typing the query. Each chip shows the unfiltered count for that kind so the operator knows what's being hidden. Pairs with rev-18 saved searches as the workspace-search QoL trio (cross-entity + bookmark + scope).
Workspace at-a-glance procurement panelNew 'Procurement-ready summary' panel mounts above the integrations panel showing all-time totals across the five core entities (signals captured, outputs produced with by-status breakdown, memory entries, sources connected with by-status, tasks lifetime with by-status), total cycles, approval rate, plus first-cycle-date / last-cycle-date / workspace-created-date. Pure derived state via one parallel Promise.all of Postgres count queries. Companion to the rev-6 JSON export + rev-7 activity CSV + rev-22 outputs CSV (the procurement evidence trio): where those are takeaway artefacts an owner sends to a procurement reviewer, this is the single-screen instrument cluster the owner shows the reviewer in real time. The shape mirrors the SOC 2 / ISO 42001 reviewer's natural axes so the read top-to-bottom matches the questionnaire shape.
MCP and the Protocol-Bound Future of Business AI (announcement post)Rev-37/38/39/40/41 running states all named 'MCP server announcement post' as the dedicated marketing piece pending the actual MCP server launch. Rev 42 publishes the precursor: a public blog post explaining what MCP is, why protocol-bound AI workspaces matter for buyers evaluating governance-first tools, and the v1 surface state of completion that makes the upcoming MCP server exclusively protocol-translation work. SEO surface area for 'MCP business workspace' / 'Loop Desk MCP' — the named buyer-facing terms on the protocol-bound side of the line.