Separate reader traffic
When agents touch CI, teams need reviews, tests, audit logs, and rollback expectations.
Requests are not readers
The useful question is not whether traffic looks busy; it is which activity represents readers, monitoring, crawlers, retries, or system errors.
Check the logs first
- Decide what the agent can change and how a human accepts it
- Keep the test narrow: one low-risk task or tool entry before connecting permissions, logs, failure handling, and human takeover to production
What still needs proof
Treat this as a primary signal, then still check pricing, limits, and real adoption before acting. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.