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

rev 922026-05-02

Digest configuration audit endpoint + 'n' keyboard shortcut + print-friendly /share/[token] + integrations panel polish

Historical digest-gating audit log on dashboard + v1 — closes the named rev-91 next-sprint candidateRev 91's running state explicitly named 'unified digest configuration audit endpoint' as the rev-92 candidate, citing the rev-90 closure-receipt event + rev-90 activity-log entry + rev-91 multi-channel push as the three layers that together capture every gating change but had no historical-read surface. Rev 92 closes that. New `getDigestAuditLog()` helper reads the rev-90 `digest_gating_change` activity-log entries within a bounded window (default 30 days, max 365), parses each detail string into a structured `{ outcome, recipientLabel }` shape, and returns newest-first. New `GET /api/workspace/digest-audit?sinceDays=30&limit=100` (admin-only) + matching `GET /api/v1/workspace/digest-audit?sinceDays=30&limit=100` (bearer-auth) endpoints expose it on both the dashboard and protocol-bound surfaces in lockstep. New collapsible inline 'Gating history' section in the integrations panel renders directly under the rev-89/91 gating-pill cluster so admins see both current outcome AND historical drift in one glance. OpenAPI 3.1 spec entry typed in lockstep. **Strategic significance**: closes the four-axis digest-config instrument cluster on the protocol-bound surface — rev-86 digest-preview (render-only test) + rev-89 digest-recipients-gating (current-instant outcome) + rev-90 digest-config (current snapshot) + rev-92 digest-audit (historical drift). The MCP server's digest-config tooling now has nothing left to design across the *complete* descriptive→audit lifecycle. Pairs with the rev-91 multi-channel push as the historical-read surface that completes the rev-90 closure-receipt loop on the procurement-conscious side.
Power-user keyboard shortcut 'n' opens the new task creation formExtends the rev-23 keyboard shortcuts overlay + rev-27 ⌘K command palette with the third primary creation affordance — power-user keyboard parity with Linear/Raycast/GitHub for the most-frequent originating operator action (handing the desk a new task). Press `n` from anywhere on the dashboard (when not typing in an input/textarea) and the desk: (a) smooth-scrolls to the rev-24 `panel-task-create`, (b) dispatches a `loopdesk:open-task-form` custom event, (c) the form's new useEffect listener expands the `open` state and focuses the title input. Documented in the rev-23 keyboard shortcuts overlay so the shortcut is discoverable. **Strategic significance**: rev 23 shipped the keyboard surface (?, /, g+a/t/s/m/h, Esc); rev 27 shipped the command palette; rev 92 closes the third edge of the keyboard creation triangle. The dashboard now has three orthogonal entry points for new tasks — chip-tap on a quick-start template (rev 64), command palette ⌘K (rev 27), single-key shortcut `n` (rev 92) — covering chip-discovery, search-driven, and muscle-memory operators in one consistent vocabulary.
Print-friendly /share/[token] page — procurement-friendly takeaway at zero schema costProcurement reviewers reading shared briefs frequently want to print or save-to-PDF for their evidence package; until rev 92 the page printed with the brand header, the rev-45 ShareTagDrillDown chip row, the rev-18 ShareFeedbackForm reaction surface, and the dashboard footer all bleeding ink and competing with the load-bearing content. Rev 92 adds an `@media print` block in `globals.css` that hides every operator-only or interactive surface (header / drill-down / feedback / footer / status pills) and strips the card chrome so the body reads as a clean single-document print. Title + summary + body get print typography (24pt / 12pt / 11pt). External links print their full URL inline via `a[href^='http']::after` so the reviewer can trace every reference without scanning the screen version. Revision lineage (rev 44) + source evidence (rev 42) print as boxed appendix blocks at the end with `page-break-inside: avoid` so they read as a clean appendix. **Strategic significance**: rev 42 made input transparency operator-visible on the share page; rev 44 made revision lineage external-reader-visible. Rev 92 makes both procurement-takeaway-friendly. The procurement story across the public surface is now four levels deep: input evidence (rev 42) + revision lineage (rev 44) + interactive narrowing (rev 45/46) + take-and-print (rev 92).
Visual polish — audit history list typography + brand-green/amber row tintsNew `.ld-digest-audit-*` CSS uses a brand-green left-border accent on `would_send` rows + amber on `muted` rows, mirroring the rev-89/91 gating-pill colour vocabulary so the three dashboard gating surfaces (rev-89 rollup pill / rev-91 per-member pill / rev-92 audit row) read as one consistent visual story. The collapse/expand chevron (▸/▾) reads as a quiet affordance under the digest control cluster — the section is expanded only when the operator wants it, so the integrations panel doesn't grow visually for admins who don't care about the audit history. Cumulative micro-polish — every rev 22+ has carried at least one. **Strategic significance**: the integrations panel now reads as a four-level digest control cluster (rev-2 on/off → rev-79 personal sections → rev-80/81 mute config → rev-89 gating preview → rev-92 audit history) wearing one consistent typography + colour vocabulary. The rev-by-rev discipline of one targeted polish per rev keeps the panel from drifting into instrument-stack chaos after 92 revs.