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

rev 642026-05-01

Task quick-start templates, per-assignee chronic warning, activity heatmap, cumulative UI polish

Task quick-start templates (operator-stickiness pivot)New `src/lib/task-templates.ts` with 8 vertically-scoped operator quick-start templates (Competitor analysis, Customer feedback synthesis, Quarterly board update, Renewal conversation prep, Pricing decision review, Content brief, Hiring scoping, Strategic question). Each template pre-fills title / summary / goal / kind / deliverableType / priority / tags so an operator can go from 'I want a board update' to 'task queued' in two taps. The chip row replaces the old 'Queue task directly' button when the form is collapsed; tapping a chip opens the form with all fields pre-filled and a clear 'X — adjust before queueing' eyebrow that names the active template. **Strategic significance**: pivots from the cost-axis cluster (13 revs deep) into the operator-stickiness layer. Mirrors the rev-19 onboarding-template shape (memory + signal presets) but at the workspace's *ongoing* starvation point (day N) rather than the day-1 starvation point. Every direct-task path until rev 64 started from a blank form, even though operators routinely run the same 6-8 task shapes — quick-start templates collapse repeated typing into chip-tap-and-go.
Per-assignee chronic-spike counter + chronic warning push (closes rev-63 named candidate)New `workspace_member.consecutiveSpikeDays` integer column + chronic-warning sweep wired into the existing `pingAssigneeCostSpikes()` daily cron. Mirrors the rev-61 source consecutiveSpikeDays counter at the per-recipient axis: the counter increments every time the rev-62 detector flags an assignee as spiking, resets to 0 the first day they don't. When any assignee crosses the chronic threshold (3 days), a new `assignee.chronic_warning` outbound event + Slack push fires recommending rebalancing rather than auto-acting. Distinct from the rev-62 daily ⚡ alarm — the chronic warning names a *structural* problem (queue overload, scope creep, noisy task) and is rate-limited via its own activity-log kind so the chronic warning doesn't drown out the daily ⚡ alarm on the same workspace. New `⏳ Nd` chip on the cost-by-assignee panel (mirrors rev-61 source chronic chip): stays neutral until the count crosses 3d, then turns brand-red. **Strategic significance**: nudge-not-act because the right answer (reassign work / raise cap / hire) depends on context the desk doesn't have. The four-axis alarm cluster now reads consistently — daily push (rev 32/55/58/62) + chronic counter + warning (rev 61 source / rev 64 assignee).
7-day × 4-block activity heatmap (UI/visual improvement)New `ActivityHeatmap` client component renders inside the rev-13 desk-health panel. 28 cells (7 days × 4 hour-blocks: night 23-5 / morning 5-11 / midday 11-17 / evening 17-23 UTC). Reads top-to-bottom for diurnal rhythm, left-to-right for weekly cadence. The diagonal of dark cells is the desk's natural rhythm; the bright outliers are when something unusual happened. Mirrored on the v1 surface as `sevenDay.heatmap` on `/api/v1/stats` so MCP hosts can render the same temporal-shape view. Pure derived state from the existing 7-day desk_runs query — no extra round-trip, no schema change. Hidden when there are no cycles in the window (fresh workspaces don't see clutter). **Strategic significance**: pairs with rev-13 desk-health + rev-14 cycle performance + rev-15 signal sparkline as the fourth instrument on the 'is the desk healthy?' cluster — but along the temporal-shape axis the others don't cover. Useful for capacity planning ('the desk runs hottest mid-morning') + diagnosing dead-window patterns ('we never get overnight cycles, is the daemon up?').
Cumulative UI polish + accessibility (cost cluster, focus chips, panel target flash)Cumulative micro-polish (every rev 22+ has carried at least one). Five small but cumulative pieces: (a) the rev-29 focus-tag chips gain a tactile 1px hover lift + soft shadow + brand-colour border-shift on hover so the focus surface feels active rather than static. (b) The rev-29 focus-suggest buttons gain matching transform + `:focus-visible` outline so keyboard-only operators see a clear landing pad. (c) New `.app-panel.is-target-flash` keyframes animation gives a soft 1.8s pulse when scroll-into-view lands on a panel via #panel-* navigation (mention permalinks, palette jumps, scroll-to-top jumps) — clearer 'you arrived here' affordance without a toast. (d) New `:focus-visible` ring on the rev-23 keyboard-shortcut FAB + rev-38 scroll-to-top FAB so the three power-user FABs (palette + shortcuts + scroll-top) land consistently. (e) New `.sr-only` utility class for the rev-64 heatmap's per-cell screen-reader labels so the heatmap is meaningful to assistive tech. **Strategic significance**: the rev-by-rev discipline of one targeted polish per rev is what keeps the dashboard from drifting toward the design-debt smell that hand-rolled SaaS dashboards usually develop after 64 revs.