[supermdguy]

Still figuring it out, but it's been really convenient to have an always-on agent that has access to internal systems and can be triggered by webhooks. Some examples of what we use it for:

- automatically fixing simple CI failures

- getting production alerts and automatically creating RCAs and a fix PR

- periodically checking slow DB queries and finding ways to speed them up.

- creating charts to answer one-off questions about our data

I've tried using it as an on-the-go coding agent as well, but found I prefer more interactive agents, so I can see what the code looks like.

[stephenway]

I think the interesting challenge isn’t running agents, it’s reviewing their work. The more code agents produce, the more important provenance, review ergonomics, and trust become. I also suspect repository platforms will need to evolve there over the next few years.

[nozzlegear]

> periodically checking slow DB queries and finding ways to speed them up.

How does this work in practice?

[jaggederest]

At least for me, I have a couple dozen years of DB experience but robot, given performance metrics, can get really close to optimal on a tactical level (single query or pattern of queries) but can't yet do the full normalize/denormalize level of improvements without supervision. But really solid if you have one misbehaving query and give it explain analyze access on a read only account