Skip to content
← Tags
langchain-ai/deepagentsMIT

Deep Agents: an off-the-shelf agent harness reverse-engineered from Claude Code

The README opens by calling itself an off-the-shelf agent harness: MIT licensed, Python (plus deepagents.js), built on LangGraph, so streaming, durability and checkpoints are inherited rather than rewritten. The key to reading it is the acknowledgement - inspired by Claude Code, trying to figure out what makes it general and pushing that further - which makes this a reverse-engineering exercise: take a closed coding agent that is known to work well, open it up, and ask what actually lets it handle long tasks. Its answer is four bundled things: a pluggable-backend file system (the artefacts of long tasks are files, not messages, so context keeps only pointers), sub-agents each with their own window (context isolation and compression, not extra helpers), long-thread summarisation with tool output offloaded to disk, and on-demand Skills. Also sandboxed shell execution, cross-session persistent memory, human-in-the-loop approval/edit/reject before a tool call runs, and any MCP server as a tool. Model agnostic: frontier APIs, open weights hosted on Baseten or Fireworks, and self-hosted Ollama/vLLM/llama.cpp all work, with three lines of create_deep_agent giving you a planning, file-reading-and-writing agent. The security section is unusually blunt - it follows a trust-the-LLM model, boundaries must be enforced at the tool and sandbox layer, and you should not expect the model to restrain itself. 29.7k stars. Not run yet; sub-agent isolation quality and summarisation information loss are unverified, so this is graded as pending reproduction.

Agent HarnessCoding AgentSub-Agents
Python30k4.2k139
ahujasid/mcp-for-blenderMIT

MCP for Blender: 32 tools that make Blender a 3D workspace an LLM can drive

Formerly blender-mcp, a third-party community plugin (the README states on its first screen that it is not made by Blender), MIT licensed, Python, and the highest-starred entry among 3D MCP servers. The PyPI package is now mcp-for-blender, yet uvx blender-mcp still runs and existing configs need no change. Two components only: an addon inside the Blender process runs a socket server that actually executes commands (the only place with bpy, the current scene and the UI thread), while a separate MCP server process translates protocol, joined by JSON over TCP on localhost:9876 by default. The source defines 32 @mcp.tool() decorators across four layers - perception (get_scene_info, get_object_info, get_viewport_screenshot returning an MCP Image, closing an act-then-look loop), reference lookup (bpy_api_lookup and describe_node_type so the model queries instead of guessing socket order and enum names), execution (execute_blender_code as the escape hatch, set_texture, export_scene to GLB/FBX), and asset retrieval and generation (Poly Haven with semantic search, importing the .blend source and writing attribution properties; Poly Pizza with about 10,600 low-poly models, size normalisation and automatic CC-BY credit; Sketchfab; Hyper3D Rodin text-to-3D and image-to-3D; Tencent Hunyuan3D distinguishing the mainland ai3d endpoint from the international hunyuan one). On security, arbitrary code execution is the design rather than a bug: an optional safe mode (BLENDER_MCP_SAFE_MODE=1) statically validates scripts before running, blocking file access, subprocesses, network and persistent code while modelling, rendering, saving, import and export pass normally, and blocked scripts return to the model with the reason so it can retry. Content telemetry is off by default, and a dedicated disable_telemetry tool can only turn collection off. 29.2k stars. Not run with Blender locally yet, so this is graded as pending reproduction.

MCPBlender3D Generation
Python29k2.7k202

As an Amazon Associate, we earn from qualifying purchases.