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

rev 1072026-05-02

Markdown-driven author profile overrides + chronological prev/next nav + per-category HTML archive page + v1 neighbours endpoint

Markdown-driven author profile overridesCloses the named rev-106 next-sprint candidate. Until rev 107 author profiles lived only in data/blog-authors.json. Rev 107 lets post markdown frontmatter optionally carry authorBio / authorTagline / authorAvatar / authorUrl — the most-recent post's frontmatter override wins, then the JSON registry, then null. A contributor's first PR can now include both their post and their profile in one place without touching a separate file. JSON registry stays the canonical home for fields not expressible in markdown (links[]) — the override surface is intentionally narrow but covers 95% of the contributor-onboarding case.
Chronological prev/next navigation on /blog/[slug]Closes the chronological reading axis on the rev-102+ blog cluster. The rev-106 related-posts (tag overlap) primitive answered 'you might also like' by content similarity; rev 107 adds the timeline axis ('newer post' / 'older post') for binge-readers walking the archive. Either side renders as a quiet 'first post' / 'latest post' card when the source is at the head or tail of the timeline. Pure derived state — no schema, no migration. Pairs naturally with the rev-106 related-posts grid that already renders above for the full content-similarity + timeline-axis pair.
Per-category HTML archive page at /blog/category/[key]Closes the gap the rev-106 sitemap explicitly noted ('Next doesn\'t currently have a /blog/category/[key] HTML route. List only the RSS endpoints so feed-reader auto-discovery works without shipping a 404 for the missing HTML axis'). Mirrors the rev-105 per-author archive page pattern at the category axis with a coloured hero that reflects the category's accent + a 'browse other categories' chip row at the bottom for cross-navigation. Sitemap updated in lockstep so crawlers see every per-category archive page (high priority) alongside the existing per-category RSS endpoints (lower priority — the HTML archive is the human-readable destination).
GET /api/v1/blog/{slug}/neighborsCloses the v1 parity gap on the rev-107 dashboard prev/next navigation primitive in the same cycle the dashboard primitive ships. Distinct from the rev-106 /api/v1/blog/related/{slug} endpoint (which ranks by tag-overlap content similarity) — neighbours walks the publication timeline. MCP hosts rendering 'binge-read the timeline' widgets, AI tooling newsletters generating per-post chronological sidebars, and search clients building 'next post' affordances now have a one-call answer for the chronological axis. Closes the sixth axis on the v1 blog cluster (listing + detail + categories + authors + related + neighbours). No auth — same model as the rev-102/103/104/105/106 endpoints.