--- title: "open-swe vs CodeMachine-CLI" type: "comparison" canonical_url: "https://www.graphcanon.com/compare/langchain-ai-open-swe-vs-moazbuilds-codemachine-cli" tools: ["langchain-ai-open-swe", "moazbuilds-codemachine-cli"] --- # open-swe vs CodeMachine-CLI *GraphCanon updated Jul 15, 2026* ## Verdict Pick open-swe if open-swe is an open-source asynchronous coding agent that allows customization of components like models, sandboxes, tools, triggers, prompts, and middleware; pick CodeMachine-CLI if codeMachine-CLI is an open-source TypeScript tool that enables developers to create repeatable workflows using AI coding agents. [open-swe](https://www.langchain.com/blog/open-swe-an-open-source-framework-for-internal-coding-agents) reports 10k GitHub stars, 1.2k forks, and 18 open issues, last pushed Jul 10, 2026. [CodeMachine-CLI](https://codemachine.co/) has 2.5k stars, 242 forks, and 9 open issues, last pushed Feb 25, 2026. Figures are from public GitHub metadata via [open-swe's repository](https://github.com/langchain-ai/open-swe) and [CodeMachine-CLI's repository](https://github.com/moazbuilds/CodeMachine-CLI). | | [open-swe](/tools/langchain-ai-open-swe.md) | [CodeMachine-CLI](/tools/moazbuilds-codemachine-cli.md) | | --- | --- | --- | | Tagline | An Open-Source Asynchronous Coding Agent | Orchestrates AI coding agents into repeatable workflows | | Stars | 10,235 | 2,509 | | Forks | 1,167 | 242 | | Open issues | 18 | 9 | | Language | Python | TypeScript | | Adopt for | open-swe is an open-source asynchronous coding agent that allows customization of components like models, sandboxes, tools, triggers, prompts, and middleware. | CodeMachine-CLI is an open-source TypeScript tool that enables developers to create repeatable workflows using AI coding agents. | | Persona | - | - | | Runtime | - | - | | License | MIT | Apache-2.0 | | Categories | AI Agents, Evaluation & Observability | AI Agents, Developer Tools | ## Trust and health _Sourced signals - not a safety guarantee. No winner column._ | | [open-swe](/tools/langchain-ai-open-swe.md) | [CodeMachine-CLI](/tools/moazbuilds-codemachine-cli.md) | | --- | --- | --- | | Maintenance | Very active (96%) | Slowing (36%) | | Days since push | 0d | 139d | | Open issues (now) | 18 | 9 | | Owner type | Organization | User | | Full report | [trust report](/tools/langchain-ai-open-swe/trust.md) | [trust report](/tools/moazbuilds-codemachine-cli/trust.md) | ## Decision facts: open-swe - **Adopt for:** open-swe is an open-source asynchronous coding agent that allows customization of components like models, sandboxes, tools, triggers, prompts, and middleware. ## Decision facts: CodeMachine-CLI - **Adopt for:** CodeMachine-CLI is an open-source TypeScript tool that enables developers to create repeatable workflows using AI coding agents. ## Choose when ### Choose open-swe if… - open-swe is primarily Python; CodeMachine-CLI is TypeScript. - License: open-swe is MIT, CodeMachine-CLI is Apache-2.0. - Tags unique to open-swe: agent, anthropic, claudecode, llm. - Also covers Evaluation & Observability. - open-swe ships Docker support for self-hosted deployment. - If you are integrating with Linear/Slack/GitHub workflows specifically as it seems to support these platforms natively. ### Choose CodeMachine-CLI if… - CodeMachine-CLI is primarily TypeScript; open-swe is Python. - License: CodeMachine-CLI is Apache-2.0, open-swe is MIT. - Tags unique to CodeMachine-CLI: automation, cli-tool, code-generation, multi-agent-systems. - Also covers Developer Tools. - CodeMachine-CLI ships an MCP server manifest. - When you need to define and execute complex, multi-step coding workflows involving multiple AI agents for automation or code generation tasks ## When NOT to use open-swe - Not recommended if you require real-time interaction with coding agents instead of asynchronous communication. - Avoid choosing this tool if your project does not align well with customization options provided or if integration complexity outweighs benefits. ## When NOT to use CodeMachine-CLI - If your workflow can be handled by a single AI agent without the need to orchestrate multiple AI-coded agents together - When you require real-time interactive sessions with an AI coding assistant and do not benefit from pre-defined workflows for automation purposes ## Common questions ### What is the difference between open-swe and CodeMachine-CLI? open-swe: An Open-Source Asynchronous Coding Agent. CodeMachine-CLI: Orchestrates AI coding agents into repeatable workflows. See the comparison table for live GitHub stats and shared categories. ### When should I choose open-swe over CodeMachine-CLI? Choose open-swe over CodeMachine-CLI when open-swe is primarily Python; CodeMachine-CLI is TypeScript; License: open-swe is MIT, CodeMachine-CLI is Apache-2.0; Tags unique to open-swe: agent, anthropic, claudecode, llm; Also covers Evaluation & Observability; open-swe ships Docker support for self-hosted deployment; If you are integrating with Linear/Slack/GitHub workflows specifically as it seems to support these platforms natively. ### When should I choose CodeMachine-CLI over open-swe? Choose CodeMachine-CLI over open-swe when CodeMachine-CLI is primarily TypeScript; open-swe is Python; License: CodeMachine-CLI is Apache-2.0, open-swe is MIT; Tags unique to CodeMachine-CLI: automation, cli-tool, code-generation, multi-agent-systems; Also covers Developer Tools; CodeMachine-CLI ships an MCP server manifest; When you need to define and execute complex, multi-step coding workflows involving multiple AI agents for automation or code generation tasks. ### When should I avoid open-swe? Not recommended if you require real-time interaction with coding agents instead of asynchronous communication. Avoid choosing this tool if your project does not align well with customization options provided or if integration complexity outweighs benefits. ### When should I avoid CodeMachine-CLI? If your workflow can be handled by a single AI agent without the need to orchestrate multiple AI-coded agents together When you require real-time interactive sessions with an AI coding assistant and do not benefit from pre-defined workflows for automation purposes ### Is open-swe or CodeMachine-CLI more popular on GitHub? open-swe has more GitHub stars (10,235 vs 2,509). Stars measure visibility, not whether either tool fits your constraints. ### Are open-swe and CodeMachine-CLI open source? Yes - both are open-source projects on GitHub (open-swe: MIT, CodeMachine-CLI: Apache-2.0). ### Where can I find alternatives to open-swe or CodeMachine-CLI? GraphCanon lists graph-backed alternatives at [open-swe alternatives](/tools/langchain-ai-open-swe/alternatives) and [CodeMachine-CLI alternatives](/tools/moazbuilds-codemachine-cli/alternatives) ([open-swe markdown twin](/tools/langchain-ai-open-swe/alternatives.md), [CodeMachine-CLI markdown twin](/tools/moazbuilds-codemachine-cli/alternatives.md)), ranked by typed relationship edges rather than popularity votes. ### Is there a machine-readable version of this comparison? Yes. The markdown twin at [this comparison](/compare/langchain-ai-open-swe-vs-moazbuilds-codemachine-cli.md) mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers. ### Which is better maintained, open-swe or CodeMachine-CLI? open-swe: Very active. CodeMachine-CLI: Slowing. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance. ### Where are the full trust reports for open-swe and CodeMachine-CLI? GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: [open-swe trust report](/tools/langchain-ai-open-swe/trust); [CodeMachine-CLI trust report](/tools/moazbuilds-codemachine-cli/trust). --- **Machine-readable endpoints** - JSON: [`/api/graphcanon/graph?tool=langchain-ai-open-swe`](/api/graphcanon/graph?tool=langchain-ai-open-swe) - LLM index: [/llms.txt](/llms.txt) - Full corpus: [/llms-full.txt](/llms-full.txt) _GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_