Coding Agents Are Secretly General Agents

Denny Lee is PM Director, Startups & Ecosystem at Databricks, a longtime Apache Spark, MLflow, and Delta Lake contributor — and one of the people behind Omnigent, the open-source meta-harness Databricks just released under Apache 2.0. He joins Demetrios to explain why the industry is moving from models to harnesses to meta-harnesses, why token spend is replaying the CapEx-to-OpEx shift all over again, and why he's using debating AI agents to plan a matcha farm in Taiwan.In this episode:🍵 Agents as research partners — Denny uses dueling agents to scout matcha-growing regions in Taiwan, down to soil pH, elevation, and processing infrastructure🥊 Why agents should debate each other — letting two models argue surfaces the questions you didn't know to ask🔱 Forking conversations — the missing UX pattern: branch a session, keep the shared context, explore two threads in parallel🧠 The meta-harness layer — how Omnigent sits above Claude Code, Codex, Pi, and custom agents so models and harnesses become hot-swappable parts👥 The two-pizza rule for agents — military span-of-control logic says you can manage 5–7 agents before you lose the thread💸 Tokenomics is the new DevOps — the CapEx→OpEx playbook repeats: give developers spend visibility, keep central governance for the rest🛡️ Policies, budgets, and guardrails — enforcing cost caps and approval rules at the harness layer instead of inside prompts🤖 Auto model selection — why classic machine learning (not another LLM) may be the right way to route tasks to cheap vs. frontier models✍️ "Created by" vs. "assisted by" — the open source accountability debate: whoever submits the code owns the code🗄️ Databases are back — agents need cheap, stateful memory, which is why Postgres, Lakebase, and serverless databases are having a momentIf you're building with coding agents, managing AI spend, or trying to keep up with the harness arms race, this one's for you.Links & Resources:Omnigent (open source): https://www.databricks.com/blog/introducing-omnigent-meta-harness-combine-control-and-share-your-agentsOmnigent GitHub: https://github.com/databricks/omnigentDenny Lee on LinkedIn: https://www.linkedin.com/in/dennygleeDenny's blog: https://dennyglee.comTokenomics Foundation announcement: https://www.finops.org/insights/finops-x-2026-day-1-keynote/

Qdrant Roundtable episode: The Current State of Agentic RetrievalJoin the Community: https://go.mlops.community/YTJoinInGet the newsletter: https://go.mlops.community/YTNewsletterMLOps GPU Guide: https://go.mlops.community/gpuguideBig shout-out to Qdrant for the collaboration!// AbstractAI agents are only as good as the information they can find, retrieve, and remember. In this community roundtable with the Qdrant team, we explored the latest advances in agentic memory, vector search, retrieval systems, and production AI architectures.As AI agents move beyond simple chatbots into systems that can reason across large amounts of information, retrieval is becoming one of the most important layers in the AI stack. The discussion covered the real-world challenges of building agents that remember what matters, forget what doesn't, and consistently retrieve the right context at the right time.If you're building AI agents, RAG systems, or production AI applications, this conversation offers practical insights into where retrieval is headed and what it takes to build reliable, scalable agentic systems.// BioEwa SzyszkaEwa is a Developer Relations professional based in San Francisco with a background in Computer Science and Hardware Engineering, passionate about bridging the gap between technology and the developer community. She holds a BSc in Computer Science and an MSc in Electronics, bringing a strong blend of deep technical foundations and communication skills to her work.Dylan CouzonDylan is based in New York City, and he helps developers build better AI applications. He is passionate about AI, programming, open source, and robotics, and enjoys sharing what he’s building and learning along the way.Neil KanungoNeil is an experienced professional with expertise in data science, developer relations, and product growth. Currently serving as the Head of Developer Relations at Qdrant, Neil previously held the position of VP of Product Led Growth & Developer Relations at KX, where significant increases in product registration and user activation were achieved. At TIBCO, Neil managed a team focused on enhancing the adoption of TIBCO Spotfire through various initiatives, including tutorial videos and live webinars. With a strong technical background, Neil has developed innovative solutions in analytics, machine learning, and data visualization across multiple roles, including Engineering Data Analyst and Asset Integrity Engineer at Enterprise Products. Neil holds a Bachelor of Science in Radiation Physics from The University of Texas at Austin, a Master of Science in Mechanical Engineering from Texas Tech University, and is pursuing a Master in Applied Data Science from the University of Michigan.Evgeniya SukhodolskayaDeveloper Relations at Qdrant with 8 years of IT experience across software engineering, machine learning, and technical management, and 4 years in Developer Relations. Holds a Master’s in Machine Learning, Data Analytics, and Data Engineering. Passionate about NLP, data-centric AI, and the role of vector search in advancing AI technologies.Andrei CristeaAndrei is a Berlin-based Developer Relations Engineer at Qdrant, a prominent open-source vector database. With a Master’s degree in Artificial Intelligence from TU Munich, his expertise bridges AI, data infrastructure, and knowledge engineering.Hosted by Demetrios// Related LinksWebsite: https://qdrant.tech/~~~~~~~~ ✌️Connect With Us ✌️ ~~~~~~~Catch all episodes, blogs, newsletters, and more: https://go.mlops.community/TYExploreJoin our Slack community [https://go.mlops.community/slack]Follow us on X/Twitter [@mlopscommunity](https://x.com/mlopscommunity) or [LinkedIn](https://go.mlops.community/linkedin)] Sign up for the next meetup: [https://go.mlops.community/register]MLOps Swag/Merch: [https://shop.mlops.community/]

