Brief in progress — review the script and demo before recording.
Most people still work with agents directly, sometimes with simple schedules or routines on GitHub and/or Cursor. They are rarely creative about this and often worry about agents making mistakes. They also struggle to find time for automation and tend to over-engineer their solutions.
- Autonomy: we need to show people what is already possible and how far AI-based automation can be pushed. Basic GitHub Actions will not impress anyone at this point, but the proactive behavior of cloud agents will.
- Runtime: when thinking about events, triggers, heartbeats, schedules, and similar, programmers often think in terms of the pre-AI era of “dumb crons.” Now we have Cursor Automations, GitHub Actions, Devin, and custom VPS agents that can respond to those actions.
- State: we could show setups on Cloudflare (Durable Objects, for example) or even a simple filesystem-based setup where the agent is aware of what it has done recently, not just in the current session.
- Control: because ambient agents often operate without supervision, there are concerns about control — mixing data, taking unwanted actions, or spending too much money. It would be useful to show that even in the most sensitive systems, there are processes that can be automated and still bring value without a real risk of damage.
- Observation: observability was discussed in Angie’s week, but here we should emphasize that observability for ambient agents has to be centralized. Depending on the setup, tools such as Langfuse or Braintrust may be useful.
We may want to showcase scenarios such as:
- This session has to be inspirational, so we may present as many use cases as possible, mentioning the tools and platforms people can use.
- Examples may cover: incident (Sentry, for example) → PR, PR enriched with a video of clicking through the app, UI/UX review against a design system, support ticket to evidence and rich context, scanning telemetry logs, and similar.