Blog

Stay up to date with Grok and Delegate

Every morning, my Grokbot "TLDR" sends the AI developer news to Slack. It reads newsletters and blogs I follow, buys live news, X and Reddit data through Delegate, and checks the stories against our code.

The TLDR newsletter inspired the name and format: short summaries that help me decide which stories to read in full.

What arrives in Slack

The main message starts with four or five big stories from the last 24 hours: model launches, company moves, outages and security news. Then come two to four stories around Delegate, covering MCP, agent payments, API marketplaces and the libraries we use. It also covers what builders are saying on X, Reddit or other socials.

Each story gets a linked headline and two or three sentences with the number, version or name that matters. I can read the issue without opening every link.

A thread underneath gives me three to five points on what the news means for our work. If a library gets a security fix, I want the version in our code and what needs checking. If a provider deprecates an API endpoint, I want to know which of our agents still uses it.

Give it your reading list and read-only code

The bot knows my role at Delegate. Its memory includes my reading preferences and feedback on earlier issues.

The routine is configured to read our repository, its docs and the latest commits without making changes. I don't ask it to force a code reference into every story. One or two useful connections are enough.

My reading list starts with TLDR, TLDR AI, TLDR DevOps, Hacker News, Simon Willison, Latent Space, The Pragmatic Engineer and Interconnects. These are sources I would open myself; the bot does the first pass.

It also keeps a story log. A launch I read about on Monday shouldn't come back on Tuesday under a different headline.

Where Delegate fits

On November 16, my bot made three Google News searches covering agents and MCP, plus a batched search across X and Reddit. It bought that data through Delegate, without separate accounts or API keys for each data provider.

points on why they matter to Delegate
5
data calls through Delegate
4
for news, X and Reddit data
$0.033
My morning issue on November 16, 2026. The cost covers Delegate data only, excluding the cost of running the bot.

That is one day's cost, not a fixed daily price. Other issues can use different services or more searches. Searching the catalog is free; the data services it orders are paid per call.

  1. Read the news

    Trusted newsletters and blogs, plus live news, X and Reddit searches through Delegate.

  2. Check relevance

    Match stories to my role and code. Skip what the bot has already covered.

  3. Get the brief

    Headlines and short summaries in Slack, with a thread explaining why they matter.

From the day's news to a brief about my work.

Set up your own routine

My setup uses Grok, GitHub and Slack. For your version, choose an agent that supports scheduled runs and can access your sources and delivery channel. Code access is optional: a reading list and your interests are enough for a general news digest.

The quickstart explains how to connect your agent to Delegate. You can also ask your agent to help with setup:

set up https://dlgt.io/SKILL.md

Then give it a brief along these lines:

Write my morning report on the AI developer news. Start with my reading list and the context I provide. Use Delegate for news, X and Reddit searches from the last 24 hours, within my spending limits. Give each item a linked headline and a TLDR of two or three sentences. Explain why the stories matter to my work or interests in a thread. Check the story log so you don't repeat yesterday's issue. Never invent stories, links or facts.

Start with a few sources you already trust and schedule the first brief for tomorrow morning. Tell the bot which stories you opened and which you skipped.

A useful brief leaves you with less to read and a reason to open the links that remain.

Give your agent the whole catalog.

Get started

No subscription needed. You pay per job.