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

rev 622026-04-30

Per-source chronic-spike auto-pause, per-assignee cost-spike alarm, cost CSV v1

Per-source chronic-spike auto-pause (closes rev-61 named candidate)New `workspace.sourceChronicSpikeAction` ('none' | 'pause') + `sourceChronicSpikeThresholdDays` (2-14, default 3) columns. When set to 'pause', the rev-62 daily sweep auto-pauses sources whose rev-61 `consecutiveSpikeDays` crosses the threshold. The auto-action variant of the rev-61 chronic-spike recommendation banner — pairs with the rev-49 stale-task auto-archive opt-in pattern at the per-source axis on the *defensive* side rather than the *nudge* side. New Slack push + outbound `source.chronic_auto_paused` event fire on every sweep. New admin-only dashboard route + integrations panel UI + bearer-auth `/api/v1/workspace/source-chronic-spike-config`. Banner copy adapts when auto-pause is on ('these will be paused at threshold N') and warns when feeds are 1 day from auto-action so operators see what's coming tomorrow.
Per-assignee cost-spike alarm (closes alarm-cluster fourth axis)New `detectAssigneeCostSpikes()` helper aggregates the rev-54 `task.dailyCostHistory` by `task.assignedToUserId` to surface assignees whose today queue-cost is >= 2× their trailing 7-day daily average AND >= $0.50 absolute. Closes the alarm cluster's fourth axis (workspace rev 32 / per-task rev 55 / per-source rev 58 / per-assignee rev 62). New daily Slack push via `buildAssigneeCostSpikeSlackPayload()` + new `assignee.cost_spike` outbound event + new bearer-auth `GET /api/v1/cost/by-assignee/spikes` endpoint. New inline ⚡ pill on every spiking row of the rev-52 CostByAssigneePanel — same visual vocabulary as the rev-58 source pill so the alarm cluster reads with one consistent shape across all four axes. Operators answering 'whose queue is anomalously expensive today?' no longer have to compute it mentally.
Cost summary CSV v1 mirror endpointNew bearer-auth `GET /api/v1/workspace/cost-export` mirrors the rev-60 dashboard cost CSV endpoint on the v1 surface. Closes the v1 parity gap on the procurement-friendly takeaway artefact. The cost-axis MCP cluster on the protocol-bound surface now reaches seven axes: per-cycle (rev 13) + per-task (rev 51) + per-task-trajectory (rev 54) + per-recipient (rev 52) + per-recipient-trajectory (rev 61) + today (rev 53) + per-source (rev 57) + per-source-trajectory (rev 60) — all with v1 mirrors plus the procurement-evidence CSV takeaway. The MCP server has nothing left to design on the cost surface.
Visual polish: unified alarm-pill vocabulary across cost cluster + chronic-banner auto-action stateThe rev-58 source ⚡ pill, rev-61 ⏳ chronic pill, and the new rev-62 per-assignee ⚡ pill now all share the same brand-red treatment so operators read alarm pills consistently across all four cost-cluster panels (workspace banner, top-cost-tasks ⚡ pill, cost-by-source ⚡+⏳ pills, cost-by-assignee ⚡ pill). Rev-61 chronic-spike recommendation banner gains a new `is-auto-action` state when the workspace has opted into rev-62 auto-pause — solid border + stronger gradient + brand-color tint distinguishes 'desk will act' from 'operator should consider'. Cumulative micro-polish — every rev 22+ has carried at least one.