Kingsley Madikaegbu is the founder of HealID, a startup building agentic AI on top of the Model Context Protocol (MCP) for one of the most heavily regulated environments there is: healthcare.Recorded at MCP Dev Summit North America in New York, Kingsley sits down with Alex Salkever of the Agentic AI Foundation to break down how you give patients, doctors, caregivers, and family members each their own agent over the same medical record — without breaching HIPAA, leaking PHI, or letting an agent quietly go off the rails. In this conversation:🏗️ The four-layer architecture — Dumb data at the bottom, then access permissions, then MCP, then reasoning agents on top. Why logic never touches the data layer.🔐 MCP vs REST — Why enforcing per-role compliance in a REST API meant encoding permissions everywhere, and how MCP collapses that mess.🪪 HIPAA, auditability & traceability — Proving a specific person (not a snooping agent) accessed a record, with a full audit trail that regulators actually accept.🎟️ The nightclub-bouncer analogy — How MCP reorganizes the entire "club" per guest instead of just checking a VIP list.⌚ Wearables & real-world data — Turning an Apple Watch arrhythmia signal into a triaged, severity-scored workflow with doctors in the loop.🧭 Deterministic vs model-driven — Why anything clinical or regulatory stays binary, and the agent-as-coach (not decision-maker) pattern for patients.🛑 Keeping agents on the leash — Tool restriction, behavioral metadata, and drift/anomaly detection so an agent can't reinterpret its own job.⚡ The instant kill switch — Revoke permission, and the agent returns a hard 404, never partial data.⚖️ The liability question — When an agent follows a designed workflow and something goes wrong, who's responsible: patient, host, or provider? The industry hasn't decided.📋 Kingsley's MCP wishlist — Built-in traceability (OTEL-style spans), native time-bound enforcement, and guardrails against agent-to-agent data leakage.If you're building agentic systems for healthcare, finance, legal, or any regulated industry where "the agent did it" isn't a good enough answer — this one's for you.Links & Resources🔗 HealID — https://gethealid.com/🔗 Kingsley Madikaegbu — https://www.linkedin.com/in/kmadikaegbu🔗 Alex Salkever / Agentic AI Foundation — linkedin.com/in/alexsalkever🔗 MCP Dev Summit North America — https://events.linuxfoundation.org/mcp-dev-summit-north-america/Timestamps:[00:00] Intro[00:13] AI Agent Liability[01:10] MCP in Healthcare AI[06:30] MCP vs REST Architecture[11:29] Healthcare Integration Challenges[18:29] Non-compliant Patient Challenges[24:13] Deterministic vs Model-Driven Workflows[28:08] AI in Healthcare Conversations[34:38] Agent-to-agent workflows in healthcare[38:02] Future MCP security

