Leo can be trained on your niche, then cuts 200 stories down to ~20 worth reading.
AI newsletter
Train Feedly to find the stories, Claude to summarize them, Beehiiv to send. Promote the issue on X via Typefully. The whole loop runs on $45/mo.
Claude handles long context. Feed it 20 articles, get a coherent issue out the other side.
Free up to 2,500 subs, plus referral mechanics + an ad network when you outgrow free.
One newsletter → one X thread → one LinkedIn post, all from the same draft.
- feedly$8
- claude$20
- beehiiv$0
- typefully$0
- feedly$8
- claude$20
- beehiiv$39
- typefully$13
- feedly$8
- claude$80 API
- beehiiv$129
- typefully$28
Fast mode for Claude Opus 4.8 deprecated with November 30 removal date
Fast mode for Claude Opus 4.8 is being deprecated and will be removed on November 30, 2026. Developers using fast mode with Opus 4.8 must migrate to Claude Opus 5.5 to continue using the feature.
Usage and Cost Analytics API launched in beta to track token consumption and costs
Anthropic released the Usage and Cost Analytics API in beta, enabling organizations to monitor token usage and costs across Claude API consumption with filtering and grouping by dimensions like model, workspace, and API key. The API provides /v1/organizations/analytics/usage and /v1/organizations/analytics/cost endpoints. Legacy usage reporting endpoints remain supported.
Messages API and Token Counting API maximum request size increased to 128 MB
The maximum request size for the Messages API and Token Counting API doubled from 32 MB to 128 MB on the first-party Claude API, allowing developers to process significantly larger payloads in single requests. This change takes effect immediately and applies to both APIs.

Substack Notes can now include videos and mentions
Videos up to 15 minutes and @-mentions are now supported in Substack Notes published through Typefully. Videos are automatically preserved when cross-posting from X or LinkedIn, while unsupported content is flagged before publishing.
- 1Curate the weekFeedly
Browse the Feedly Leo digest; star ~20 worth syncing.
- 2SynthesizeClaude
Claude merges starred items into your section template.
Prompt · Issue from starred itemsYou are writing this week's issue of {{newsletter_name}}, a newsletter for {{audience}}. Voice: {{e.g. direct, mildly skeptical, light dry humor}}. Here are this week's starred articles: """ {{paste feedly starred items: title, source, url, 1-line summary}} """ Structure the issue using these sections (use this template every week): 1. **The story** — the single most important item, 120 words, with a sharp lede and one specific number. 2. **Three more worth your time** — bulleted, 35 words each, link in the bullet. 3. **Worth a click** — 5 short links with 1-line context each. 4. **One contrarian take** — pick the most against-the-grain item and steelman it in 80 words. Rules: - Never use "delve", "in the rapidly evolving landscape", "it's important to note", "navigating the complexities". - Every section opens with a specific noun, not a transition phrase. - No em dashes. Use commas, periods, or parentheses. - Cite source name inline, like "(Bloomberg, May 2)". Output the full issue as Markdown, ready to paste into Beehiiv. - 3Edit and designBeehiiv
Drop into Beehiiv. Use the same template every week.
- 4Promo loopTypefully
Typefully thread + LinkedIn post draft; schedule for Tue 9am ET.
Prompt · X thread + LinkedIn post from issueTake this newsletter issue: """ {{paste full issue}} """ Output two artifacts: 1. **X thread** (5 to 7 posts, max 280 chars each) - Post 1: the hook from the lede, no "in today's newsletter" - Posts 2 to 6: one specific takeaway each, with a number or name - Final post: link to the issue with a one-line "why click" 2. **LinkedIn post** (180 to 220 words) - First line is the hook, no warm-up - Plain text, no hashtags except 1 to 2 at the end - End with a link to the issue and a single concrete CTA No emojis in either. No em dashes. - 5ShipBeehiiv
Send Tue 7am ET. Beehiiv recommendations, boosts, and ads kick in.
One issue/week, 90 minutes of writing time. Sponsorship rates lifted at 2k subs because the audience was tightly scoped to AI engineers.
Beehiiv recommendations only kick in after ~500 subs. Plan for a 90-day cold start.
Read every issue out loud before sending. Strip 'delve', 'in the rapidly evolving landscape', etc.
'AI news' is dead on arrival. 'AI for HR teams in regulated industries' has a list.
What changed in AI tools and the stacks that ship. One email a week.
