Skip to main content
An environment records where an agent was running when it produced a trace. Every trace an agent records lands in exactly one of its environments, which are drawn from a fixed set of four. Because the environment travels with the trace, where the agent was running is a property of the trace itself.
Beta. Agent-based workspaces are in beta. LangChain enables agent-based workspaces for an organization, and the change applies to workspaces created after that. An existing project-based workspace does not convert automatically, but LangChain can convert it. To ask about access, contact our sales team.

Environment names

The four environments are fixed, and custom names are not supported. The environment switcher lists them most production-like first:
  • Production
  • Staging
  • Development
  • Local
How many of the four an agent has depends on how it was created. An agent created in the UI, through Build, starts with Production alone, and each of the others appears the first time a trace is addressed to it. An agent created any other way starts with all four. LangSmith attaches no behavior to the choice beyond keeping each environment’s traces apart. An environment does not change how an agent is instrumented, and the same build can report into a different environment by changing its agent addressing.

Select an environment

Wherever LangSmith needs one environment instead of all of them, it uses the same control: a button showing the current environment, which opens the list. It lists the agent’s environments in the order above. The environment selected when you arrive depends on the section:
  • Studio and alerts: Production.
  • Monitoring and Deployments: The environment you last used for the agent, or Production when there is none.
  • Tracing: The environment you last used for the agent, then Local, then the first environment the agent has.
On Deployments, Local does not display, and the list adds a Preview entry when preview builds are turned on and the agent has previews. The list holds only the environments that exist for the agent. This control drives environment selection on Tracing, Monitoring, alerts, Engine, Studio, and Deployments. Evaluators and Insights also scope to a single environment, but they do it without this dropdown.

See also