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

rev 262026-04-29

Task comments, output → memory promotion, source keyword filter, bulk task actions

Task comments — teammate-to-teammate discussionNew task.comments column + endpoints + Discussion thread on every active-work card. Comments are explicitly distinct from operator notes (rev 14): notes feed the AI as authoritative direction; comments are for teammates to leave context, ask each other questions, or flag a question without polluting the AI's working set. The comment author or a workspace admin can delete. Outbound webhook event task.commented fires on every new comment so external automations can mirror the thread. Mirrored on the v1 surface (GET/POST /api/v1/tasks/{id}/comments).
Output → memory promotionNew Save to memory chip on every approval-queue artifact. One click promotes the artifact's title + summary + a slice of body into a durable memory entry (kind=lesson by default, importance 8). Tags carry over. Closes the gap where a great output was approved and then archived without the underlying insight ever becoming durable workspace knowledge — future cycles will retrieve it via the existing memory scoring.
Per-source keyword include/exclude filterEvery RSS, review-site, and LinkedIn source gets a Filter chip that opens an inline editor for include and exclude keyword lists (up to 10 each). Items whose title + body match an exclude keyword are dropped silently with an activity-log entry; if any include keywords are configured, items must match at least one. Lets operators tune noisy feeds without pausing them entirely. Stored on source.config (no schema change).
Bulk task actions — select + delete / set priority / tagActive-work panel now shows a checkbox on every task when the operator has edit role. Selecting one or more tasks reveals a bulk action bar above the queue: set priority (urgent/high/normal/low), add or remove a tag (with autocomplete from the workspace tag pool), or bulk delete (with confirm). New POST /api/tasks/bulk endpoint enforces a 50-task cap. Mirrors rev 6's bulk approve/archive on the artifact side.