deep-agents
Skill445 starsChanged 10 days agoMITView on GitHub
Build batteries-included agents with planning, context management, subagent delegation, and sandboxed execution. Use for complex, multi-step tasks that need built-in capabilities.
- Installs packages
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/docs-style.mdcCursor rule
- add-docs-pageSkill
- docs-code-samplesSkill
- docs-editSkill
- docs-restructureSkill
- docs-reviewSkill
- docs-team-voiceSkill
- docs-tooling-notionSkill
- submit-integrationSkill
- update-integrations-prsSkill
- verify-against-sourceSkill
- deepagents-codeSkill
- deepagentsjsSkill
- deepagentsSkill
- openwikiSkill
- release-researchSkill
- ship-docs-updateSkill
- langgraph-docsSkill
- write-timestampSkill
- pandas-patternsSkill
- langchainSkill
- langgraphSkill
- langsmithSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Use Deep Agents when you need to:
- Distinctive: line 26
Default to Managed Deep Agents for new agents.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deep Agents
Deep Agents is the agent harness for complex, multi-step work: planning, a virtual filesystem for context, subagent delegation, and long-term memory. It is built on LangChain and the LangGraph runtime.
Start with Managed Deep Agents: a managed open-source harness for agents that plan, use tools, delegate to subagents, and work over long horizons. Alternatively, for maximum flexibility while using the same Deep Agents harness, use the Deep Agents SDK and host agents yourself, or run a custom LangSmith Deployment.
When to use
Use Deep Agents when you need to:
- Handle complex, multi-step tasks that benefit from automatic planning
- Manage context with a built-in virtual filesystem for large inputs
- Delegate subtasks to specialized subagents
- Run code safely in sandboxed execution environments
- Use a terminal agent via Deep Agents Code
Default to Managed Deep Agents for new agents. Use the self-hosted SDK when the user needs to own the backend, store, checkpointer, or Agent Server.
When NOT to use
- For simple tool-calling agents without planning or subagents, use LangChain agents instead—lighter weight
- For custom graph-based orchestration with explicit control flow, use LangGraph directly
- Deep Agents is the highest-level abstraction—it trades flexibility for convenience
Install
# Python
pip install deepagents
# JavaScript/TypeScript
npm install deepagents langchain @langchain/coreQuick reference
Create a deep agent
# pip install deepagents langchain-anthropic
from deepagents import create_deep_agent
def get_weather(city: str) -> str:
"""Get weather for a given city."""
return f"It's always sunny in {city}!"
agent = create_deep_agent(
model="anthropic:claude-sonnet-4-6",
tools=[get_weather],
system_prompt="You are a helpful assistant",
)
result = agent.invoke(
{"messages": [{"role": "user", "content": "What is the weather in SF?"}]}
)Use Deep Agents Code
# Install Deep Agents Code
pip install deepagents-code
# Run an interactive terminal agent
deepagentsBuilt-in capabilities
| Capability | Description |
| Planning | Automatic task decomposition for complex requests |
| File system | Virtual filesystem for reading, writing, and managing context |
| Subagents | Spawn child agents for parallel subtask execution |
| Context management | Automatic context compression for long conversations |
| Sandboxed execution | Run code in isolated environments (Modal, Runloop, Daytona) |
| Protocols | ACP, MCP, and A2A support for interoperability |
Key documentation
- Managed Deep Agents—Build deep agents with managed deployment infrastructure
- Overview—Harness overview and Managed vs self-host decision
- SDK quickstart—The same deep agents harness, self-hosted
- Customization—Configure models, tools, and behavior
- Context engineering—Manage context for complex tasks
- Subagents—Delegate work to child agents
- Sandboxes—Run code in isolated environments
- Code—Deep Agents Code, the terminal agent interface
API reference
For SDK class and method details, use the LangChain API Reference site:
- MCP server:
https://reference.langchain.com/mcp
Related skills
- langchain—Core building blocks that Deep Agents is built on
- langgraph—Runtime that powers Deep Agents' durable execution
- langsmith—Trace, evaluate, and deploy your deep agents
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

