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

rev 302026-04-29

Focus-aware memory retrieval, mentions inbox, focus history diff, v1 reaction + focus endpoints

Focus-aware memory retrievalRev 29 made the AI cycle's task selection and prompt focus-aware, but memory retrieval still ranked entries by recency + token overlap + importance only — a focus-themed task could pull in off-theme memory. Rev 30 closes that gap: a memory entry tagged with a current focus tag receives a +0.6 boost in the retrieval score so AI cycles working on focus-themed tasks recall focus-themed prior knowledge first. The third place focus is now load-bearing alongside queue selection (rev 29) and AI prompt (rev 29).
Mentions inbox panelEvery comment that @-mentions you across every task in the workspace now surfaces in a dedicated 'You were @-mentioned' dashboard panel between Pinned tasks and Active work. Each row shows the author, the comment text, the parent task title, and a one-click jump to the comment. Read state persists in localStorage per-workspace so dismissed mentions stay dismissed across sessions; 'Mark all read' clears the queue. Closes the rev-27 mentions push channel with the matching pull surface — multi-operator teams catching up after a day off no longer have to scroll every task to find what was directed at them.
Team focus history (week-over-week diff)The 'Team focus' sidebar panel now also shows the prior focus snapshot inline beneath the active tags. Tags that were dropped from focus render struck-through; tags that survived render in brand-color pills. Drives from the existing activity-log entries (rev 29 already records every focus change) so no new schema. Pairs with rev-29's focus tags by giving operators a sense of focus drift week-over-week — if you switched from #q3-launch to #renewals two weeks ago and the desk is still pulling Q3-relevant memory, the history line is the load-bearing visual signal.
v1 surface for comment reactions + focus tagsTwo new bearer-authenticated endpoints close the rev-29 MCP symmetry gap: POST /api/v1/tasks/:id/comments/:commentId/reaction toggles a 👍/👀/🎯/❤️/🚀 reaction (defaults to workspace owner if no asUserId provided), and GET/PUT /api/v1/workspace/focus-tags reads or sets the workspace's focus tags. The MCP server is now exclusively a protocol-translation job — every dashboard mutation including the rev-29 reactions and focus tags has a v1 equivalent.