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

rev 1092026-05-02

Per-tag RSS feed + '/' keyboard shortcut on /changelog + sitemap RSS entries + archive surface a11y polish

Per-tag RSS feed at /blog/tag/[slug]/rss.xmlCloses the named rev-108 next-sprint candidate. Mirrors the rev-104 per-category RSS + rev-105 per-author RSS shapes at the third axis so feed aggregators (Feedly, Inoreader, founder / AI-tooling release-roundup newsletters) can subscribe to one tag vocabulary with the same client they use for the workspace-wide blog feed. Closes the four-axis public-cadence subscription cluster on the protocol-bound side: workspace blog (rev 97) / per-category (rev 105) / per-author (rev 105) / per-tag (rev 109) / changelog (rev 37). Readers tracking only one tag (e.g. #MCP) now have a passive distribution channel scoped exactly to their interest without the brand-voice noise from off-theme posts. Pure read of the existing getPostsByTagSlug() helper so the page and feed never drift. Surfaced on every per-tag archive hero as an inline 'RSS' chip plus alternates metadata so feed-reader auto-discovery just works.
'/' keyboard shortcut on /changelog keyword searchMirrors the rev-103 /blog '/' keyboard shortcut at the changelog axis. The rev-101 changelog keyword search was visible but mouse-only — keyboard-first power-users who already use '/' on the dashboard (rev 17) and on /blog (rev 103) had no parity on the third reading surface. Rev 109 closes that gap. Press '/' from anywhere on /changelog to focus the search input; Esc clears the query + blurs. The visible <kbd>/</kbd> hint inside the search input fades on focus for discoverability, matching the rev-103 visual treatment exactly so all three keyword surfaces speak one consistent power-user vocabulary.
Sitemap entries for per-tag RSS feedsExtends the rev-108 per-tag HTML archive sitemap entries with their RSS-feed companions, mirroring the rev-105 per-category + per-author sitemap shape exactly. Same lower priority (0.4) as the rev-105 per-category + per-author RSS feeds since the HTML archive is the human-readable destination and the feed is the subscription endpoint. Crawler-side discoverability for feed aggregators reading the sitemap. Closes the indexability gap on the rev-109 RSS feed in the same cycle the feed itself ships — the cadence pattern from rev 37 onwards (ship the primitive + the sitemap entry in lockstep) holds unbroken.
Archive surface accessibility polishCumulative micro-polish (every rev 22+ has carried at least one). Adds :focus-visible outline rings to every archive cross-navigation chip across the per-author + per-category + per-tag archive pages so keyboard-only readers land cleanly on every chip with one consistent visual landing pad. The .blog-tag-other-chip already had hover lift via rev 108; rev 109 closes the accessibility gap on the matching per-author + per-category chips so all three archive surfaces speak one consistent accessibility vocabulary. Closes a small but consistent affordance gap that's been growing since the per-author + per-category archive pages shipped (rev 105 + rev 107) without the same accessibility treatment the rev-108 per-tag chips inherited from the start.