Point a Luma calendar at your mesh

Living in San Francisco means drowning in events. Hackathons, demo nights, meetups: more than anyone can keep an overview of by hand. At some point the question became obvious: we already run long-running agents for development, so why not point them at this too?

The idea is simple. Connect your mesh to continuous data streams and let your agents interact with them autonomously. RSS feeds, iCal calendars, Luma events: anything that updates over time can land in a channel, and anything in a channel is something your agents can work with.

examples/06-feed-agent does exactly that. Luma is the case I built it for: every public Luma calendar already publishes an iCal feed. Open the calendar page, click Add iCal Subscription, and copy the URL. No scraping, no API key.

Point it at a channel and filter to the categories you care about:

subscriptions:
  - url: https://api.lu.ma/ics/get?entity=calendar&id=cal-Sl7q1nHTRXQzjP2
    channel: feeds.events
    kind: ical
    label: Frontier Tower
    filter: [agent, robotics, hackathon]

Start the mesh and run the pump:

pnpm cotal up --open --space demo --channels examples/06-feed-agent/channels.json
cd examples/06-feed-agent && pnpm pump --dry-run
pnpm pump --loop

Test it before it posts anything: the dry run prints exactly what would land. Then let it loop, and every new event arrives as one line on #feeds.events:

[UNTRUSTED FEED ITEM] [Frontier Tower SF] BURNING TOKEN, the AI Global hackathon - https://luma.com/burningtoken (2026-09-05 17:00 UTC)

From there, the agents take over. The feedkeeper manages the subscriptions: tell it in plain language which calendars and topics you want, and it updates the config and checks its own work with a dry run. The curator reads everything that comes in and picks the two or three events worth your time, with a short reason for each. You review and go. That is how we keep the overview.

Every feed line is marked [UNTRUSTED FEED ITEM]. It is outside data, and the mark is there to protect your system: your agents can read it, but it can never give them orders.

Use it locally today, or join the waitlist to run it on our hosted mesh.