Skip to content

Conversation

@tanushree-sharma
Copy link
Contributor

@tanushree-sharma tanushree-sharma commented Jan 20, 2026

@github-actions github-actions bot added langsmith For docs changes to LangSmith internal labels Jan 20, 2026
@github-actions
Copy link
Contributor

Mintlify preview ID generated: preview-messag-1768875178-1bbe0c2

Copy link
Contributor

@katmayb katmayb left a comment

Choose a reason for hiding this comment

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

Couple of suggestions, but lgtm


- **A LangSmith account**: Sign up or log in at [smith.langchain.com](https://smith.langchain.com).
- **A LangSmith API key**: Follow the [Create an API key](/langsmith/create-account-api-key#create-an-api-key) guide.
- **A LangSmith API key**: Create an API key [here](https://smith.langchain.com/settings/apikeys).
Copy link
Contributor

Choose a reason for hiding this comment

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

OK, we don't make this change? It is a better docs practice to spell out the link that a user is going to. We try to avoid "here" where possible for links.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I added manual guidance along with the direct link. Want to make it as easy as possible for people to create an api key

@tanushree-sharma tanushree-sharma changed the title Document messages format in more places Document messages format Jan 20, 2026
@github-actions
Copy link
Contributor

Mintlify preview ID generated: preview-messag-1768940705-dd721f5

@github-actions
Copy link
Contributor

Mintlify preview ID generated: preview-messag-1768942621-8d4fe46


**1. Rich debugging experience**: LangSmith provides structured rendering of message lists, making it easier to visualize and understand the conversation history.

**2. LangSmith features**: Features like [Polly](/langsmith/polly), [LangSmith Fetch](https://github.com/langchain-ai/langsmith-fetch) and [multi-turn evals](/langsmith/online-evaluations#configure-multi-turn-online-evaluators) require properly structured traces to work correctly.
Copy link
Contributor

Choose a reason for hiding this comment

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

are you open to calling multi-turn evals "thread evals"? it feels like the more marketable name

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I actually think the opposite - "multi-turn" is used by those building agents, while "threads" is an implementation detail


#### Threads

A [_**Thread**_](/langsmith/threads) groups multiple interactions together so you can see the conversation history over time. In the LangSmith UI, threads can be viewed in the "Threads" tab within a Tracing Project.
Copy link
Contributor

Choose a reason for hiding this comment

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

I wonder if we need to go more broad with this definition i.e. what is a thread in the context of a non-conversational agent

Copy link
Contributor

Choose a reason for hiding this comment

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

but if we give such a definition, the next sentence could still be using "conversation" as an example of a type of thread

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Agree, will generalize to just "history" over time

@github-actions
Copy link
Contributor

Mintlify preview ID generated: preview-messag-1768947382-18caaf8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal langsmith For docs changes to LangSmith

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants