Nov 6, 2026
Branch updates can be lockfile-only.
Nov 6, 2026
Remote Control keeps work on an awake host.
Nov 6, 2026
Existing scans and secret inventories need different interpretations.
Inspect secrets and model choices before cutover.
The November 3 expansion
LangChain’s November 3 announcement expands LangSmith BYOC to Azure and Google Cloud in beta; AWS remains generally available. LangChain operates the control plane and manages the data plane in the customer’s cloud. Sales provisions access.
The launch separately limits trace migration to AWS. A copied workspace is not proof its history is present.
Check the copied agent
Imagine an imported Fleet agent appears in the destination workspace. Before directing work there, separate two checks: restore required secret values and confirm its selected model. The migration guide says secrets become empty placeholders and unavailable source models can be substituted, with substitutions logged.
A successful object copy therefore cannot establish working credentials or unchanged model identity. If answers differ after cutover, verify the model choice before attributing the difference to the move. Each user must also reconnect OAuth. This is a documented acceptance scenario, not a migration or output comparison we ran.
Conceptual diagram: OpenTools Team; selected checks from LangChain’s migration guide, not a performed migration.
Name the acceptance owners
The responsibility model leaves application validation with the customer while LangChain operates BYOC‑managed services. Give the credential/reconnection owner and application owner separate sign‑offs: one restores access, the other confirms the intended model and application behavior. The undated guides describe current requirements; their individual details are not all newly launched on November 3.