freshcrate
Home > Security > swe-rex

swe-rex

Sandboxed code execution for AI agents, locally or on the cloud.

Description

<div align="center"> <a href="https://swe-rex.com"><img src="docs/assets/swe-rex-logo-bg.svg" alt="SWE-ReX" style="height: 7em"/></a> </div> # SWE-agent Remote Execution Framework [![Docs](https://img.shields.io/badge/Docs-green?style=for-the-badge&logo=materialformkdocs&logoColor=white)](https://swe-rex.com/latest/) [![Slack](https://img.shields.io/badge/Slack-4A154B?style=for-the-badge&logo=slack&logoColor=white)](https://join.slack.com/t/swe-bench/shared_invite/zt-36pj9bu5s-o3_yXPZbaH2wVnxnss1EkQ) [![PyPI - Version](https://img.shields.io/pypi/v/swe-rex?style=for-the-badge&logo=python&logoColor=white&labelColor=black&color=deeppink)](https://pypi.org/project/swe-rex/) SWE-ReX is a runtime interface for interacting with sandboxed shell environments, allowing you to effortlessly let your AI agent run *any command* on *any environment*. Whether commands are executed locally or remotely in Docker containers, AWS remote machines, Modal, or something else, your agent code remains the same. Running 100 agents in parallel? No problem either! Specifically, SWE-ReX allows your agent to * ✅ **Interact with running shell sessions**. SWE-ReX will recognize when commands are finished, extract the output and exit code and return them to your agent. * ✅ Let your agent use **interactive command line tools** like `ipython`, `gdb` or more in the shell. * ✅ Interact with **multiple such shell sessions in parallel**, similar to how humans can have a shell, ipython, gdb, etc. all running at the same time. We built SWE-ReX to help you focus on developing and evaluating your agent, not on infrastructure. SWE-ReX came out of our experiences with [SWE-agent][] and [SWE-agent enigma][enigma]. Using SWE-ReX, we * 🦖 Support **fast, massively parallel** agent runs (which made evaluating on large benchmarks a breeze). * 🦖 Support a **broad range of platforms**, including non-Linux machines without Docker. * 🦖 **Disentangle agent logic from infrastructure concerns**, making SWE-agent more stable and easier to maintain. This is [SWE-agent][] using SWE-ReX to run on 30 [SWE-bench][] instances in parallel: <div align="center"> <img src="docs/assets/swerex.gif" alt="SWE-ReX in action" width=600px> </div> ## Get started ```bash pip install swe-rex # With modal support pip install 'swe-rex[modal]' # With fargate support pip install 'swe-rex[fargate]' # With daytona support (WIP) pip install 'swe-rex[daytona]' # Development setup (all optional dependencies) pip install 'swe-rex[dev]' ``` Then head over to [our documentation](https://swe-rex.com/) to learn more! [SWE-agent]: https://swe-agent.com [SWE-bench]: https://swebench.com [enigma]: https://enigma-agent.com/ ## Our other projects <div align="center"> <a href="https://github.com/SWE-agent/SWE-agent"><img src="docs/assets/sweagent_logo_text_below.svg" alt="SWE-agent" height="120px"></a> <!-- <a href="https://github.com/SWE-agent/SWE-ReX"><img src="docs/assets/swerex_logo_text_below.svg" alt="SWE-ReX" height="120px"></a> --> &nbsp;&nbsp; <a href="https://github.com/SWE-agent/mini-SWE-agent"><img src="docs/assets/mini_logo_text_below.svg" alt="Mini-SWE-Agent" height="120px"></a> &nbsp;&nbsp; <a href="https://github.com/SWE-bench/SWE-smith"><img src="docs/assets/swesmith_logo_text_below.svg" alt="SWE-smith" height="120px"></a> &nbsp;&nbsp; <a href="https://github.com/SWE-bench/SWE-bench"><img src="docs/assets/swebench_logo_text_below.svg" alt="SWE-bench" height="120px"></a> &nbsp;&nbsp; <a href="https://github.com/SWE-bench/sb-cli"><img src="docs/assets/sbcli_logo_text_below.svg" alt="sb-cli" height="120px"></a> </div>

Release History

VersionChangesUrgencyDate
1.4.0Imported from PyPI (1.4.0)Low4/21/2026
v1.4.0## What's Changed v1.4.0 brings support for Daytona as a backend (thanks @Tpuljak). @joyliu-q and @saltzm improved the stability of remote connections with any cloud backend. It also ships a fix for the hardcoded value of the python runtime (standalone python) that caused docker build failures when running in the default configuration with SWE-agent and other projects (thanks @sinha-scripts) ## Features * feat: add daytona deployment by @Tpuljak in https://github.com/SWE-agent/SWE-Low8/14/2025
v1.2.1# 1.2.1 (03/04/25) ## Fixed * `TemporaryDirectory` cleanup issues on Windows in https://github.com/SWE-agent/SWE-ReX/pull/181 ## Enhanced * Message about building docker images in https://github.com/SWE-agent/SWE-ReX/pull/178 **Full Changelog**: https://github.com/SWE-agent/SWE-ReX/compare/v1.2.0...v1.2.1Low3/5/2025
v1.2.0## What's Changed * Add platform flag to Deployment config for docker builds on different platforms by @carlosejimenez in https://github.com/SWE-agent/SWE-ReX/pull/165 * Fix: Avoid exceptions from Deployment.__del__ by @klieret in https://github.com/SWE-agent/SWE-ReX/pull/170 * Enh: Validate image ID by @klieret in https://github.com/SWE-agent/SWE-ReX/pull/173 **Full Changelog**: https://github.com/SWE-agent/SWE-ReX/compare/v1.1.1...v1.2.0Low2/25/2025

Dependencies & License Audit

Loading dependencies...

Similar Packages

azure-identityMicrosoft Azure Identity Library for Pythonazure-template_0.1.0b6187637
azure-keyvault-secretsMicrosoft Corporation Key Vault Secrets Client Library for Pythonazure-template_0.1.0b6187637
azure-storage-queueMicrosoft Azure Azure Queue Storage Client Library for Pythonazure-template_0.1.0b6187637
azure-data-tablesMicrosoft Azure Azure Data Tables Client Library for Pythonazure-template_0.1.0b6187637
azure-appconfigurationMicrosoft App Configuration Data Client Library for Pythonazure-template_0.1.0b6187637