> [!CAUTION] > Merging this PR will automatically publish to **PyPI** and create a **GitHub release**. For the full release process, see [`.github/RELEASING.md`](https://github.com/langchain-ai/deepagents/blob/main/.github/RELEASING.md). --- _Release notes preview: keep this section in sync with the package `CHANGELOG.md`. The published GitHub release body is extracted from the merged `CHANGELOG.md` by `release.yml`, not from this PR description._ --- ## [0.1.42](https://github.com/langchain-ai/deepagents/compare/deepagents-code==0.1.41...deepagents-code==0.1.42) (2026-07-17) ### Features - Plugins are now generally available. ([#4797](https://github.com/langchain-ai/deepagents/issues/4797)) - Added search to the plugin list and now summarize plugin changes after reloads. ([#4765](https://github.com/langchain-ai/deepagents/issues/4765), [#4767](https://github.com/langchain-ai/deepagents/issues/4767)) - Added Kimi K3 to the OpenRouter model selector. ([#4803](https://github.com/langchain-ai/deepagents/issues/4803)) - Added hidden `connect` and `reconnect` keywords for `/restart`. ([#4807](https://github.com/langchain-ai/deepagents/issues/4807)) - Debug Console thread IDs can now be clicked to copy, with an added LangSmith link. ([#4760](https://github.com/langchain-ai/deepagents/issues/4760)) - Added auto-approve (YOLO) mode to trace metadata. ([#4764](https://github.com/langchain-ai/deepagents/issues/4764)) ### Bug Fixes - Improved plugin marketplace loading and onboarding, including asynchronous marketplace additions and polish for empty marketplace states. ([#4766](https://github.com/langchain-ai/deepagents/issues/4766), [#4759](https://github.com/langchain-ai/deepagents/issues/4759)) - Clarified plugin component discovery and reload status. ([#4774](https://github.com/langchain-ai/deepagents/issues/4774)) - Avoided blocking MCP OAuth token refresh. ([#4770](https://github.com/langchain-ai/deepagents/issues/4770)) - Restored keyboard focus for marketplace details. ([#4763](https://github.com/langchain-ai/deepagents/issues/4763)) - Dismissed the startup tip when submitting an initial prompt with `-m`. ([#4779](https://github.com/langchain-ai/deepagents/issues/4779)) _End release notes preview._ --- > [!NOTE] > A **New Contributors** section is appended to the GitHub release notes automatically at publish time (see [Release Pipeline](https://github.com/langchain-ai/deepagents/blob/main/.github/RELEASING.md#release-pipeline), step 2). --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: langchain-oss-automated-triage[bot] <248757908+langchain-oss-automated-triage[bot]@users.noreply.github.com>
Deep Agents CLI — Deployment Tooling
Important
The interactive coding agent moved. As of
deepagents-cli==0.1.0, this package contains only the deployment subcommands (init,dev,deploy). The interactive REPL — previously launched viadeepagents— now ships asdeepagents-code(dcode).curl -LsSf https://langch.in/dcode | bash dcode
Install
uv tool install deepagents-cli
You'll need a LangSmith API key with access to the Managed Deep Agents private
preview (waitlist).
Export it before running any command, or put it in a repo .env or
~/.deepagents/.env:
export LANGSMITH_API_KEY="..."
Usage
# Scaffold a new project folder
deepagents init my-agent
# Register any MCP servers you intend to use (one-time, per workspace)
deepagents mcp-servers add --url https://tools.langchain.com \
--header X-Api-Key=$LANGSMITH_API_KEY \
--name Fleet
# init scaffolds an empty tools.json. Add tools that reference a registered
# MCP server's URL (otherwise the agent has no tools), e.g. the Fleet server
# registered above:
# { "name": "read_url_content", "mcp_server_url": "https://tools.langchain.com",
# "mcp_server_name": "Fleet", "display_name": "read_url_content" }
# Upsert the project as a managed agent on /v1/deepagents/*
cd my-agent && deepagents deploy
deepagents init scaffolds an empty tools.json, an example skill under
skills/, and an example subagent under subagents/; edit or remove them to
suit your agent. tools.json starts empty because every tool must reference an
MCP server that is already registered in the workspace
(deepagents mcp-servers add) — so a freshly scaffolded project deploys
without first registering a server.
New agents default to the state backend. To opt into a managed sandbox, set
agent.json's backend.type to sandbox and configure
backend.sandbox_config.scope as thread or agent; sandbox_config can also
include sandbox policy IDs and TTL fields. The CLI does not create or run
sandboxes locally; sandbox lifecycle is handled by the Managed Deep Agents
platform.
{
"backend": {
"type": "sandbox",
"sandbox_config": {
"scope": "thread",
"policy_ids": ["policy-id"]
}
}
}
Project layout
my-agent/
agent.json # name, description, backend, runtime.model, permissions
AGENTS.md # system prompt
tools.json # tools the agent can call (optional)
skills/<name>/SKILL.md # frontmatter-tagged skills (optional)
subagents/<name>/ # delegated subagent definitions (optional)
Other commands
deepagents agents list # list workspace agents
deepagents agents get <agent_id> # show one agent
deepagents agents delete <agent_id> # delete an agent
deepagents mcp-servers list # list workspace MCP servers
deepagents mcp-servers add --url URL # register a server
deepagents mcp-servers get <id|name|url> # show one server
deepagents mcp-servers tools <id|name|url> # list a server's tools
deepagents mcp-servers update <id|name|url> # update server URL or headers
deepagents mcp-servers delete <id|name|url> # remove a server
deepagents mcp-servers connect <id|name|url> # start OAuth for a server
get, update, delete, and connect accept an MCP server's id, exact name,
or URL — a non-id value is resolved against mcp-servers list (URLs are matched
ignoring case and trailing slash).
📖 Resources
- CLI Documentation
- Changelog
- Source code
- Deep Agents SDK — underlying agent harness
- Deep Agents Code — coding agent
- LangChain Academy — Comprehensive, free courses on LangChain libraries and products, made by the LangChain team.
- Code of Conduct — community guidelines and standards
📕 Releases & Versioning
See our Releases and Versioning policies.
💁 Contributing
As an open-source project in a rapidly developing field, we are extremely open to contributions, whether it be in the form of a new feature, improved infrastructure, or better documentation.
For detailed information on how to contribute, see the Contributing Guide.