Bret Taylor: Open-source AI is chaotic and unpolished, harness engineering is key for efficient development, and emotional attachment to code hinders growth | Cheeky Pint

AI agents are set to revolutionize customer service by replacing outdated systems and enhancing user experience.

Listen on Cheeky Pint

Share

Add us on Google by Editorial Team Mar. 25, 2026

Key takeaways

• Open-source AI projects are currently in a chaotic state, reflecting the broader consumer AI landscape.
• The intricate details of engineering are where the real challenges lie, particularly in coding environments.
• Harness engineering, which leverages existing code bases, is an efficient method for developing general-purpose AI agents.
• Software engineers’ emotional attachment to code can impede their growth and adaptation to new technologies.
• Multi-agent systems often lack the necessary context, leading to robotic-sounding interactions.
• The future of web applications might prioritize harnessing user expertise over traditional API usage.
• A harness framework can help users maximize the value from services like Stripe, beyond just API interaction.
• Product management might evolve to focus more on enabling agents to manipulate dashboards rather than UI design.
• Enterprise software design often falls short when compared to consumer-focused applications.
• AI agents have the potential to significantly enhance customer experience by replacing traditional systems like IVR.
• The development of AI technologies is marked by a contrast between polished consumer applications and chaotic open-source projects.
• Coding environments are uniquely structured to support the automation of digital tasks.
• The role of software engineers is evolving, requiring a shift away from emotional attachment to code.

Guest intro

Bret Taylor is co-founder and CEO of Sierra, an AI agent company focused on transforming customer service, and serves as Chairman of the OpenAI board. He previously served as co-CEO of Salesforce and led the team that created Google Maps at Google. His experience spanning product management, engineering, and executive leadership across Meta, Twitter, and multiple startups positions him at the forefront of AI’s impact on enterprise software and business models.

The chaotic state of open-source AI projects

• The chaotic development of open-source AI projects reflects the current state of consumer AI.

  — Bret Taylor

• Open-source projects often lack the polish seen in consumer AI applications.

• I love everything about the chaos of it just because all people in our circles have been talking about AI agents for consumer use.

  — Bret Taylor

• There’s a stark contrast between the usability of open-source projects and consumer applications.
• The chaotic nature of these projects highlights the evolving landscape of AI technology.
• Open-source AI projects serve as a testing ground for new ideas and innovations.

• Instead you’re chatting over WhatsApp with a thing on a Mac mini that’s mildly unhinged and insecure.

  — Bret Taylor

• The disparity in development reflects the broader challenges in consumer AI.

The unique challenges of coding environments

• The hard part of engineering lies in the details, and coding environments are uniquely structured to support automated agents.

  — Bret Taylor

• Coding environments provide specific qualities that facilitate automation.

• You can actually it’s almost designed for a robot.

  — Bret Taylor

• The structure of coding environments offers feedback mechanisms distinct from other digital tasks.
• These environments highlight the challenges and intricacies of engineering work.
• Automation in coding is supported by the unique characteristics of these environments.
• Understanding these environments is crucial for developing effective automated agents.
• The details in coding environments present unique challenges for engineers.

Harness engineering in AI development

• Harness engineering is an efficient way to build general-purpose agents by mimicking existing code bases.

  — Bret Taylor

• Mimicking code bases is a practical approach for developing AI agents.
• This method may be an idiosyncratic but effective way to create general-purpose agents.

• Maybe over time we’ll get fancier than that but it’s actually like a relatively efficient harness for an agent.

  — Bret Taylor

• Harness engineering leverages existing resources for efficient AI development.
• The approach highlights the importance of practical solutions in AI innovation.
• Understanding harness engineering is key to grasping current AI development trends.
• This method reflects a broader trend of using existing structures to build new technologies.

Emotional attachment to code in software engineering

• The emotional attachment to code can hinder a software engineer’s growth.

  — Bret Taylor

• Engineers often take pride in the elegance of their code, which can be limiting.

