Skip to content
← Tags

#Open Source (148)

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
GLips/Figma-Context-MCPMIT

Framelink MCP for Figma: design files compressed into usable context, not screenshots

Also known as Figma-Context-MCP, npm package figma-developer-mcp, TypeScript, MIT, and a third-party implementation rather than the Dev Mode MCP server Figma ships itself. It exposes only two tools: get_figma_data (read-only) and download_figma_images (removable with –skip-image-downloads, and confined to writing inside –image-dir). The narrow surface is deliberate; the engineering sits in the fetch → simplify → serialize pipeline behind it. Simplify uses composable extractors (layout, text, visuals, component, plus the allExtractors, layoutAndText, contentOnly, visualsOnly and layoutOnly bundles) to compress the raw Figma response into semantic layout and styling in a single tree walk, with maxDepth and nodeFilter, and outputs tree (default, cheapest in tokens), yaml or json. The part worth copying is that compression effectiveness is a metric computed on every call: rawSizeKb against simplifiedSizeKb, rawNodeCount against simplifiedNodeCount, component/instance/text/image node counts, namedStyleCount (the source comment states a high count is a design-system maturity signal), hasVariables (whether Figma Variables are used at all), and separate fetch/simplify/serialize timings; the same hooks drive MCP progress notifications and heartbeats so a large file taking tens of seconds does not look hung. Judgement shows in the details: node IDs accept both the plain and the deeply nested instance shape, the depth parameter description says do not use it unless the user explicitly asks, the proxy default deliberately avoids installing EnvHttpProxyAgent when no proxy variables exist so a stale variable cannot route traffic through an intermediary returning 403, and stdio mode warns at startup when –image-dir is unset. Credentials come from FIGMA_API_KEY or FIGMA_OAUTH_TOKEN; telemetry can be disabled with –no-telemetry or DO_NOT_TRACK=1 and secrets are redacted from reports. 15.9k stars. It generates no frontend code - the output is design facts, and translating them into React, Vue or SwiftUI is your coding agent job. Not yet run against a Figma file of our own, and no screenshot-versus-structured-data accuracy comparison, so this is graded as pending reproduction.

MCPFigmaDesign-to-Code
TypeScript16k1.3k65
XiaomiMiMo/MiMo-CodeMIT

MiMo Code: Xiaomi terminal coding agent betting on memory and self-evolution

Xiaomi open-sourced terminal-native AI coding assistant, TypeScript built with bun. The source is MIT but usage is additionally bound by USE_RESTRICTIONS.md, the MiMo terms of service and the trademark policy - read those before treating it as plain MIT. The README states it is a fork of OpenCode: it keeps the multi-provider, TUI, LSP, MCP and plugin core and adds persistent memory (SQLite FTS5 full-text search across four kinds - project MEMORY.md, session checkpoints, scratch notes and task progress - injected automatically on session resume), intelligent context management (near the limit it rebuilds from the latest checkpoint plus project memory plus task progress plus retained recent messages, ranked by importance against a token budget), goals and stop conditions (/goal sets the condition, and when the agent wants to stop a separate judge model assesses whether it was truly met, which targets optimistic early quitting), and deterministic JS workflows in a sandbox (compose splits independent tasks into isolated git worktrees with per-task TDD; also deep-research, fact-check with three-reviewer adversarial voting, and research-experiment with an anti-metric-gaming audit). Twenty built-in skills (arxiv, claude-code, codex, docx, pdf, pptx, xlsx, html-to-video, product-design and more), compatible with four skill roots - .agents/skills, .claude/skills, .codex/skills, .opencode/skills - where a user skill of the same name overrides the built-in. /dream and /distill are its signature: the first distils recent session trajectories into project memory and prunes stale entries, the second finds your repeated manual routines and packages high-confidence candidates into reusable skills. Model agnostic - the Xiaomi platform, Codex/ChatGPT OAuth, or any OpenAI-compatible endpoint. 13.4k stars. Not installed or run yet; memory-restore accuracy, judge-model effectiveness and the vendor-stated cache hit rates are unverified, so this is graded as pending reproduction.

Coding AgentAgent HarnessPersistent Memory
TypeScript13k1.4k76
AI CodingDevelopmentTopC

Trae: ByteDance two-form-factor coding line - TraeCode (IDE + SOLO) and TraeWork, plus a stalled MIT-open shell

Trae is the AI coding line from ByteDance, and the official docs split it into two clearly different things. TraeCode is a development tool with AI deeply integrated, in two modes: IDE mode keeps the editor, terminal, debugger, extensions and source control for scenarios that need fine-grained control over code changes and execution, while SOLO mode hands the lead to AI - describe the requirement in natural language, by voice or by uploading local files, and it decomposes the task itself and runs code generation, testing, preview, change summary and deployment, with a task panel, an AI conversation panel and a tool panel (built-in editor, doc viewer, browser) from left to right. TraeWork is the AI-native workspace grown out of the SOLO mode of TraeCode, on web, desktop and mobile, in Work / Code / Design modes, aimed at product managers, data analysts, operations and designers rather than developers only. The long-task ceilings are stated concretely: Max mode extends the context window to 1M, allows up to 200 tool-call rounds per task and reads up to 750 lines per file read to cut down on chunking. bytedance/trae-agent is MIT-licensed but has not been updated for about eight months and cannot stand for the current engineering of Trae. Boundaries: no third-party benchmark readings are published (no SWE-bench or Terminal-Bench self-evidence), so every capability claim comes from feature docs and vendor descriptions; clients are closed source; 1M / 200 rounds / 750 lines are ceilings rather than typical experience and the vendor itself says they raise cost substantially; model availability is doubly limited by region (Seed, MiniMax and GLM unavailable to US users) and by plan tier, so teams across regions do not share one model set; concurrent cloud tasks are a hard tier difference and Free excludes SOLO, so evaluation cannot look at monthly price alone. Confidence C (vendor-claim).

1M · 200 roundsMax mode limits (context / tool rounds per task)Vendor Claim · 2026-09
ProductByteDanceSiteRepo
Trae: ByteDance two-form-factor coding line - TraeCode (IDE + SOLO) and TraeWork, plus a stalled MIT-open shell

As an Amazon Associate, we earn from qualifying purchases.