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

rev 352026-04-29

v1 bulk endpoints, mention-ack push, comment count badges, 7-day baseline, activity glyphs

Bulk operations on the v1 surface (close MCP-protocol gap)Rev 6 / 26 / 33 / 34 shipped bulk operations on the dashboard for outputs / tasks / signals / memory respectively — but until rev 35 those mutations were dashboard-only. The MCP server work (Q3 #1) now has nothing left to design on this surface: four new bearer-auth endpoints — POST /api/v1/tasks/bulk, POST /api/v1/signals/bulk, POST /api/v1/memory/bulk-update, POST /api/v1/artifacts/bulk — mirror the dashboard semantics exactly. Operators driving the desk via the upcoming MCP server can now clear a noisy queue in one tool call without enumerating IDs through individual PATCHes.
Mention ack push notification (close rev-34 named gap)Rev 34 introduced workspace-shared mention acks — when a teammate clicks 'I've got this', their name pins to the comment so other operators see who's already on it. Rev 35 closes the missing push channel: the original mention author now gets a Slack ping (and email when Resend is configured) the moment a teammate acks their @-mention. New task.mention_acked outbound event for downstream integrations. The full mention conversation now reads end-to-end across all three channels — opener (rev 27), receipt (rev 30 inbox + rev 34 ack), closure (rev 35 push to author).
Comment count + unacked-mention badges in Active WorkUntil rev 35, the rev-26 task discussion thread was buried at the bottom of every task card — operators had to expand the discussion to know if anything was happening. Now every task with comments shows a 💬 N pill in the header. When the current user has an unacked @-mention on the task, the pill turns brand-color and adds an @N indicator — that's the 'I should look at this' signal directly in the queue, distinct from the rev-30 mentions inbox panel which is the workspace-wide pull surface.
Today vs 7-day baseline on the Today panelRev 33 added the Today snapshot panel; rev 34 added yesterday delta. Rev 35 layers the trend horizon — every stat now shows the rolling 7-day daily-average baseline as a quiet trailing fact (e.g. '7d avg 4.2'). The window excludes today so today's value can't dilute its own baseline. Operators get two complementary horizons: yesterday for short-term volatility, 7-day for trend. Pairs with the rev-21 cost-cap warning + rev-32 cost-spike detector for the full descriptive → defensive cost narrative.
Activity log glyphs + per-kind colour tintingThe activity log accumulates 14 distinct kinds (cycle, capture, task, artifact, memory, status, slack, cost, outbound, source, member, stuck_loop, cost_spike, signal). Until rev 35 every row had the same brand-color dot — operators had to read every detail line to scan visually. Rev 35 replaces the dot with a tinted glyph per kind (↻ cycle, ⇣ capture, ✓ task, ✦ artifact, ★ memory, etc.) — pure unicode so it renders consistently across platforms with no extra dependency. Operators can now skim the log for cost spikes or stuck loops without reading every line.