langchain-ai/docs
1
0
Fork 0
mirror of https://github.com/langchain-ai/docs.git synced 2026-07-21 11:55:23 -04:00
Code Issues 490 Packages Projects Releases Wiki Activity

[PR #3733] docs(deepagents): OpenAI Responses API and data retention on Models page #3760

New Issue
Open
opened 2026-06-05 18:53:03 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 18:53:03 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/3733
Author: @AdemBoukhris457
Created: 4/25/2026
Status: 🔄 Open

Base: main ← Head: docs/deepagents-openai-retention-models

📝 Commits (1)

  • 22c0d6e docs(deepagents): document OpenAI Responses retention on Models page

📊 Changes

1 file changed (+39 additions, -0 deletions)

View changed files

📝 src/oss/deepagents/models.mdx (+39 -0)

📄 Description

Add "OpenAI and the Responses API" to models.mdx: default Responses path for openai: strings, Chat Completions via use_responses_api=False, and store=False + include=["reasoning.encrypted_content"] with a pre-built model instance. Aligns with create_deep_agent docstring; JS points to OpenAI chat integration.

Overview

Documents Deep Agents behavior for OpenAI models on the Models page: Responses API as the default for openai:... strings, how to switch to Chat Completions with a pre-initialized model, and how to opt out of data retention on Responses while keeping encrypted reasoning output (store=False, include=["reasoning.encrypted_content"]). Clarifies that OpenAI-specific kwargs require passing a configured model instance, not only a provider string. TypeScript readers are directed to the OpenAI chat integration for equivalent options.

Type of change

Type: Update existing documentation

Related issues/PRs

  • GitHub issue: closes #3732
  • Feature PR:
  • Linear issue:
  • Slack thread:

Checklist

  • I have read the contributing guidelines, including the language policy
  • I have tested my changes locally using docs dev
  • All code examples have been tested and work correctly
  • I have used root relative paths for internal links
  • I have updated navigation in src/docs.json if needed

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langchain-ai/docs/pull/3733 **Author:** [@AdemBoukhris457](https://github.com/AdemBoukhris457) **Created:** 4/25/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `docs/deepagents-openai-retention-models` --- ### 📝 Commits (1) - [`22c0d6e`](https://github.com/langchain-ai/docs/commit/22c0d6e9d8c1d57d4eeff5961cc038e4c129d86b) docs(deepagents): document OpenAI Responses retention on Models page ### 📊 Changes **1 file changed** (+39 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/oss/deepagents/models.mdx` (+39 -0) </details> ### 📄 Description Add "OpenAI and the Responses API" to models.mdx: default Responses path for openai: strings, Chat Completions via use_responses_api=False, and store=False + include=["reasoning.encrypted_content"] with a pre-built model instance. Aligns with create_deep_agent docstring; JS points to OpenAI chat integration. ## Overview Documents Deep Agents behavior for OpenAI models on the [Models](/oss/deepagents/models) page: Responses API as the default for `openai:...` strings, how to switch to Chat Completions with a pre-initialized model, and how to opt out of data retention on Responses while keeping encrypted reasoning output (`store=False`, `include=["reasoning.encrypted_content"]`). Clarifies that OpenAI-specific kwargs require passing a configured model instance, not only a provider string. TypeScript readers are directed to the OpenAI chat integration for equivalent options. ## Type of change **Type:** Update existing documentation ## Related issues/PRs - GitHub issue: closes #3732 - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist - [x] I have read the [contributing guidelines](README.md), including the [language policy](https://docs.langchain.com/oss/python/contributing/overview#language-policy) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-05 18:53:03 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
deepagents
docs-infra
external
external
help wanted
integration
internal
internal
javascript
js/ts
langchain
langgraph
langsmith
needs-title
pull-request
Mirrored from GitHub Pull Request
 python
reference
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/docs#3760
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?