Skip to content

Commit 9139eb9

Browse files
jty1128jty1128
committed
Initial commit: Fork from SWE-agent
0 parents  commit 9139eb9

299 files changed

Lines changed: 25264 additions & 0 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.cursor/rules/general.mdc‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
description:
3+
globs:
4+
alwaysApply: true
5+
---
6+
7+
# Your rule content
8+
9+
- Use python with type annotations
10+
- Target python 3.11 or higher
11+
- Use `pathlib` instead of `os.path`. Also use `Path.read_text()` over `with ...open()` constructs
12+
- Use `argparse` to add interfaces
13+
- Keep code comments to a minimum and only highlight particularly logically challenging things
14+
- Do not append to the README unless specifically requested

‎.cursor/rules/project-overview.mdc‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
description:
3+
globs:
4+
alwaysApply: true
5+
---
6+
# SWE-agent overview
7+
8+
SWE-agent implements an AI software engineering agent that uses language models to
9+
fix github issues.
10+
Here's what you need to know about the project structure:
11+
12+
- The main entry points to running are in the `sweagent/run`, in particular `run_single.py` and `run_batch.py`, where the latter is used for benchmarking.
13+
- The main class that governs agent behavior is `sweagent/agent/agents.py`
14+
- The AI agent proposes actions that are executed in sandboxed docker containers
15+
- At the beginning of an agent class, we initialize a `SWEEnv` class from `sweagent/environment/swe_env.py`. This class interfaces with the SWE-ReX project to interface with the sandboxed docker containers
16+
- Part of the SWE-agent project are tools in `tools/`. They are organized in bundles. These bundles are copied to the sandboxed container and made available in the $PATH variable.
17+
- In addition we provide two "inspectors" that allow to inspect trajectories (the output files of agents), `inspector_cli.py` provides a command line interface and `sweagent/inspector/server.py` a web interface.

‎.devcontainer/README.md‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
# .devcontainer
2+
3+
The files in this directory configure a VSCode environment like
4+
GitHub codespaces.

‎.devcontainer/bashrc_epilog.sh‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
2+
if [ -z "$(docker images -q sweagent/swe-agent 2> /dev/null)" ]; then
3+
echo "⚠️ Please wait for the postCreateCommand to start and finish (a new window will appear shortly) ⚠️"
4+
fi
5+
6+
echo "Here's an example SWE-agent command to try out:"
7+
8+
echo "sweagent run \\
9+
--agent.model.name=claude-sonnet-4-20250514 \\
10+
--agent.model.per_instance_cost_limit=2.00 \\
11+
--env.repo.github_url=https://github.com/SWE-agent/test-repo \\
12+
--problem_statement.github_url=https://github.com/SWE-agent/test-repo/issues/1 \\
13+
"

‎.devcontainer/devcontainer.json‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
{
2+
"name": "SWE-Agent Codespace",
3+
"image": "mcr.microsoft.com/vscode/devcontainers/miniconda:0-3",
4+
"customizations":{
5+
"vscode":{
6+
"extensions": [
7+
"ms-python.python",
8+
"ms-azuretools.vscode-docker",
9+
"ms-toolsai.jupyter"
10+
]
11+
}
12+
},
13+
"onCreateCommand": "./.devcontainer/oncreate.sh",
14+
"postCreateCommand": "./.devcontainer/postcreate.sh",
15+
"features": {
16+
"ghcr.io/devcontainers/features/docker-in-docker:2": {}
17+
},
18+
"mounts": [
19+
"source=/var/run/docker.sock,target=/var/run/docker.sock,type=bind"
20+
],
21+
"remoteUser": "vscode"
22+
}

‎.devcontainer/oncreate.sh‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
#!/usr/bin/env bash
2+
3+
set -euo pipefail
4+
set -x
5+
6+
# Run from repo root
7+
8+
sudo usermod -aG docker vscode
9+
sudo chmod 666 /var/run/docker.sock
10+
pip install -e '.'
11+
cp .devcontainer/sample_keys.cfg keys.cfg
12+
cat .devcontainer/bashrc_epilog.sh >> ~/.bashrc

‎.devcontainer/postcreate.sh‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
#!/usr/bin/env bash
2+
3+
set -euo pipefail
4+
set -x
5+
6+
pip install -e '.'

‎.devcontainer/sample_keys.cfg‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
# All keys are commented out by default. Make sure to remove the leading '#' of the relevant lines
2+
# GITHUB_TOKEN: 'GitHub Token to clone private repos'
3+
# OPENAI_API_KEY: 'OpenAI API Key Here if using OpenAI Model'
4+
# ANTHROPIC_API_KEY: 'Anthropic API Key Here if using Anthropic Model'
5+
# TOGETHER_API_KEY: 'Together API Key Here if using Together Model'
6+
# AZURE_OPENAI_API_KEY: 'Azure OpenAI API Key Here if using Azure OpenAI Model'
7+
# AZURE_OPENAI_ENDPOINT: 'Azure OpenAI Endpoint Here if using Azure OpenAI Model'
8+
# AZURE_OPENAI_DEPLOYMENT: 'Azure OpenAI Deployment Here if using Azure OpenAI Model'
9+
# AZURE_OPENAI_API_VERSION: 'Azure OpenAI API Version Here if using Azure OpenAI Model'
10+
# OPENAI_API_BASE_URL: 'LM base URL here if using Local or alternative api Endpoint'
11+
# GROQ_API_KEY: 'Groq Models API Key'

