Stripe built Minions. Ramp built Inspect. Coinbase built Cloudbot. Three engineering organizations, working independently, arrived at similar architectural decisions for their internal AI coding agents. LangChain noticed the convergence and open-sourced the pattern.
Open SWE, released March 17, is an open-source framework built on LangChain’s Deep Agents and LangGraph that provides the core architectural components for internal coding agents. The MIT-licensed project isn’t trying to be another AI coding assistant. It’s a customizable foundation for organizations that want to build their own — the way Stripe, Ramp and Coinbase already have.
The Convergence
What caught LangChain’s attention was that these independently developed systems share the same architectural decisions. Isolated cloud sandboxes where tasks run with full permissions inside strict boundaries. Curated toolsets — Stripe reportedly maintains around 500 carefully selected tools. Subagent orchestration where complex tasks get decomposed and delegated to specialized child agents. And integration with existing developer workflows through Slack, Linear, and GitHub rather than requiring engineers to adopt new interfaces.
The convergence suggests that production engineering environments have common requirements for AI coding agents. Open SWE codifies those requirements into a framework that other organizations can start from rather than rebuilding from scratch.
How it Works
Open SWE composes on the Deep Agents framework rather than forking an existing agent — similar to how Ramp built Inspect on top of OpenCode. This gives organizations an upgrade path: When Deep Agents improve context management or token efficiency, those improvements flow through without requiring customizations to be rebuilt.
Each task runs in its own isolated cloud sandbox — a remote Linux environment with full shell access. The repository is cloned in, the agent is granted full permissions within that boundary, and errors are contained. Multiple tasks run in parallel, each in a separate sandbox. The framework supports pluggable providers, including Modal, Daytona, Runloop and LangSmith.
The toolset is deliberately small — roughly 15 curated tools covering shell execution, web fetching, API calls, Git operations, and integrations with Linear and Slack, plus Deep Agents’ built-in tools for file operations, search, planning, and subagent spawning. Stripe’s insight was that tool curation matters more than quantity. Open SWE follows that principle and allows organizations to add tools for internal APIs or testing frameworks as needed.
Context engineering happens through two channels. An AGENTS.md file at the repository root gets injected into the system prompt — the equivalent of Stripe’s rule files, encoding conventions, testing requirements, and architectural decisions. The full Linear issue or Slack thread history is assembled and passed to the agent, so it starts with rich context rather than having to discover everything through tool calls.
Workflow Integration
Open SWE integrates through the surfaces where developers already work. Mention the bot in a Slack thread, and it replies with status updates and PR links. Comment @openswe on a Linear issue, and the agent reads the full context, acknowledges with a reaction, and posts results as comments. Tag @openswe in PR comments on agent-created pull requests, and it addresses review feedback and pushes fixes to the same branch.
Each invocation creates a deterministic thread ID, so follow-up messages route to the same running agent. You can send messages mid-task — change the spec, add a requirement, redirect the approach — and the agent integrates your feedback into its active session without restarting.
When the work completes, the middleware automatically opens a PR if the agent hasn’t already. The agent runs linters, formatters, and tests before committing. Organizations can extend this with deterministic CI checks, visual verification, or review gates as additional middleware.
“When Stripe, Ramp, and Coinbase independently arrive at the same architecture for internal AI coding agents, you take notice. Open SWE brings together the important elements of isolated sandboxes, curated toolsets, subagent orchestration, and workflow integration through surfaces developers already use,” according to Mitch Ashley, VP and practice lead for software lifecycle engineering at The Futurum Group.
“For teams evaluating whether to build their own, the rebuild calculus has changed. These are production-validated patterns, and organizations that reconstruct them from scratch are absorbing delay and risk the market has already worked through.
Why This Matters for DevOps
Open SWE represents a different trajectory than the AI coding tools we’ve covered in this series. Claude Code, GitHub Copilot, Gemini Code Assist and Cursor are products you adopt. Open SWE is a customizable framework. The distinction matters for organizations that need control over how agents interact with their codebase, internal tools, and workflows.
The sandbox isolation model addresses security concerns we’ve seen across the agent landscape—full permissions inside strict boundaries. Blast radius contained. The same pattern is formalized in IronCurtain’s architecture and VS Code’s agent hooks, now implemented as a deployment model.
The middleware architecture is the extensibility story. Deterministic hooks for CI gates, security scans, approval workflows — without modifying core agent logic. Configuration-level customization rather than fork-level modification.
The framework defaults to Claude Opus 4.6 but supports any LLM provider. Organizations can configure different models for different subtasks — the same strategy-vs-tactics separation we’ve seen in Gemini CLI’s model routing and Random Labs’ Slate architecture.
Open SWE is available now at github.com/langchain-ai/open-swe. A hosted version is available at swe.langchain.com and requires an Anthropic API key.