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

rev 1132026-05-03

Live markdown preview across task creation form + operator notes + renew notes + comment composer + unified .ld-md-live-preview surface

Markdown preview on task creation form summary + goal (closes named rev-112 candidate)Closes the named rev-112 next-sprint candidate. Until rev 113 the rev-24 manual task creation form rendered both the 'Why this matters' summary and the optional goal as plain textareas — operators pasting structured task descriptions had no surface to verify how the field would render once the AI cycle and the rev-10 artifact body / rev-110 memory / rev-111 operator-note renderers consumed it. Rev 113 adds an inline brand-color-accented preview directly below each textarea that fires when the rev-110/rev-111/rev-112 shouldRenderAsMarkdown() heuristic returns true (≥80 chars OR markdown-syntax detection). Short one-line summaries stay plain — only structured paste pays the marked.js round-trip. Closes the rendering symmetry on the typed-input axis (rev 112 closed the *saved-template* preview; rev 113 closes the *live-typed* preview).
Markdown preview in operator note composer + renew note composerMirrors the rev-113 task-creation primitive at the rev-14 operator-notes axis and the rev-50/rev-112 renew-note axis. Past operator notes already render as markdown (rev 111); the rev-113 live preview closes the read/write symmetry so operators pasting structured steering see exactly what the AI cycle prompt will see *before* submitting. Same shouldRenderAsMarkdown() gate. Renew note composer follows in lockstep — renew notes route through addTaskOperatorNote() (rev 112) and the past notes render as markdown (rev 111), so a structured renew note will be readable as markdown after submission and the live preview signals that contract before the operator commits.
Markdown preview in comment composer (preserves @-mention pills)Closes the rendering quartet across all four operator-loaded composers (task creation summary + goal, operator note, renew note, comment). Posted comments already render as markdown via rev 111 with @-mention pills preserved through renderCommentMarkdown(); the rev-113 live preview reuses the same helper so operators see their structured comment + mention pills before posting. Long discussion threads with code samples or numbered checklists no longer surprise the author with a different rendered shape post-submit.
Unified .ld-md-live-preview CSS — one visual family across four surfacesCumulative micro-polish (every rev 22+ has carried one). New .ld-md-live-preview shared CSS class anchors all four typed-input preview surfaces (rev-24 summary, rev-24 goal, rev-14 operator note, rev-50/rev-112 renew note, rev-26 comment) in one consistent visual vocabulary alongside the rev-112 read-only saved-template preview. Brand-color dashed left border + soft gradient + 220ms ld-md-live-fade entrance animation. Max-height 220px with overflow-y so a long structured paste doesn't push the textarea off-screen. New .ld-md-live-preview-label uppercase eyebrow + per-surface contextual copy ('Markdown preview', 'this is what the next cycle will read', '@-mentions render as pills') so the operator knows what they're verifying without reading the surrounding form. Closes the visual-hierarchy gap that would have grown as the rev-by-rev rendering symmetry thread reaches every dashboard text surface.