Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
76 changes: 38 additions & 38 deletions reference/python/uv.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion src/oss/langchain/models.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -1048,7 +1048,7 @@ Models can be requested to provide their response in a format matching a given s
- **Method parameter**: Some providers support different methods (`'json_schema'`, `'function_calling'`, `'json_mode'`)
- `'json_schema'` typically refers to dedicated structured output features offered by a provider
- `'function_calling'` derives structured output by forcing a [tool call](#tool-calling) following the given schema
- `'json_mode'` is a precursor to `'json_schema'` offered by some providers- it generates valid json, but the schema must be described in the prompt
- `'json_mode'` is a precursor to `'json_schema'` offered by some providers - it generates valid json, but the schema must be described in the prompt
- **Include raw**: Use `include_raw=True` to get both the parsed output and the raw AI message
- **Validation**: Pydantic models provide automatic validation, while `TypedDict` and JSON Schema require manual validation
</Note>
Expand Down
2 changes: 1 addition & 1 deletion src/oss/langchain/structured-output.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ const agent = createAgent({

## Provider strategy

Some model providers support structured output natively through their APIs (currently only OpenAI and Grok). This is the most reliable method when available.
Some model providers support structured output natively through their APIs (e.g. OpenAI, Grok, Gemini). This is the most reliable method when available.

To use this strategy, configure a `ProviderStrategy`:

Expand Down
4 changes: 2 additions & 2 deletions src/oss/langgraph/add-memory.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -1396,8 +1396,8 @@ const deleteMessages = (state) => {
<Warning>
When deleting messages, **make sure** that the resulting message history is valid. Check the limitations of the LLM provider you're using. For example:

* some providers expect message history to start with a `user` message
* most providers require `assistant` messages with tool calls to be followed by corresponding `tool` result messages.
* Some providers expect message history to start with a `user` message
* Most providers require `assistant` messages with tool calls to be followed by corresponding `tool` result messages.
</Warning>

<Accordion title="Full example: delete messages">
Expand Down
Loading