> Markdown version of [/videos/2033-guiding-agentic-ai-with-vue](https://www.wearedevelopers.com/videos/2033-guiding-agentic-ai-with-vue). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Guiding Agentic AI with Vue The next generation of agentic software won't rely on ubiquitous chatboxes. Learn how to map AI intent directly to Vue components using Pinia and the Vercel AI SDK. - **Speakers:** [Rijk van Zanten](https://www.wearedevelopers.com/@rijk-van-zanten) - **Event:** World Congress 2026 Europe - Virtual Stage - **Published:** July 2, 2026 - **Duration:** 31:18 - **URL:** https://www.wearedevelopers.com/videos/2033-guiding-agentic-ai-with-vue ## Summary Integrating agentic AI transforms basic chat interfaces into capable assistants that perform real tasks within an application. By treating AI tools as simple, descriptive functions, developers can bridge the gap between large language models and practical UI execution. This integration naturally splits into background server agents for rapid execution and foreground client agents that explicitly demonstrate workflows to the user—turning complex application navigation into a guided, observable onboarding experience. Implementing client-side agentic tooling elegantly aligns with the Vue component lifecycle. Using a centralized Pinia store combined with custom composables ensures the AI only interacts with the UI elements currently rendered and active on the screen. Coupling this architecture with tools like the Vercel AI SDK allows the model to map intent directly to interface capabilities. Furthermore, continually passing the current UI state to the LLM's context window essentially removes its blindfold, enabling context-aware actions rather than naive guesses. Elevating these capabilities from a gimmick to a reliable feature requires rigorous tool design. Developers should approach tool descriptions as if "writing docs for what is effectively a literal junior developer," relying heavily on precise, single-purpose names and explicit success or error returns to maintain the agentic loop. Destructive actions demand built-in guardrails, pausing autonomous execution to render explicit human confirmation steps. As applications mature, engineering teams must adapt to the inherent testing challenges of probabilistic models, pivoting toward behavioral end-state assertions rather than rigid step-by-step checks. Ultimately, the next generation of agentic software will shed the ubiquitous chatbox entirely, embedding this deterministic tool-calling infrastructure invisibly behind context menus and native application interfaces. **Keywords:** agentic ai integration, vue component lifecycle mapping, llm function calling, pinia state management, vercel ai sdk implementation, client-side ui automation, ai tool design principles, destructive action guardrails, non-deterministic behavioral testing, system prompt engineering, context-aware ai assistants, background vs foreground agents, virtual cursor onboarding, frontend ai architecture, autonomous workflow execution ## Chapters 1. **Defining agentic AI and the tool execution architecture** (00:00) — Providing LLMs access to specific executable tools enables them to modify data and trigger real-world application workflows. 1. **Comparing background and foreground agent interactions in apps** (04:05) — Choosing between background and foreground tool execution determines whether the AI acts silently or explicitly demonstrates interaction steps. 1. **Registering and scoping client-side tools in Vue components** (08:55) — Managing tool states through state libraries and component lifecycles ensures the AI only accesses visible user interface elements. 1. **Passing registered UI tools to the LLM chat object** (12:18) — Supplying the registered tool store to the AI provider bridges the gap between client interactions and model capabilities. 1. **Designing explicit AI tools with precise schemas and results** (13:29) — Creating well-named tools with specific return values and clear error messages helps the model successfully navigate task failures. 1. **Syncing current UI state and context to the LLM** (17:42) — Supplying contextual data like selected items prevents the model from acting blindly without situational or spatial awareness. 1. **Managing tool permissions and user approval workflows** (19:05) — Implementing confirmation steps for destructive actions builds necessary guardrails while avoiding excessive notification fatigue for the end user. 1. **Crafting system prompts as AI behavioral specifications** (21:33) — Writing precise system prompts acts as a primary design surface to dictate when the model uses specific interaction methods. 1. **Navigating tool latency and integration testing challenges** (24:20) — Integrating agentic capabilities introduces architectural complexities around tool explosion, visible interface latency, and non-deterministic software testing. 1. **Evolving beyond chat windows for contextual agentic interfaces** (28:33) — Embedding contextual AI actions directly into standard components offers a more cohesive and intuitive alternative to isolated chat boxes. ## Related Moments - [Audience Q&A on tooling choices and AI application prototyping](https://www.wearedevelopers.com/videos/100195-xcode-development-redefained) (from "Xcode development redefAIned") - [Key takeaways for integrating agentic UI in web applications](https://www.wearedevelopers.com/videos/100074-generative-uis-and-ai-assistants-for-your-angular-applications) (from "Generative UIs and AI Assistants for Your Angular Applications") - [The evolution of AI programming and agentic workflows](https://www.wearedevelopers.com/videos/100032-under-the-hood-of-building-on-lovable) (from "Under the Hood of Building on Lovable") - [Enhancing conversational intent through modern large language models](https://www.wearedevelopers.com/videos/1641-hello-jarvis-building-voice-interfaces-for-your-llms) (from "Hello JARVIS - Building Voice Interfaces for Your LLMS") - [Summarizing developer experience and artificial intelligence companions](https://www.wearedevelopers.com/videos/884-forget-developer-platforms-think-developer-productivity) (from "Forget Developer Platforms, Think Developer Productivity!") - [Evaluating AI tooling and design platforms for developers](https://www.wearedevelopers.com/videos/1340-wearedevelopers-live-performance-and-ai-social-media-decline-developer-events-and-more) (from "WeAreDevelopers LIVE - Performance and AI?, Social Media decline, Developer Events and more") ## Related Articles - [What is Agentic Programming and Why Should Developers Care?](https://www.wearedevelopers.com/magazine/625-what-is-agentic-programming-and-why-should-developers-care) - [WWC24 Talk - Scott Hanselman - AI: Superhero or Supervillain?](https://www.wearedevelopers.com/magazine/469-wwc24-talk-scott-hanselman-ai-superhero-or-supervillain) - [Exploring AI: Opportunities and Risks for Developers](https://www.wearedevelopers.com/magazine/522-exploring-ai-opportunities-and-risks-for-developers) - [Never delegate the understanding](https://www.wearedevelopers.com/magazine/749-never-delegate-the-understanding) ## Related Jobs - [AI Software Engineer (Germany)](https://www.wearedevelopers.com/jobs/48317-ai-software-engineer-germany) at **Sunhat** - [AI Full Stack Engineer](https://www.wearedevelopers.com/jobs/ext/1354435-ai-full-stack-engineer) at **Almedia** - [Staff Software Engineer, Copilot Experiences](https://www.wearedevelopers.com/jobs/ext/164361-staff-software-engineer-copilot-experiences) at **GitHub** - [Senior AI Agent Software Engineer (Go, Python) (m/f/x)](https://www.wearedevelopers.com/jobs/48277-senior-ai-agent-software-engineer-go-python-m-f-x) at **Dynatrace** - [AI Operations Manager (all genders)](https://www.wearedevelopers.com/jobs/48263-ai-operations-manager-all-genders) at **envelio** - [Principal Product Manager, Agent Platform](https://www.wearedevelopers.com/jobs/ext/277541-principal-product-manager-agent-platform) at **GitHub**