In this episode:🧠 Coding agents are generalist agents — why "positive transfer" means an agent that's better at code is better at everything, and how that makes them "AGI-complete"⏳ "Code will be solved in a year" — what the automation of knowledge work actually looks like, and why Jay joined ClickUp to be on it🏗️ Why the labs are crushing AI startups — free-for-two-years deals, Windsurf losing Claude access, and the brutal economics of building on top of frontier models🔗 The real moat is convergence — context, surfaces, and unit economics, a.k.a. "Cursor for your whole job"💬 Slack's data walls & the Glean problem — why fragmentation is the enemy and a single system of record wins🧪 RLVR & verifiability — why code became the perfect training ground for agents, and how to tell if you're even getting better🔬 LLMs are running the frontier of science — Putnam 12/12, Erdős problems, simulating a cell, and vibe-writing economics papers🚗 The car wash test that still breaks GPT-5 — spiky models, world models, Plato's cave, and the "stochastic parrot" debate🏖️ Plus: mechanistic interpretability as "brain surgery," catastrophic forgetting, the danger of deleting knowledge from models, and a pitch for a "resort for LLMs"Whether you're building agents, leading an AI team, or just trying to figure out what "agentic" really means for everyday work — this one's a fun, deep ride.🔗 Links & ResourcesJay Hack: linkedin.com/in/jayhackClickUp: clickup.comMLOps Community: go.mlops.communityMentioned: Gödel, Escher, Bach (Douglas Hofstadter) · "Machine Learning: The High-Interest Credit Card of Technical Debt" (Sculley et al.) · Periodic Labs · Ginkgo Bioworks · Physical Intelligence⏱️ Timestamps[00:00] AI Timeline[00:22] AI Startups and Timing[06:30] GPT-3 Impact[13:24] Selling CodeGen to ClickUp[19:31] AI Interaction Patterns[28:41] Slack and AI Agents[36:11] ClickUp Task Automation[41:32] AI in Scientific Research[48:48] Human Understanding vs AI[54:18] Catastrophic Forgetting Explained[59:59] AI Delegating to Humans[1:05:00] Agent-Based Game Integration[1:08:42] LLM vs Game Design[1:11:27] Wrap up#AIAgents #AgenticAI #ClickUp

Sam Partee (CTO & co-founder of Arcade.dev) and Nate Barbettini (Founding Engineer at Arcade.dev) sit down at the MCP Dev Summit to unpack what nobody wants to admit about the Model Context Protocol: the security model is still full of sharp edges. From tool poisoning and prompt injection to why OAuth got bolted onto the spec, this is a builder 's-eye view of where MCP breaks — and how to ship agents safely anyway.What we get into:🔓 OAuth on MCP — Why the spec adopted OAuth as its authorization standard, and the class of spoofing attacks it shuts down.☠️ Tool poisoning — How a malicious server hides instructions in tool descriptions, and why your agent trusts them by default.🧪 MCP Debugger & ToolBench — Shining a light on the rough edges by grading servers from S-tier to F-tier.🖥️ Sandboxing agents — Giving an agent a shell and a file system without handing over the keys to your machine.📜 Allow lists — Why MCP has client-level allow lists but skills mostly don't — and why that worries them.🔄 The auto-update problem — How skills and servers that silently update become a supply-chain risk ("rug pulls").✅ SOC 2, honestly — Why the controls are voluntary, misunderstood, and actually about best practices.🤖 AI-generated PRs — The new behaviors to watch for as agents start writing and merging code.If you build agents, ship MCP servers, or are responsible for AI security at your company, this one's for you.🔗 Links & ResourcesArcade.dev: https://www.arcade.devArcade MCP framework (GitHub): https://github.com/ArcadeAI/arcade-mcpSam Partee (GitHub): https://github.com/sparteeNate Barbettini (LinkedIn): https://www.linkedin.com/in/nbarbettiniMLOps.community: https://mlops.community⏱️ Timestamps[00:00] Skills, agents, and local context[08:36] MCP Debugger grades your server[10:34] Why AI clients are still buggy[20:54] Why agents shouldn’t always have shell access[22:44] “I have a spicy take.”[26:27] “Do not build your own auth.”[31:14] The “checking someone else’s email” problem[35:40] “OAuth is the best worst option.”[43:50] The future of AI entertainment[46:19] Tool poisoning explained[50:49] “Trust me, bro,” is not a security solution[52:45] MCP registries as the App Store model[1:00:28] AI-generated PRs and speed vs quality[1:02:37] Why behavior-driven development is coming back[1:08:11] Have we already reached AGI?#MCP #AIAgentSecurity #ToolPoisoning

