A Research Brief That Writes Itself Every Morning

A real recurring swarm workflow: 150 stories scraped and 20 curated every morning, 211 dated briefs archived since February, zero failures since 24 August.

  • Schedules
  • Research
  • Memory
  • GTM

Real session, redacted. This workflow runs in our own swarm every morning and has since 25 February 2026. The brief itself is internal, so the figures below come from the swarm's own task records; the primitives behind it are open source. All times are Barcelona time.

Request

A standing ask from the two founders: every morning, before the day starts, a short brief of what moved in AI — from sources they chose, curated to what is worth reading, delivered by email. No prompting, no reminding; the schedule is the request.

Starting context

The workflow has run daily since 25 February 2026. Each run scrapes the Hacker News front page (pages one to three), the New page, and Show HN, then loads a shared source-registry script that adds the Anthropic blog, the OpenAI and DeepMind RSS feeds, and eight X accounts read through the X API. Adding a source means adding one entry to the registry — not editing a prompt. Two artifacts land on every run: an email to the two founders and a dated Markdown file in the shared workspace archive.

Task breakdown

The run of 5 October 2026 is representative. 04:30 the schedule fired. The scrape pulled 150 stories from the registered sources. The deterministic build curated them to 20 — ten from the front page, five from New, five from Show HN — plus two deep dives and one external item. The three lab blogs had published nothing in the 24-hour window, so the brief said so instead of padding the section. 04:33 the email was sent and the dated brief archived: 3 minutes 28 seconds end to end.

Worker roles and handoffs

The schedule is the dispatcher — nobody asks for the brief; it exists every morning. The scripts do the fetching, curation, formatting, delivery, and archiving, with no model in the formatting path since the late-June rebuild. An agent enters only on failure: the lead reviews the failed run, fixes the cause, and records the learning. There is one handoff — schedule to scripts — which is why this is the cheapest workflow the swarm runs.

Approval points

The brief is internal, so the gates sit on its configuration rather than on each run: which sources count, what the brief is for, and who receives it are human-set and human-changeable. Any external reuse of its content — a post, a customer note — goes through a human first.

Output

Two artifacts per run: the email in the founders' inboxes before they start the day, and a dated Markdown brief in the shared archive — 211 dated briefs and counting, every one searchable by every agent in the swarm.

Measurable result

Measured from the swarm's task records. Before the rebuild (4 March to 28 June): 105 completed of 118 runs, 11 failed, 8.9 minutes on average. The LLM-driven formatting step that kept retry-looping was replaced with two deterministic scripts, and email delivery moved server-side after authentication errors. After the rebuild (29 June to 5 October): 91 completed of 94 runs, 3 failed, 7.5 minutes on average — and no failure since 24 August.

What stayed human-owned

Which sources count, what the brief is for, and every decision to act on it. The swarm owns the pulling, the curating, and the delivering; the founders own what the news means.

Sources and tools

  • Schedules — the recurring trigger: a cron expression on a timezone that creates the task each morning. Documented under scheduling.
  • The shared source registry — one script, one entry per source, shared by every run and reusable by other workflows.
  • Deterministic build and send scripts — curation, formatting, delivery, and archiving run as code, not as model output, so the figures in the brief are auditable and the email sends server-side.
  • Shared memory — past runs and source quirks stay searchable; see the memory architecture docs.

More real sessions: the engineering pull request merged in four hours, the security-alert triage that closed thirty-three Dependabot alerts, the two-day orchestration loop that carried one request to four human-merged pull requests, and the fully public x402 payment session. Browse everything on the examples index. The schedule, script, and memory primitives behind this page are open source in desplega-ai/agent-swarm.