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

rev 1052026-05-02

Per-author drill-down + per-category RSS feeds + v1 byline endpoints

Per-author archive at /blog/author/[slug]Closes the named rev-104 next-sprint candidate. Every blog post's byline is now a clickable chip that lands on a stable per-author archive page listing every post by that author, newest-first. Mirrors the rev-103 tag drill-down pattern at the byline axis. The primitive becomes load-bearing the moment a real human byline lands; even today it gives readers a way to slice the archive by voice without re-typing in the rev-102 search input. SSG'd via generateStaticParams so the page is static + cacheable like every other blog page.
Per-category + per-author RSS feedsCloses the per-axis subscription gap on the brand-voice surface. The rev-97 workspace-wide blog feed answers 'subscribe to all the brand voice'; rev 105 adds per-category (/blog/category/[key]/rss.xml) and per-author (/blog/author/[slug]/rss.xml) feeds so readers tracking only governance-first posts (or only one byline) can subscribe to a single slice. Pairs with the rev-37 /changelog/rss.xml + rev-97 /blog/rss.xml as the four-axis public-cadence subscription cluster (workspace blog / per-author / per-category / changelog). Per-category subscribe chips now sit inline in every CategorySection head and per-category sidebar row.
GET /api/v1/blog/authors + GET /api/v1/blog/by-author/{slug}Closes the fourth axis on the v1 blog cluster. Rev 102 added the listing endpoint; rev 103 added the per-post detail; rev 104 added the category taxonomy; rev 105 closes the byline axis. The cluster is now four axes deep on the protocol-bound side, matching the depth of the rev-100/101 changelog cluster (listing + sinceRev) and the rev-98/99 roadmap cluster (planned + most-requested + trending). MCP hosts rendering 'browse by byline' or AI tooling newsletters writing per-byline weekly roundups now get a typed contract instead of scraping the SSR'd author pages. OpenAPI 3.1 spec typed in lockstep (cadence pattern from rev 78 onward holds unbroken into rev 105).
Sidebar Authors + Browse-by-category cards + clickable byline chipNew AuthorsCard sidebar lists every byline with post count + click-to-archive link. New CategoriesCard sidebar pairs every category with its rev-105 per-category RSS feed in one click. Featured card adds a 'by [Author]' meta line. Post detail page wraps the existing avatar + name + date + readTime + word-count meta block in a single Link to the per-author archive — clicking anywhere on the byline cluster lands on the archive. New rev-105 visual polish: brand-color hover glow on the byline link, amber-tint per-category RSS chip in section heads, focus-visible rings + tactile hover lift on every new chip, stacked-on-mobile responsive treatment of the per-author hero.