open-swe

open-swe is a plugin for Claude Code from langchain-ai/open-swe. Its manifest loads nothing; the 2 skills, 1 MCP server it bundles cost 47 tokens per session together, scanned A, original, MIT.

A Claude Code plugin that mirrors coding sessions into private Open SWE threads and provides access to Open SWE tools. Open SWE is a service for viewing and working with those session threads.

In plain words
What is it for?
Use it to connect Claude Code to an Open SWE deployment, mirror sessions, and find their threads.
Why use it?
It keeps session mirroring and the related tool connection together instead of configuring them separately.

Plugin for Claude Code ✓ vendor

Written for Claude Code: a Claude Code plugin manifest. Also seen: mentions Claude Code.

▶ Introducing Open SWE: An Open-Source Asynchronous Coding Agent LangChain · about open-swe · on YouTube →

Good fit Use it to connect Claude Code to an Open SWE deployment, mirror sessions, and find their threads.

Compare 6 plugins from other repositories ↓
Install in Claude Code
/plugin marketplace add langchain-ai/open-swe
/plugin install open-swe
About the project

Open SWE is an open-source software factory that gives coding tasks to an asynchronous agent, which investigates repositories, changes code, validates the results, and delivers pull requests. Engineering teams use it to automate code changes, reviews, CI follow-up, and related repository work from dashboards and connected tools.

langchain-ai/open-swe · 11,163 stars · on GitHub · langchain.com

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/langchain-ai/open-swe

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for open-swe

README.md
[![agentmods](https://agentmods.dev/badge/plugins/langchain-ai/open-swe/claude-code-plugin/github.svg)](https://agentmods.dev/plugins/langchain-ai/open-swe/claude-code-plugin)
Your own site
<a href="https://agentmods.dev/plugins/langchain-ai/open-swe/claude-code-plugin"><img src="https://agentmods.dev/badge/plugins/langchain-ai/open-swe/claude-code-plugin/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for open-swe

Your own site · 80×15
<a href="https://agentmods.dev/plugins/langchain-ai/open-swe/claude-code-plugin"><img src="https://agentmods.dev/badge/plugins/langchain-ai/open-swe/claude-code-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured The manifest loads nothing itself; its 2 skills, 1 MCP server cost 47 tokens a session between them.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

open-swe scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

claude-code-plugin/.claude-plugin/plugin.json · 20 lines

What it actually says

{
  "name": "open-swe",
  "displayName": "Open SWE",
  "version": "0.1.0",
  "description": "Mirror Claude Code sessions into Open SWE threads, use Open SWE's MCP tools, and find a session's thread",
  "author": {
    "name": "LangChain"
  },
  "repository": "https://github.com/langchain-ai/open-swe",
  "license": "MIT",
  "userConfig": {
    "server_url": {
      "type": "string",
      "title": "Open SWE URL",
      "description": "Origin of your Open SWE deployment",
      "default": "https://openswe.langchain.dev"
    }
  }
}
Contents

What it installs

The manifest is a name and a version. 2 skills, 1 MCP server travel with it, and installing the plugin installs all of them — 47 tokens a session between them. Each is measured on its own page, and each can be installed alone.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 20 lines scan A 46224de199af

Subscribe to this mod's changes

open-swe is a plugin published in the GitHub repository langchain-ai/open-swe (11,163 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-02.