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

rev 432026-04-30

Per-task input transparency, memory copy, JSON-export source evidence, v1 workspace summary

Per-task input transparency on every active-work card (close named rev-42 follow-up)Rev 42's running state explicitly named 'per-task input transparency' as the next-sprint candidate to close the load-bearing rev-41 transparency loop on the task surface. Rev 41 made input transparency visible on every artifact (post-cycle); rev 43 closes the loop on the task (pre-cycle / in-flight). New 'N source signals' chip mounts on every active-work card with at least one source signal; one tap expands a panel listing the signals that shaped this work item (kind, priority, title, detail, source link). Lazy-fetched via the new GET /api/tasks/{id}/sources route. Reads from the existing rev-1 task.sourceSignalIds JSONB column (no migration). Operators debugging 'why is the AI heading this direction' no longer have to wait for an artifact to land — the queue itself answers the input question. Pairs with rev-12 work log (what the AI did) + rev-40 timeline (when it did it) + rev-41 artifact sources (what shaped the output) for the full per-task transparency story before, during, and after the cycle.
Markdown copy chip on every memory entryRev 42 shipped one-tap markdown copy on every artifact for the 'paste a brief into Notion / Slack / Linear' workflow. Rev 43 mirrors the same primitive on memory entries — operators paste durable knowledge into wikis / one-pagers / customer-onboarding docs just as often as outputs, and the rev-26 promote-to-memory flow only handles the output → memory direction (not memory → external doc). New MemoryCopyButton mounts alongside the existing edit / pin / delete chips on every memory row, available to all members including viewers (copy is read-only). Assembles a small markdown package: title (H3), kind + importance meta line, content body. Fallback execCommand path for older browsers and non-secure contexts. Pairs with rev-21 memory tags + rev-34 memory bulk operations + rev-33 memory reactions for the complete read/teach/curate/lift-out memory surface.
Resolved source-evidence appendix in workspace JSON export (close named rev-42 follow-up)Rev 42's running state named 'input transparency on the artifact JSON export' as a next-sprint candidate. The rev-41 columns sourceSignalIds + sourceMemoryIds rode every artifact row in the export from rev 41 onwards as ID arrays, and the export had always carried signals + memory as their own arrays — but a procurement reviewer cross-referencing the input set had to write a join. Rev 43 makes it one read: a new top-level sourceEvidence appendix maps artifactId → { signals: [{ id, kind, priority, title }], memory: [{ id, kind, importance, title }] } for every artifact with at least one source. The export bumps to exportVersion 2 (forward-compatible with the rev-40 import). Procurement teams reviewing AI tool exposure under ISO 42001 / SOC 2 frameworks can answer 'which inputs shaped this brief' without parsing the workspace's full signal + memory arrays.
GET /api/v1/workspace/summary (close rev-42 v1 parity)Rev 42 shipped the procurement-friendly workspace summary panel (signals, artifacts by status, memory, sources by status, tasks by status, cycles, approved artifacts, anchor timestamps) as a dashboard-only surface. Rev 43 mirrors it on the v1 surface as a single bearer-auth call. MCP hosts can now answer 'how big is this workspace' for an MCP-driven procurement-evidence tool without enumerating every entity. Pairs with the rev-13 /api/v1/runs (cycle history) + rev-18 /api/v1/stats (7-day health) + rev-20 /api/v1/activity (audit trail) as the four-axis 'how is this desk doing' instrument cluster on the protocol-bound surface.
GET /api/v1/tasks/{id}/sources (v1 mirror of rev-43 dashboard endpoint)Mirrors the new rev-43 dashboard per-task input transparency endpoint on the v1 surface. MCP hosts driving the desk can render the same 'N source signals' transparency surface in their own UIs — same vocabulary, same shape — without bridge code. Closes the v1-vs-dashboard parity loop in the same rev that the dashboard primitive lands, matching the rev-37 / rev-40 / rev-41 cadence pattern.