Shahram Anver is the Co-Founder and CEO of Cleric, the autonomous AI SRE that investigates and root-causes production issues like an experienced teammate — often in under two minutes. Before Cleric, Shahram led MLOps, DevOps, and FinOps platform engineering at Gojek, Southeast Asia's super-app. In this conversation, he breaks down why production operations never kept pace with AI-accelerated development, and why the real unlock for an AI SRE isn't faster triage — it's an agent that *learns* and compounds operational memory across your whole org.In this episode:🔧 The on-call problem — Why one broken service still drags ten engineers onto a call, and how AI changes that🤖 What an AI SRE actually is — How Cleric investigates across your existing observability stack instead of adding another tool🧠 Learning over MTTR — Why Shahram argues the value isn't alert triage, it's an agent that gets better every investigation🪜 Ramping like a new engineer — Explore the environment, learn from the work, talk to the team🔁 The investigate–measure–learn loop — Turning what worked on one incident into context for the next🕸️ Knowledge graphs & operational memory — Mapping teams, clusters, and dependencies so insight from one team helps another⚡ Under two minutes to root cause — What "fast" really requires in a live production environment🚀 The road to autonomy — From assisted investigation toward self-healing infrastructureIf you're an SRE, platform engineer, DevOps lead, or anyone building or buying AI agents for production, this one's for you.🔗 Links & ResourcesCleric: https://cleric.aiShahram on LinkedIn: https://www.linkedin.com/in/shahramanver/Willem Pienaar (Co-Founder/CTO): https://www.linkedin.com/in/willempienaar/Cleric launches the first self-learning AI SRE: https://cleric.ai/blog/cleric-launches-the-first-self-learning-ai-sreMLOps Community: https://mlops.communityJoin the community: https://go.mlops.community/slack⏱️ Timestamps[00:00] Tech Jargon Confusion[00:27] Harness vs Model[08:48] Model Evolution in Cleric[13:36] Sandboxing and Simulated Environments[20:40] Shifting AI Perceptions[24:10] Managing Humans vs Agents[31:32] Steering Parallel Agents[34:16] Human Decision Integration in Models[43:28] 80/20 Data Split[49:40] Becoming a Skill[53:35] 2027 Agent Autonomy[59:14] Agent Learning in Production[1:04:31] Software as Personal Capabilities[1:08:31] Vibe Coding vs Durability[1:18:23] Wrap up#AISRE #SiteReliabilityEngineering #AIAgents

Zipline Roundtable episode: Building Real-Time ML Systems with Zipline + ChrononJoin the Community: https://go.mlops.community/YTJoinInGet the newsletter: https://go.mlops.community/YTNewsletterMLOps GPU Guide: https://go.mlops.community/gpuguideBig shout-out to ZiplineAI for the collaboration!// AbstractReal-time ML use cases like personalization and risk decisioning come with a unique set of challenges: serving fresh feature values at low latency for inference, generating temporally consistent backfills for training, and building complex chains of on-demand, batch, and streaming transformations. In this roundtable, practitioners from Intuit, CreditKarma, Depop, and OpenAI share how they use Zipline and the OSS Chronon project to solve these challenges and deploy real-time ML use cases in production.// BioGerman KrikorianGerman is a Software Engineer on the Feature Platform team at Credit Karma. Since joining the company during the early development of its recommendation system, they have played a key role in building and scaling the platform over the years. Their work focuses on feature pipelines and the feature store, which serves as critical infrastructure supporting numerous teams and business verticals across the organization.Ben MagyarBen is an engineer at Depop working on ML and data systems. Before Depop, he worked on Search at Etsy. Most of his work is around the infrastructure and operational problems that come with running ML systems at scale.Raj KatakamRaj architects ML Infrastructure at Credit Karma (Intuit). He holds a Master's in Software Engineering from Carnegie Mellon and a B.Tech in EECE from IIT Kharagpur. His interests include ML Infrastructure, Distributed Systems, Real-Time Data Processing, and Generative AI. His current focus is on providing feature engineering platforms, production GenAI infrastructure, vector databases, ML model serving, and MLOps pipelines for fraud detection, personalized recommendations, financial insights, and model explainability.Mick JermsurawongLed Flyte ML training/experimentation at Stripe, and now led Chronon for ML features at OpenAIHosted by Demetrios// Related LinksWebsite: https://zipline.ai/https://chronon.ai/~~~~~~~~ ✌️Connect With Us ✌️ ~~~~~~~Catch all episodes, blogs, newsletters, and more: https://go.mlops.community/TYExploreJoin our Slack community [https://go.mlops.community/slack]Follow us on X/Twitter [@mlopscommunity](https://x.com/mlopscommunity) or [LinkedIn](https://go.mlops.community/linkedin)] Sign up for the next meetup: [https://go.mlops.community/register]MLOps Swag/Merch: [https://shop.mlops.community/]Connect with Demetrios on LinkedIn: /dpbrinkmConnect with German on LinkedIn: /e2zdkwh8cxghydg/Connect with Raj on LinkedIn: /rajkiran2190Connect with Mick on LinkedIn:/mick-jermsurawong/

