Skip to content

Conversation

@ai13f
Copy link
Contributor

@ai13f ai13f commented Aug 13, 2025

Summary:

• Introduces new model entry GPT-5-mini with 128k context and 128k output limits
• Enables text+image input modality and text output
• Flags advanced capabilities: reasoning mode, tool calls, temperature control, attachments
• Sets metadata: release_date 2025-08-13, last_updated 2025-08-13, knowledge cutoff 2024-06
• Explicitly marks weights as closed (open_weights = false)

Details:

• Model identifier: GPT-5-mini
• Capabilities: attachment handling, reasoning enhancements, external tool invocation, adjustable temperature
• Modalities: input (text, image), output (text)
• Limits: 128,000 token context window, 128,000 token max generation

@thdxr thdxr merged commit 00f1cb6 into anomalyco:dev Aug 13, 2025
1 check passed
neilberkman added a commit to neilberkman/models.dev that referenced this pull request Nov 1, 2025
- Update schema to accept boolean OR object for tool_call
- Add streaming and coerces_types optional fields
- Update meta.llama3-3-70b-instruct-v1:0 as example
- Documents Bedrock streaming limitation and type coercion

Addresses provider-specific tool calling limitations documented in:
- AWS re:Post (streaming, type coercion issues)
- langchain-aws anomalyco#140, anomalyco#354
- pydantic-ai #1649

100% backward compatible at TOML level - existing tool_call = true/false still valid
neilberkman added a commit to neilberkman/models.dev that referenced this pull request Nov 1, 2025
- Update schema to accept boolean OR object for tool_call
- Add streaming, parallel, and coerces_types optional fields
- Update meta.llama3-3-70b-instruct-v1:0 as example
- Documents Bedrock streaming limitation and type coercion

Addresses provider-specific tool calling limitations:
- Streaming incompatibility (AWS Bedrock non-Anthropic models)
- Type coercion issues (Bedrock integer handling)
- Parallel tool calling tracking (addresses anomalyco#202)

Evidence:
- AWS re:Post: streaming errors, integer coercion
- langchain-aws anomalyco#140, anomalyco#354: streaming validation issues
- pydantic-ai #1649: response format problems
- req_llm: agentjido/req_llm#163

100% backward compatible at TOML level - existing tool_call = true/false still valid
neilberkman added a commit to neilberkman/models.dev that referenced this pull request Nov 1, 2025
- Update schema to accept boolean OR object for tool_call
- Add streaming, parallel, and coerces_types optional fields
- Update meta.llama3-3-70b-instruct-v1:0 as example
- Documents Bedrock streaming limitation and type coercion

Default semantics (do the least harm):
- streaming: undefined → true (matches current tool_call=true assumption)
- parallel: undefined → false (safer, not universally supported)
- coerces_types: undefined → false (most models work correctly)

Addresses provider-specific tool calling limitations:
- Streaming incompatibility (AWS Bedrock non-Anthropic models)
- Type coercion issues (Bedrock integer handling)
- Parallel tool calling tracking (addresses anomalyco#202)

Evidence:
- AWS re:Post: streaming errors, integer coercion
- langchain-aws anomalyco#140, anomalyco#354: streaming validation issues
- pydantic-ai #1649: response format problems
- req_llm: agentjido/req_llm#163

100% backward compatible at TOML level - existing tool_call = true/false still valid
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