deepagents-code 0.1.67 stops leaking secrets across projects

LangChain's deepagents-code CLI released version 0.1.67, and most of the changelog is workspace isolation work. Project policy now resolves per workspace, a project's .env file stays scoped to that workspace, and LangSmith auth and tracing no longer cross between workspaces, per the release notes on GitHub.

That closes a real gap for anyone running the CLI across more than one project directory. Before 0.1.67, policy settings and secrets from one workspace could carry into another just by switching directories and running the tool again.

The same applied to LangSmith. Tracing and auth weren't scoped to a workspace. A trace or a credential set in one project's context could show up attached to a run in a different project.

The release notes don't say how long the isolation gap existed, whether it gets a formal security advisory, or what a user would have actually seen if it hit them. They also don't say if the fix needs any config changes on the user's end. Anyone running this CLI against multiple client or personal projects from one machine should pull 0.1.67.