• What I’m trying to do is force myself to not be emotionally attached to the code.

  — Bret Taylor

• Adapting to new tools and methodologies requires a shift in mindset.
• Emotional attachment can prevent engineers from embracing new technologies.
• The evolving role of engineers necessitates detachment from traditional coding practices.
• Growth in the field requires overcoming emotional ties to one’s work.
• This shift is part of a broader change in the technological landscape.

The importance of context in multi-agent systems

• Multi-agent systems require a significant amount of context to function effectively, which is often lacking in traditional architectures.

  — Bret Taylor

• Context is crucial for improving user experience in AI systems.

• You stuff all the context in the sub agents and the one on top has no ability to actually like not sound robotic.

  — Bret Taylor

• Current architectures often fall short in providing necessary context.
• The lack of context leads to robotic-sounding interactions in multi-agent systems.
• Addressing this challenge is key to advancing AI design.
• Understanding the limitations of current architectures is crucial for improvement.
• Enhancing context in AI systems can significantly improve user interactions.

The future of web applications and harnessing expertise

• The future of web applications may shift towards a model that emphasizes harnessing knowledge and expertise over traditional APIs.

  — Bret Taylor

• User expertise may become more important than API usage in web applications.

• We do have an agent harness and what I mean by that is something more than the APIs.

  — Bret Taylor

• This shift highlights the evolving role of user interaction in technology.
• Web applications may prioritize frameworks that enhance user expertise.
• The evolution of web applications reflects broader changes in technology usage.
• Understanding this shift is crucial for future web application development.
• The role of APIs may change as user expertise becomes more central.

The role of harness frameworks in maximizing value

• A harness provides a framework for users to maximize the value they extract from a service like Stripe, beyond just using the API.

  — Bret Taylor

• A harness framework offers guidance for effective software utilization.

• Here’s the instruction manual for all the unix commands that power… Stripe.

  — Bret Taylor

• This approach emphasizes the importance of user understanding in software use.
• Maximizing value from services requires more than just API interaction.
• Harness frameworks provide a comprehensive understanding of available tools.
• This approach is crucial for effective software application use.
• Understanding harness frameworks is key to leveraging technology effectively.

The evolving role of product management with AI agents

• The future of product management may involve adding switches to dashboards that agents can manipulate, rather than focusing solely on UI design.

  — Bret Taylor

• Product management may prioritize enabling agent interaction over traditional design.

• Imagine being a product manager in the future you just need to add the switch to the dashboard.

  — Bret Taylor

• This shift reflects the growing role of AI agents in software applications.
• The focus may move from UI design to facilitating agent manipulation.
• Understanding this change is crucial for future product management strategies.
• The role of product managers may evolve alongside advancements in AI technology.
• This shift highlights the impact of AI on traditional software roles.

The design gap between enterprise and consumer software

• The design of enterprise software is often lacking compared to consumer-focused applications.

  — Bret Taylor

• Enterprise software design often prioritizes functionality over elegance.

• Most enterprise software you can’t say that about their dashboard.

  — Bret Taylor

• Consumer applications typically offer better design and user experience.
• This gap highlights differences in design philosophy between the two types of software.
• Improving enterprise software design is crucial for enhancing user experience.
• Understanding these differences can inform future software design strategies.
• The design gap affects both functionality and user satisfaction in enterprise software.

AI agents enhancing customer experience

• AI agents can significantly enhance customer experience by replacing traditional systems like IVR.

  — Bret Taylor

• Replacing IVR systems with AI agents can improve customer interactions.

• If you have a big phone line these ai agents can replace your ivr system and just pick up the phone.

  — Bret Taylor

• AI agents offer a more efficient alternative to traditional customer service systems.
• The transformative potential of AI agents lies in their ability to streamline interactions.
• Understanding the role of AI in customer service is crucial for modern businesses.
• AI agents can reduce wait times and improve overall customer satisfaction.
• This enhancement reflects broader trends in AI’s impact on traditional systems.

Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.