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

rev 1142026-05-03

Live markdown preview on signal detail + artifact body editor + memory teach-the-desk + memory edit — closes the rev-113 typed-input rendering quintet

Live markdown preview on the rev-22 signal-add form detail field (closes named rev-113 candidate)Closes the named rev-113 next-sprint candidate at the signal-axis composer. Until rev 114 the rev-22 manual signal-add form rendered the 'What happened?' detail field as a plain textarea — operators pasting structured signal context (forwarded email bodies, Slack threads, customer feedback excerpts with bulleted asks) had no surface to verify how the field would render once the AI cycle and downstream renderers consumed it. Rev 114 adds an inline brand-color-accented preview directly below the textarea using the rev-113 unified .ld-md-live-preview surface + same shouldRenderAsMarkdown() gate so short one-line signals stay plain. Closes the rendering symmetry gap on the signal-axis composer alongside the rev-113 task-creation + operator-note + renew-note + comment composers.
Live markdown preview on the rev-23 inline artifact body editor (closes named rev-113 candidate)Closes the named rev-113 next-sprint candidate at the artifact-body axis. The rev-23 inline body editor is the operator's primary direct-edit surface for outputs — title (160 chars), summary (260 chars), body (12,000 chars markdown). Until rev 114 the body field rendered as a plain monospace textarea; operators editing structured output (briefs with headings + bulleted action items, decision artifacts with rationale + risk sections) had to save and look at the rendered card to verify their changes parsed correctly. Rev 114 adds an inline preview that fires the same rev-10 renderArtifactBody helper used at save time + on the public share page — the preview is bit-for-bit what the operator sees post-save. New .is-long-form modifier on .ld-md-live-preview-body extends max-height 220px → 360px since the body field caps at 12,000 chars (vs 600 for operator notes / 1000 for comments). Closes the verify-before-save gap on the operator's most load-bearing direct-edit surface.
Live markdown preview on the rev-6 memory teach-the-desk form + rev-7 inline memory editorExtends the rev-114 typed-input primitive to the two memory composer surfaces. The rev-6 'Teach the desk' add form and the rev-7 inline memory editor both feed durable knowledge into the workspace's memory store; rev-110 made memory entries render as markdown but the *write* surface stayed plain. Operators pasting structured knowledge (bulleted brand-voice rules, decision rationales with sub-points, lessons-learned with numbered steps) now see the rendered shape before saving so the next AI cycle's memory retrieval reads what they intended. Closes the read/write symmetry on the memory-axis the same way rev 111 closed it on operator notes + comments and the same way rev 113 closed it on the rest of the typed-input cluster.
Tactile hover affordance on every .ld-md-live-preview surface + cumulative visual polishCumulative micro-polish — every rev 22+ has carried at least one. Every .ld-md-live-preview surface (now five composers + two memory variants) gains a 220ms hover lift: border-color steps from rgba(31,143,137,0.32) → 0.55, gradient deepens, a soft brand-color box-shadow appears on the bottom edge. The hover affordance signals 'this preview is real, scroll it, hover it' rather than competing visually with the active textarea above it — operators verifying long structured paste benefit because they can scroll the preview without losing the textarea. Plus the new .is-long-form modifier extends max-height to 360px on the artifact body editor preview only, so 12,000-char bodies scroll cleanly without competing with the surrounding edit shell.