Naseem Al-Naji is the co-founder of MCPcat.io and the creator of Opal — a builder with deep roots in privacy-first developer tooling. In this conversation, he breaks down why MCP servers have become a black box in production, and how MCPcat gives teams X-ray vision into how agents and users actually behave.What we get into:🐱 What MCPcat Is — Open-source analytics and live debugging built specifically for MCP servers🎬 Session Replay — Watch an agent's full journey through your server, tool call by tool call🎯 Agent Intent & Goals — Understand "why" a tool was called, not just that it was🔍 Trace Debugging — Find exactly where agents and users get stuck or confused🚨 Catching Hallucinations — How issue tracking surfaces when an LLM goes off the rails🔒 Privacy-First by Design — Client-side redaction so sensitive data never leaves your environment⚡ One-Line Integration — Python, TypeScript, and Go SDKs that drop into existing stacks📊 Works With Your Stack — Native support for OpenTelemetry, Datadog, and Sentry🚀 The Future of MCP — Where agent observability and the MCP ecosystem are headingIf you build, ship, or maintain MCP servers — or you're trying to figure out why your AI agents misbehave in production — this one's for you.🔔 Subscribe, like, and share for more conversations on agentic AI:▶️ YouTube: https://www.youtube.com/@AAIFAgenticConversations🎧 Spotify: https://open.spotify.com/show/033rZZJrQOVSSmhcStFhZA?si=rUNjFuNqRvGvAEWwqms7TALinks & Resources:🐱 MCPcat: https://mcpcat.io💻 MCPcat on GitHub: https://github.com/mcpcat👤 Naseem on LinkedIn: https://www.linkedin.com/in/naseem-al-naji🐙 Naseem on GitHub: https://github.com/naji247Timestamps:[00:00] Intro[01:41] MCP Needs Gatekeepers[06:32] Measuring MCP Success[13:57] MCPAT Feature Rollouts[18:50] MCP Server Query Optimization[26:48] UI Design Shift[29:14] MCP Server Design Choices[33:51] User Journey Traceability[40:40] Agent Experience Evaluation[45:23] AI Model Improvement Strategies#MCP #AIAgents #Observability

