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

rev 2062026-08-10Accelerating

Makes the managed approval handoff accountable: task-derived review ownership, owner-scoped queue views, reassignment, reminder-safe digests, and typed API parity.

One authoritative review owner + at-a-glance workloadEvery ready output now inherits the originating task's assignee as its review owner, avoiding a second reviewer field that could drift. The shared approval helper adds assigned, unassigned, mine, and mine-overdue counts; the dashboard summary renders mine / unassigned / owned chips and every row carries accessible owner text beside its age state.
My reviews, assigned, and unassigned views + inline reassignmentThe approval queue adds an ownership selector that composes with kind, tag, and keyword filters. Outputs with an originating task mount the existing assignment control, so operators can rebalance review directly from the queue through the existing role guard, notification, and audit path rather than creating parallel reviewer state.
Daily digest ownership + silent-reminder bug fixDigest rows name their owner, per-recipient preheaders and summary lines call out how many reviews are yours, and unassigned work stays explicit. A waiting approval queue now qualifies for the daily digest even on days with no fresh signal or newly-created artifact; previously that quiet-content condition could suppress the reminder while old reviews continued aging.
Review-owner API filters and OpenAPI 3.1 parityGET /api/v1/artifacts adds reviewer=assigned|unassigned, reviewerId, a nullable reviewOwner projection, and an approvalOwnership aggregate alongside rev 205's aging fields. OpenAPI types every addition, extending the typed-contract cadence to its 114th unbroken rev. No schema change.