‎.git-blame-ignore-revs‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
# Trailing whitespace & black
2+
51699eb03c3c4f36d4b5ef2725f7bd5223874da7
3+
70ba97190a781705203ba838bfe0fb8be7cfa32f
4+
83988093c08ab5f1cb999f97fc3745f3d3af306f
5+
# Code quality: Convert to make use of PEP 585 and PEP 604
6+
29a4c6dfb6cceff5e657c707ce809bc78f33b778
7+
# Sort imports
8+
f873761e6760a844c1788cb5f4e42de401ab2c38

‎.github/CODE_OF_CONDUCT.md‎

Lines changed: 134 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,134 @@
1+
2+
# Contributor Covenant Code of Conduct
3+
4+
## Our Pledge
5+
6+
We as members, contributors, and leaders pledge to make participation in our
7+
community a harassment-free experience for everyone, regardless of age, body
8+
size, visible or invisible disability, ethnicity, sex characteristics, gender
9+
identity and expression, level of experience, education, socio-economic status,
10+
nationality, personal appearance, race, caste, color, religion, or sexual
11+
identity and orientation.
12+
13+
We pledge to act and interact in ways that contribute to an open, welcoming,
14+
diverse, inclusive, and healthy community.
15+
16+
## Our Standards
17+
18+
Examples of behavior that contributes to a positive environment for our
19+
community include:
20+
21+
* Demonstrating empathy and kindness toward other people
22+
* Being respectful of differing opinions, viewpoints, and experiences
23+
* Giving and gracefully accepting constructive feedback
24+
* Accepting responsibility and apologizing to those affected by our mistakes,
25+
and learning from the experience
26+
* Focusing on what is best not just for us as individuals, but for the overall
27+
community
28+
29+
Examples of unacceptable behavior include:
30+
31+
* The use of sexualized language or imagery, and sexual attention or advances of
32+
any kind
33+
* Trolling, insulting or derogatory comments, and personal or political attacks
34+
* Public or private harassment
35+
* Publishing others' private information, such as a physical or email address,
36+
without their explicit permission
37+
* Other conduct which could reasonably be considered inappropriate in a
38+
professional setting
39+
40+
## Enforcement Responsibilities
41+
42+
Community leaders are responsible for clarifying and enforcing our standards of
43+
acceptable behavior and will take appropriate and fair corrective action in
44+
response to any behavior that they deem inappropriate, threatening, offensive,
45+
or harmful.
46+
47+
Community leaders have the right and responsibility to remove, edit, or reject
48+
comments, commits, code, wiki edits, issues, and other contributions that are
49+
not aligned to this Code of Conduct, and will communicate reasons for moderation
50+
decisions when appropriate.
51+
52+
## Scope
53+
54+
This Code of Conduct applies within all community spaces, and also applies when
55+
an individual is officially representing the community in public spaces.
56+
Examples of representing our community include using an official email address,
57+
posting via an official social media account, or acting as an appointed
58+
representative at an online or offline event.
59+
60+
## Enforcement
61+
62+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
63+
reported to the community leaders responsible for enforcement at
64+
[INSERT CONTACT METHOD].
65+
All complaints will be reviewed and investigated promptly and fairly.
66+
67+
All community leaders are obligated to respect the privacy and security of the
68+
reporter of any incident.
69+
70+
## Enforcement Guidelines
71+
72+
Community leaders will follow these Community Impact Guidelines in determining
73+
the consequences for any action they deem in violation of this Code of Conduct:
74+
75+
### 1. Correction
76+
77+
**Community Impact**: Use of inappropriate language or other behavior deemed
78+
unprofessional or unwelcome in the community.
79+
80+
**Consequence**: A private, written warning from community leaders, providing
81+
clarity around the nature of the violation and an explanation of why the
82+
behavior was inappropriate. A public apology may be requested.
83+
84+
### 2. Warning
85+
86+
**Community Impact**: A violation through a single incident or series of
87+
actions.
88+
89+
**Consequence**: A warning with consequences for continued behavior. No
90+
interaction with the people involved, including unsolicited interaction with
91+
those enforcing the Code of Conduct, for a specified period of time. This
92+
includes avoiding interactions in community spaces as well as external channels
93+
like social media. Violating these terms may lead to a temporary or permanent
94+
ban.
95+
96+
### 3. Temporary Ban
97+
98+
**Community Impact**: A serious violation of community standards, including
99+
sustained inappropriate behavior.
100+
101+
**Consequence**: A temporary ban from any sort of interaction or public
102+
communication with the community for a specified period of time. No public or
103+
private interaction with the people involved, including unsolicited interaction
104+
with those enforcing the Code of Conduct, is allowed during this period.
105+
Violating these terms may lead to a permanent ban.
106+
107+
### 4. Permanent Ban
108+
109+
**Community Impact**: Demonstrating a pattern of violation of community
110+
standards, including sustained inappropriate behavior, harassment of an
111+
individual, or aggression toward or disparagement of classes of individuals.
112+
113+
**Consequence**: A permanent ban from any sort of public interaction within the
114+
community.
115+
116+
## Attribution
117+
118+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
119+
version 2.1, available at
120+
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
121+
122+
Community Impact Guidelines were inspired by
123+
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
124+
125+
For answers to common questions about this code of conduct, see the FAQ at
126+
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
127+
[https://www.contributor-covenant.org/translations][translations].
128+
129+
[homepage]: https://www.contributor-covenant.org
130+
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
131+
[Mozilla CoC]: https://github.com/mozilla/diversity
132+
[FAQ]: https://www.contributor-covenant.org/faq
133+
[translations]: https://www.contributor-covenant.org/translations
134+

0 commit comments

Comments
 (0)