Skip to content
Sign in
Artwork for Agentic AI in DevOps
Agentic AI in DevOps · August 31

#17 — DevOps Agents Need Context, Not More Tools

Your agent can call every tool you give it and still not know which account a service runs in, what depends on it, or what changed last week. So every session starts with the same discovery work. Andrey Devyatkin, Vladimir Samoylov and Fernando Gonçalves get into Grok 4.6 in Cursor, Anthropic's Claude Tag, cloud code review and AI-driven bug bounty noise, and why all four land on the same gap. What you will learn: Why AWS Agent Toolkit gives an agent access, but not orientation What a CI reviewer misses when Terraform sits in another repo How live configuration turns bug bounty noise into provable findings Why infrastructure state belongs in a database, not a skills file What it costs to keep your context inside one vendor's memory Maybe try B.O.R.I.S, our context layer for AI agents: https://www.getboris.ai Episode page, show notes and links

0:00Duration unknown
Play in

transcript

No transcript — this publisher did not publish one.

show notes

Your agent can call every tool you give it and still not know which account a service runs in, what depends on it, or what changed last week. So every session starts with the same discovery work.

Andrey Devyatkin, Vladimir Samoylov and Fernando Gonçalves get into Grok 4.6 in Cursor, Anthropic's Claude Tag, cloud code review and AI-driven bug bounty noise, and why all four land on the same gap.

What you will learn:

  • Why AWS Agent Toolkit gives an agent access, but not orientation
  • What a CI reviewer misses when Terraform sits in another repo
  • How live configuration turns bug bounty noise into provable findings
  • Why infrastructure state belongs in a database, not a skills file
  • What it costs to keep your context inside one vendor's memory

Maybe try B.O.R.I.S, our context layer for AI agents: https://www.getboris.ai

Episode page, show notes and links

links2

more episodes

All episodes