Feature request
Currently, a static LangSmith project can only be configured through LANGSMITH_PROJECT, which identifies the project by name (docs: https://docs.langchain.com/langsmith/log-traces-to-project#set-the-destination-project-statically)
I propose supporting LANGSMITH_PROJECT_ID as an alternative, allowing applications to identify their project by its stable ID.
Motivation
LangSmith projects can be renamed due to typos, naming convention changes, or other organizational needs.
The web-UI gives a capability to rename the project. It however warns that Before saving, ensure your application code is updated to use the new project name. New traces sent to the old project name will go to a separate project..
Since it's practically impossible to sync a deployment rollout with project rename, it's guaranteed that some traces are going to be sent to the old project (and auto-create it as well).
Feature request
Currently, a static LangSmith project can only be configured through LANGSMITH_PROJECT, which identifies the project by name (docs: https://docs.langchain.com/langsmith/log-traces-to-project#set-the-destination-project-statically)
I propose supporting LANGSMITH_PROJECT_ID as an alternative, allowing applications to identify their project by its stable ID.
Motivation
LangSmith projects can be renamed due to typos, naming convention changes, or other organizational needs.
The web-UI gives a capability to rename the project. It however warns that
Before saving, ensure your application code is updated to use the new project name. New traces sent to the old project name will go to a separate project..Since it's practically impossible to sync a deployment rollout with project rename, it's guaranteed that some traces are going to be sent to the old project (and auto-create it as well).