How agent-based workspaces differ

LangSmith organizes a workspace in one of two ways. A project-based workspace groups traces by tracing project. An agent-based workspace groups them by agent, and divides each agent’s traces across environments drawn from a fixed set of four. Agent-based organization is in beta. This page covers what is different in an agent-based workspace, and what changes if yours becomes one.

​

Check which one you have

The control at the top left tells you. In an agent-based workspace it names your workspace and opens a list of the workspaces in your organization. In a project-based workspace it shows the LangSmith logo, and the sidebar has an Application section with an application picker.

​

What changes

The organizing container changes, and everything scoped to it follows:

• Traces group under an agent and one of its environments instead of under a tracing project you named. Nothing is re-ingested or moved. When an existing workspace converts, each tracing project becomes an agent with a production environment, and that environment keeps the project’s ID and name. A tracing project for a new environment takes the agent identifier, a hyphen, and the environment as its name: an agent whose identifier is checkout has its staging traces in checkout-staging.
• Prebuilt dashboards cover an environment rather than a named project. See Monitor projects with dashboards.
• Alerts are scoped to an environment of an agent. See Alerts.
• Evaluators attach to an environment. See Manage evaluators.
• Datasets attach to one or more agents rather than to a project, and to no environment, so one dataset can serve several agents. See Create and manage datasets in the UI.
• Navigation gains an agent picker in the top bar, which moves between the agent list and a single agent’s Overview. See Navigate agents.
• The top-left control becomes a workspace switcher. In a project-based workspace it shows the LangSmith logo. Where Fleet is enabled, the logo opens a menu for moving between LangSmith and Fleet. Otherwise, it links to the LangSmith home page. In an agent-based workspace the control names your workspace and lists the other workspaces in your organization. Where Fleet is enabled, the menu ends with a link to Fleet.

What does not change: your traces, datasets, prompts, and experiments are the same records, and existing tracing configuration keeps working. See Log traces to a specific project.

​

What the change is worth

Agents and environments record what a tracing project cannot: which application produced a trace, and which deployment of it. LangSmith can then act on that context rather than asking you to filter for it, so an alert can watch production and stay quiet about local runs, and a prebuilt dashboard covers each environment without you naming a project for it.

​

How a workspace moves

During the beta, LangChain enables agent-based organization for an organization, and the change applies to workspaces created in that organization after that. No action is required from you. An existing project-based workspace does not convert automatically. LangChain can convert it, and the conversion keeps your existing tracing projects as described in What changes. After a workspace converts, a workspace admin can switch it between the new experience and the classic, project-based experience. Go to Settings > Workspace > Configuration > Workspace. The switch applies to everyone in the workspace, and appears only in workspaces that LangChain has converted.

​

See also

• Agents
• Agent environments
• Workload isolation
• Administration overview

---