The best of dev and AI, scored every day by an agent. Filtered, summarized, ranked. No color, no noise — just the substance.
Showing Sources In The Frontend outlines an evaluator-optimizer loop for LLM workflows and recommends displaying sources in the UI as card-like entries (favicon, title and snippet). It reframes the agent as a decision loop—answer when you have enough information, otherwise search—and adapts frontend patterns to present sources clearly.
Observability is essential when building AI-driven products. Day 3 teaches you to see and debug agent behavior using Langfuse, explore traces, and add custom trace metadata, then to build a time-aware web scraper tool to improve your DeepSearch agent.
That workshop reframes the agent as an evaluator-optimizer loop: one LLM call generates a response while another provides evaluation and feedback. It also covers showing sources in the frontend with a card-like UI (favicon, title, snippet) to surface provenance and improve traceability.
Ce workshop transforme un prototype de chatbot en expérience persistante: persistance des messages en streaming, création d’un chatId et routage vers /chat/:chatId, sauvegarde en DB et réhydratation de l’UI. Vous verrez comment router, revalider le sidebar et recharger les conversations de manière fiable.
Utiliser useChat de Vercel AI SDK permet de lancer rapidement un chatbot. Cette session montre comment transformer un prototype en chat persistant: endpoint POST /api/chat, enregistrement des messages avec Drizzle, routing par chatId et réhydratation de l’UI à partir de l’historique stocké. Vous obtiendrez une expérience end-to-end avec streaming, sauvegarde et rechargement des conversations.
Observability is crucial for AI-driven products since responses can drift. Day 3 shows how to see, debug, and improve agents using Langfuse, traces, and custom metadata, and to build a time-aware web scraper tool.
This workshop demonstrates how to turn a quick chat prototype into a persistent product by adding backend persistence, streaming updates, and robust routing. It covers building a POST /api/chat endpoint to stream OpenAI completions, persisting chats with Drizzle and returning a chatId, routing to /chat/:chatId, saving messages in real time while rehydrating the UI from the database.
Observability is essential when AI agents drift in production. Day 3 guides you through setting up Langfuse, exploring initial traces, and adding custom trace metadata, culminating in a time-aware web scraper tool to diagnose and improve your DeepSearch agent.
The article explains observability for AI agents using Langfuse, showing how to set up traces, view them, and attach custom trace metadata. It also covers implementing a time-aware web scraper tool to diagnose and improve a DeepSearch agent.
Ce workshop pousse à des défis avancés : créer une boucle évaluatrice-optimisatrice et afficher les sources côté frontend. La logique actuelle revient à un simple if/else : si l’IA a assez d’information, elle répond ; sinon elle lance une recherche. L’objectif est d’adopter le motif évaluation-optimisation et d’afficher les sources comme des cartes dans l’interface.
This workshop reframes the typical LLM agent as an evaluator-optimizer loop: one call generates a response while another evaluates it, then feedback guides the next step. It emphasizes moving logic from a pure agent to an evaluative loop and optimizes around it. It also covers displaying sources in the frontend as card-like items (favicon, title, snippet) to mirror DeepResearch patterns.
Day 6 teaches task decomposition and how to build modular loops for robust, optimizable AI. It helps you take control of your agent's logic and fix brittle LLM agents.
The workshop advances an evaluator-optimizer loop: the model answers when it has enough information and searches for the rest. It also covers displaying sources in the frontend as a card-like list (favicon, title, snippet). The practical goal is to implement an optional Ask Clarifying Questions step and reuse a frontend source-display pattern.
Day 3 montre comment observer et déboguer un agent IA en production grâce à l'observabilité et aux traces. Vous configurez Langfuse, explorez les premières traces et ajoutez des métadonnées de trace personnalisées, puis implémentez un outil de scraping temporel.
Day 3 focuses on observability for AI agents. It guides you to set up Langfuse, inspect traces, and add custom trace metadata to diagnose and improve your DeepSearch agent. By the end, you'll transform it from a mystery into a well-understood, diagnosable system.
Observability is crucial for AI-driven products; Day 3 covers seeing, debugging, and improving agents. You'll set up Langfuse, explore traces, and add custom trace metadata, then build a time-aware web scraper tool. By the end, your DeepSearch agent becomes understandable and deployable with confidence.
This workshop demonstrates turning a quick prototype with the Vercel AI SDK into a durable, persistent chat app. It covers streaming completions via a POST /api/chat endpoint, using Drizzle to create and return a chatId, saving messages as they stream, and rehydrating the UI while routing by chatId for seamless reloads.
Using Vercel AI SDK's useChat, this workshop guides turning a quick chat prototype into a persistent, streaming chat app. It covers streaming completions, creating/storing chat IDs, routing by chatId, and persisting messages in real time, plus rehydrating UI from the database and updating the sidebar via route revalidation. By the end you’ll have an end-to-end persistent chat experience with routing, saving, and reloading conversations.
In this workshop you'll tackle advanced challenges: an evaluator-optimizer loop and showing sources in the frontend. The description frames the system as an evaluator in a loop and proposes frontend source cards—favicon, title and snippet—similar to patterns in Anthropic's Building Effective Agents.
Dans ce workshop, on aborde des patterns avancés: une boucle évaluateur-optimiseur et l'affichage des sources côté frontend. L'agent devient une simple logique if-else et l'objectif est d'optimiser via une boucle d'évaluation, inspirée par Anthropic. On propose aussi d'afficher les sources sous forme de cartes dans l'UI pour plus de traçabilité.