Skip to content

Conversation

tpaulshippy
Copy link
Contributor

@tpaulshippy tpaulshippy commented Aug 6, 2025

What this does

As explained here there are numerous reasons to use the newer Responses API instead of the Chat Completions API. Features we get by switching include:

  1. Mixing web search with custom tools
  2. Conversations with images in and out
  3. Certain models like o4-mini-deep-research
  4. MCP support through OpenAI

There is one feature not yet available - audio inputs are not supported by the Responses API. So, the library will detect any audio inputs and fall back to the Chat Completions API if they exist.

Type of change

  • New feature

Scope check

  • I read the Contributing Guide
  • This aligns with RubyLLM's focus on LLM communication
  • This isn't application-specific logic that belongs in user code
  • This benefits most users, not just my specific use case

Quality check

  • I ran overcommit --install and all hooks pass
  • I tested my changes thoroughly
  • I updated documentation if needed
  • I didn't modify auto-generated files manually (models.json, aliases.json)

API changes

  • No API changes

Related issues

Replaces #290
Should enable resolution of #213

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Being fully transparent - claude-4-sonnet handled most of the changes to this file in particular. Deserves some extra 👀.

…e had

Getting this:
ruby(19317,0x206ace0c0) malloc: Double free of object 0x10afc39e0
ruby(19317,0x206ace0c0) malloc: *** set a breakpoint in malloc_error_break to debug
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants