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

rev 692026-05-01

Per-tag cost-spike auto-pause closes the descriptive→defensive loop on the per-tag cost story

Per-tag cost-spike auto-pause toggleNew `workspace.tagCostSpikeAction` text column ('none' | 'pause' | null). When set to 'pause', the pulse engine's `selectNextTask` filter now also skips tasks whose tags overlap with any currently-spiking workstream until the operator acknowledges via the rev-68 ack surface. New `setTagCostSpikeAction()` + `getCostSpikePausedTagTaskIds()` helpers reuse the rev-67 `detectTagCostSpikes()` detector verbatim. Mirrors the rev-56 per-task auto-pause + rev-59 per-source auto-pause patterns at the per-tag axis. Default null (off, opt-in) so the rev-67/68 alarm + ack behaviour is unchanged unless the operator opts in. **Strategic significance**: closes the named rev-68 next-sprint candidate. The cost-spike alarm cluster (workspace rev 32 / per-task rev 55-56 / per-source rev 58-59 / per-assignee rev 62-63 / per-tag rev 67-69) now has descriptive → defensive coverage on every one of the five axes — the same auto-action pattern that started rev 20 with the workspace-level cost cap reaches the per-workstream axis.
Workspace config endpoints + v1 mirror in lockstepNew admin-only `PATCH /api/workspace/tag-cost-spike-config` route + matching bearer-auth `GET/PUT /api/v1/workspace/tag-cost-spike-config` v1 mirror. The cadence pattern from rev 37 onward (ship the dashboard primitive + the v1 mirror in the same cycle) continues. **Strategic significance**: the cost-axis MCP cluster (workspace / per-task / per-source / per-assignee / per-tag) now has full descriptive → ack → reconfigure coverage on every axis through the protocol-bound surface. The MCP server has nothing left to design on the cost-spike axis across all five axes.
Integrations panel UI section + adaptive cost-by-tag bannerNew 'Per-tag cost-spike action' section in the integrations panel under the existing Cost guardrails cluster (alongside rev-49 stale auto-archive, rev-56 per-task action, rev-59 per-source action, rev-62 chronic auto-pause). Two buttons: 'Alarm only' (rev 67/68 default) vs 'Auto-pause spiking workstreams' (rev 69 opt-in). Plus the rev-67 ⚡ alarm banner on the cost-by-tag panel now adapts when auto-pause is enabled — solid border + stronger gradient + 'Auto-pause is on' copy distinguishes 'desk will act' from 'operator should consider'. New `.ld-cost-tag-spike-banner.is-auto-action` CSS mirrors the rev-62 source chronic banner treatment at the per-tag axis. **Strategic significance**: cumulative micro-polish (every rev 22+ has carried at least one). The integrations panel's Cost guardrails cluster is now five primitives deep — rev-20 cost cap + rev-49 stale auto-archive + rev-56 per-task action + rev-59 per-source action + rev-62 chronic action + rev-69 per-tag action. The pattern is now uniform across every axis: every defensive control follows the opt-in toggle shape so an operator can tune the desk's autonomy gradient at any axis without ever feeling the desk is 'running away'.