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 #2702] [MERGED] feat: add thread read/unread behavior note for AB [closes DOC-746] #2807

New Issue
Closed
opened 2026-06-05 18:20:01 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 18:20:01 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/2702
Author: @lnhsingh
Created: 2/18/2026
Status: ✅ Merged
Merged: 2/18/2026
Merged by: @lnhsingh

Base: main ← Head: open-swe/296aa9ae-2f4b-281e-08cc-e10bc3806387

📝 Commits (2)

  • 235c3f8 Add thread read/unread behavior documentation for Agent Builder chat vs trigger-based agents
  • 86a5db0 Add Threads

📊 Changes

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

View changed files

📝 src/langsmith/agent-builder-essentials.mdx (+15 -0)

📄 Description

Description

Adds a new "Thread notifications" section to the Agent Builder essentials page
that documents how threads are marked as read/unread depending on the agent type.

This addresses a documentation gap where users had no reference for understanding
the default read/unread behavior of threads in Agent Builder:

  • Chat agents (no trigger): Responses are marked as unread by default, moving
    to read when the user views them.
  • Trigger-based agents: Responses are marked as read by default, remaining
    read for subsequent responses within the thread.
  • Both types allow the user to manually mark threads as unread at any time.

The section is placed in agent-builder-essentials.mdx right after the Triggers
section, since the behavior is directly tied to whether an agent uses triggers.

Resolves DOC-746

Test Plan

  • Verify the new "Thread notifications" section renders correctly in the Mintlify preview
  • Confirm the section appears between "Triggers" and "Skills" on the Essentials page
  • Verify no broken links or formatting issues are introduced

🔄 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/2702 **Author:** [@lnhsingh](https://github.com/lnhsingh) **Created:** 2/18/2026 **Status:** ✅ Merged **Merged:** 2/18/2026 **Merged by:** [@lnhsingh](https://github.com/lnhsingh) **Base:** `main` ← **Head:** `open-swe/296aa9ae-2f4b-281e-08cc-e10bc3806387` --- ### 📝 Commits (2) - [`235c3f8`](https://github.com/langchain-ai/docs/commit/235c3f86bb5e73e902439ca3a00f9784fb235182) Add thread read/unread behavior documentation for Agent Builder chat vs trigger-based agents - [`86a5db0`](https://github.com/langchain-ai/docs/commit/86a5db091da8624911470b294256972f9b68a56a) Add Threads ### 📊 Changes **1 file changed** (+15 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/langsmith/agent-builder-essentials.mdx` (+15 -0) </details> ### 📄 Description ## Description Adds a new "Thread notifications" section to the Agent Builder essentials page that documents how threads are marked as read/unread depending on the agent type. This addresses a documentation gap where users had no reference for understanding the default read/unread behavior of threads in Agent Builder: - **Chat agents (no trigger):** Responses are marked as unread by default, moving to read when the user views them. - **Trigger-based agents:** Responses are marked as read by default, remaining read for subsequent responses within the thread. - Both types allow the user to manually mark threads as unread at any time. The section is placed in `agent-builder-essentials.mdx` right after the Triggers section, since the behavior is directly tied to whether an agent uses triggers. Resolves DOC-746 ## Test Plan - [x] Verify the new "Thread notifications" section renders correctly in the Mintlify preview - [x] Confirm the section appears between "Triggers" and "Skills" on the Essentials page - [x] Verify no broken links or formatting issues are introduced --- <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:20:01 -04:00
yindo closed this issue 2026-06-05 18:20:01 -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#2807
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?