Stanislas Polu is Co-Founder & CTO of Dust — the enterprise AI agent platform used by 51,000 workers at 3,000+ companies. Before Dust, he spent three years on OpenAI's research team under Ilya Sutskever, working on mathematical reasoning in language models, and prior to that was an engineer at Stripe. He brings a rare combination of frontier AI research and product-building experience to the enterprise agent space.Agents & the $40M Bet on Multiplayer AI // MLOps Podcast #384 with Stanislas Polu, Co-Founder & CTO of Dust🤖 What is Dust? — How Dust enables teams to build and deploy AI agents powered by internal company data, and why the "multiplayer AI" model is winning in enterprise.🧠 From OpenAI Research to Startup Founder — Stanislas's journey from studying mathematical reasoning in LLMs under Ilya Sutskever to co-founding an enterprise AI company in Paris with Gabriel Hubert.🚀 The $40M Series B — What Dust is building with fresh funding, the bet on human-agent collaboration as the future of work, and what "multiplayer AI" actually means in practice.🔄 The Outer-Loop Era — Stanislas's framework for thinking about where AI agents create the most value: not just automating tasks, but rewiring how work gets done across entire organizations.⚠️ What Most Enterprise AI Gets Wrong — The biggest mistakes companies make when deploying AI agents, why adoption fails, and how Dust achieves 70%+ weekly adoption rates.📊 Building Reliable Agent Infrastructure — Lessons from scaling to thousands of companies: observability, governance, data security, and why enterprise AI is harder than it looks.🛠️ Horizontal vs. Vertical AI Platforms — Why Dust chose to build a horizontal enterprise agent platform and how that decision shapes product, go-to-market, and technical architecture.This episode is essential for AI/ML engineers, enterprise AI leads, and anyone building or deploying AI agents at scale inside organizations.🔗 Links & Resources:• Dust: https://dust.tt• Stanislas Polu on X/Twitter: https://x.com/spolu• Dust on LinkedIn: https://www.linkedin.com/company/dust-tt• Dust $40M Series B announcement: https://dust.tt/blog• "The Outer-Loop Era" talk by Stanislas (dotconferences): https://www.youtube.com/watch?v=_outer_loop• Dust + Stripe MCP integration: https://stripe.com/customers/dust• Dust + Datadog observability case study: https://datadoghq.com/case-studies/dust⏱️ Timestamps [00:00] Future of Work[00:19] Dust Scaling Lessons[04:44] Human-Agent Collaboration[14:24] Pod as Workspace[22:30] Work Flow Optimization[29:37] Multiplayer Collaboration Vision[39:55] Token Economics and Inference[47:20] AI Pricing Challenges[52:36] Dust vs Co-work[57:06] Agentic Work Infrastructure[1:04:23] Stateful Sandbox Challenges[1:09:58] Product Use Case Discussion[1:14:05] Agent Data Interaction Needs[1:20:09] Wrap up#EnterpriseAI #AIAgents #Dust

James Everingham is the CEO and Co-founder of Guild.ai — the AI agent control plane for production teams. With roots at Netscape, Instagram (Head of Engineering), and Meta (Head of Dev Infra, leading a 1,000-person org), James brings rare, hard-won expertise to the challenge of operating AI agents at scale.From Single-Player to Multi-Player: Operating AI Agents at Scale // MLOps Podcast #383 with James Everingham, CEO and Co-founder of Guild.aiIn this episode, James unpacks what actually breaks when you move from a single AI agent to a fleet of them — and what engineering leaders need to build before it's too late.🎯 Single-Agent vs. Multi-Agent Systems — Why "single-player" AI workflows don't survive contact with production reality, and what the shift to multi-agent coordination actually demands from your infrastructure.🔍 The Agent Control Plane — What it is, why every engineering org needs one in 2026, and how Guild.ai is building the neutral layer to deploy, govern, and share agents across any framework or model.⚠️ Non-Determinism at Scale — Why AI agents behave like employees, not software, and why you need workforce-style governance — not just observability tooling — to manage them.💸 Token Spend & Cost Visibility — How teams running agents in production are flying blind on cost, and what Guild shows you that your current stack doesn't.🏗️ Lessons from Meta's DevMate — How Meta's AI coding agent went from experiment to submitting 50% of all diffs, and what that journey teaches every engineering leader about scaling agents safely.🚦 Agent Identity & Governance — Why every agent needs an identity, what happens when they don't have one, and how agent sprawl becomes a governance crisis fast.🔄 Sharing Agents as Infrastructure — Why Guild treats agents as shared production infrastructure rather than one-off scripts, and how that changes the economics of AI investment.🛠️ Framework Agnosticism — Why betting on a single agent framework is a losing strategy, and how to build for a multi-model, multi-framework world from day one.Essential viewing for engineering leaders, AI platform teams, and founders building production-grade agentic systems.🔗 Guild.ai: https://guild.ai🔗 James on X/Twitter: https://x.com/jevering🔗 James on LinkedIn: https://www.linkedin.com/in/jameseveringham🔗 Demetrios on LinkedIn: https://www.linkedin.com/in/dpbrinkm/⏱️ Timestamps [00:00] Context Transfer Challenges[00:51] Control Plane for Agents[02:17] Effective Agent Policies[09:23] Agent Governance Policies[15:34] Developer Tool Adoption[22:02] Knowledge Sharing and Open Source[24:59] Simulated Deployments and Confidence[29:36] Agent Workloads vs Human Workloads[39:55] AI as a Customer[47:59] Agent Hub vs Autonomy[53:21] Wrap up#AgenticAI #AIAgents #AIEngineering