2025 is the “Year of the Agent”, OpenAI is heads down building towards it. In the fi">

Latent Space: The AI Engineer Podcast

⚡️The new OpenAI Agents Platform

Overview

Content

OpenAI API Launch and New Tools

* Web search tool (similar to ChatGPT for search) * Improved file search tool * Computer use tool (from ChatGPT Operator product)

* Designed to support more complex, multi-turn agentic workflows * Aims to unify functionality from chat completions and assistance API * Simplifies tool integration for developers * Will support everything chat completions and assistance APIs currently support * Offers a stateless mode (by passing store=false) * Stores conversation state for free for 30 days * Provides visual debugging and observability in dashboard

* Chat completions API is NOT going away - Will continue to be maintained - Optimized for earlier, simpler text-based interactions * Assistance API has a planned sunset date in first half of 2026 * OpenAI will provide: - Smooth migration path - Full year for developers to transition - Additional features like assistant objects and thread-like objects - Future additions of code interpreter tool and async mode

* New users should start with Responses API * Offers more capabilities and performance than chat completions * Chat completions will still be supported for years

Web Search Feature Details

* As a tool in Responses API * Direct access to fine-tuned search model (GPT-4o Search Preview) in chat completions

* Accuracy increased from 38% to 90% in simple QA * Search team focused on: - Gathering information from multiple data sources - Selecting and citing information accurately - Using synthetic data and model distillation techniques

* Can be combined with other tools like function calling and structured outputs * Allows for real-time data structuring from web sources * Provides citations from web sources * Comparable to similar APIs from Perplexity and Gemini

* Knowledge cutoff varies depending on use case * Currently no built-in parameter for search depth/breadth * Potential for agent orchestration to explore deeper search layers * Cost is approximately $30 per 1,000 queries * Potential strategies for managing search costs include: - Context budget approach - Similarity matching cut-offs - Storing search results in files to avoid repeated searches

* Companies like Hebea using web search for accessing public information * Potential for storing user preferences/memories in vector stores

File Search Enhancements

* Can be used to find personalized recommendations based on user preferences * Combining with neural networks and real-time internet access enables precise, context-aware answers * Allows integration of private company documents with AI systems * Can be combined with web search for more dynamic information retrieval

* Expanding file type support * Query optimization * Custom re-ranking * Metadata filtering becoming available (critical for large vector stores)

* OpenAI offers an out-of-the-box file search solution with some customization options * Recommendation: Start with managed solution, then customize or switch to custom solution if needed * Some AI engineers prefer building their own vector database stack for more control

Computer Use/Operator Tool

* Interact with screen (click, scroll, type) * Complete multi-step tasks * Report back on actions * Uses screenshot inputs to determine actions

Model Development Strategy

Agents SDK Updates

* Types * Guard railing (parallel execution with blocking capability) * Tracing (viewable in OpenAI dashboard)

* Integration with any chat completions API provider * Multiple tracing provider support

* Originated from customer feedback about agent orchestration challenges * Enables more modular agent design with easier monitoring * Supports creating triage agents that route to different specialized agents

Troubleshooting and Improving Agentic Workflows

* Ability to trace workflow steps between agents * Visualizing tool calls and handoffs between different agents * Helping developers build more effective AI agent systems

* Connecting traces to evaluation (evals) products * Using traces to generate better evaluations * Potentially implementing reinforcement fine-tuning based on those evaluations

More from Latent Space: The AI Engineer Podcast

Explore all episode briefs from this podcast

View All Episodes →

Listen smarter with PodBrief

Get AI-powered briefs for all your favorite podcasts, plus a daily feed that keeps you informed.

Download on the App Store