@elizaos/sweagent-root 2.0.0-alpha

package/python/trajectories/demonstrations/str_replace_anthropic_demo.yaml

@@ -0,0 +1,432 @@
+# This is a demo file generated from trajectory file:
+# /Users/fuchur/Documents/24/git_sync/SWE-agent/trajectories/fuchur/replay___1c2844.demo/1c2844.traj
+# You can use this demo file to replay the actions in the trajectory with run_replay.py.
+# You can edit the content of the actions in this file to modify the replay behavior.
+# NOTICE:
+#         Only the actions of the assistant will be replayed.
+#         You do not need to modify the observation's contents or any other fields.
+#         You can add or remove actions to modify the replay behavior.
+history:
+  - role: user
+    content: |-
+      I've uploaded a python code repository in the directory . Consider the following PR description:
+
+      <pr_description>
+      I'm running `missing_colon.py` as follows:
+
+      ```python
+      division(23, 0)
+      ```
+
+      but I get the following error:
+
+      ```
+        File "/Users/fuchur/Documents/24/git_sync/swe-agent-test-repo/tests/./missing_colon.py", line 4
+          def division(a: float, b: float) -> float
+                                                   ^
+      SyntaxError: invalid syntax
+      ```
+
+      </pr_description>
+
+      Can you help me implement the necessary changes to the repository so that the requirements specified in the <pr_description> are met?
+      I've already taken care of all changes to any of the test files described in the <pr_description>. This means you DON'T have to modify the testing logic or any of the tests in any way!
+      Your task is to make the minimal changes to non-tests files in the  directory to ensure the <pr_description> is satisfied.
+      Follow these steps to resolve the issue:
+      1. As a first step, it might be a good idea to find and read code relevant to the <pr_description>
+      2. Create a script to reproduce the error and execute it with `python <filename.py>` using the bash tool, to confirm the error
+      3. Edit the sourcecode of the repo to resolve the issue
+      4. Rerun your reproduce script and confirm that the error is fixed!
+      5. Think about edgecases and make sure your fix handles them as well
+      Your thinking should be thorough and so it's fine if it's very long.
+
+      (Open file: )
+      (Current directory: )
+      bash-$
+    agent: main
+    message_type: observation
+  - role: assistant
+    content: Let’s start by exploring the repository structure.
+    agent: main
+    tool_calls:
+      - function:
+          arguments: '{"command":"view","path":"/swe-agent-test-repo"}'
+          name: str_replace_editor
+        id: call_ggIm89M8rcBQorveMgkIrL7G
+        type: function
+    message_type: action
+  - role: tool
+    content: |-
+      Here's the files and directories up to 2 levels deep in /swe-agent-test-repo, excluding hidden items:
+      /swe-agent-test-repo
+      /swe-agent-test-repo/pyproject.toml
+      /swe-agent-test-repo/src
+      /swe-agent-test-repo/src/testpkg
+      /swe-agent-test-repo/problem_statements
+      /swe-agent-test-repo/problem_statements/1.md
+      /swe-agent-test-repo/problem_statements/1a.md
+      /swe-agent-test-repo/problem_statements/22.md
+      /swe-agent-test-repo/tests
+      /swe-agent-test-repo/tests/test_tribonaccy.py
+      /swe-agent-test-repo/tests/existing_lint_error.py
+      /swe-agent-test-repo/tests/missing_colon.py
+      /swe-agent-test-repo/tests/filetoread.txt
+      /swe-agent-test-repo/README.md
+      (Open file: )
+      (Current directory: )
+      bash-$
+    agent: main
+    message_type: observation
+    tool_call_ids:
+      - call_ggIm89M8rcBQorveMgkIrL7G
+  - role: assistant
+    content: We have several Python files in the repository. `missing_colon.py` is directly mentioned in the PR description, so let's open it.
+    agent: main
+    tool_calls:
+      - function:
+          arguments: '{"command":"view","path":"/swe-agent-test-repo/src/testpkg/missing_colon.py"}'
+          name: str_replace_editor
+        id: call_QbSqph4VzA951X9eMEgsvyOm
+        type: function
+    message_type: action
+  - role: tool
+    content: |-
+      Here's the result of running `cat -n` on /swe-agent-test-repo/src/testpkg/missing_colon.py:
+           1	#!/usr/bin/env python3
+           2
+           3
+           4	def division(a: float, b: float) -> float
+           5	    return a/b
+           6
+           7
+           8	if __name__ == "__main__":
+           9	    print(division(123, 15))
+          10
+          11
+      (Open file: )
+      (Current directory: )
+      bash-$
+    agent: main
+    message_type: observation
+    tool_call_ids:
+      - call_QbSqph4VzA951X9eMEgsvyOm
+  - role: assistant
+    content: We can see that the file contains a missing colon. Let's fix it by replacing the line with the correct version.
+    agent: main
+    tool_calls:
+      - function:
+          arguments: '{"command":"str_replace","path":"/swe-agent-test-repo/src/testpkg/missing_colon.py","old_str":"def division(a: float, b: float) -> float","new_str":"def division(a: float, b: float) -> float:"}'
+          name: str_replace_editor
+        id: call_QgE1MNhZQ2W66DgwRZGXEo1D
+        type: function
+    message_type: action
+  - role: tool
+    content: |-
+      The file /swe-agent-test-repo/src/testpkg/missing_colon.py has been edited. Here's the result of running `cat -n` on a snippet of /swe-agent-test-repo/src/testpkg/missing_colon.py:
+           1	#!/usr/bin/env python3
+           2
+           3
+           4	def division(a: float, b: float) -> float:
+           5	    return a/b
+           6
+           7
+           8	if __name__ == "__main__":
+      Review the changes and make sure they are as expected. Edit the file again if necessary.
+      (Open file: )
+      (Current directory: )
+      bash-$
+    agent: main
+    message_type: observation
+    tool_call_ids:
+      - call_QgE1MNhZQ2W66DgwRZGXEo1D
+  - role: assistant
+    content: The missing colon has been fixed. The change should not break any existing functionality. Let's submit the changes.
+    agent: main
+    tool_calls:
+      - function:
+          arguments: '{}'
+          name: submit
+        id: call_zyAyd9wbLeSeRaFXrKwlQYwI
+        type: function
+    message_type: action
+  - role: tool
+    content: |2-
+
+      diff --git a/src/testpkg/missing_colon.py b/src/testpkg/missing_colon.py
+      index 20edef5..5857437 100755
+      --- a/src/testpkg/missing_colon.py
+      +++ b/src/testpkg/missing_colon.py
+      @@ -1,7 +1,7 @@
+       #!/usr/bin/env python3
+
+
+      -def division(a: float, b: float) -> float
+      +def division(a: float, b: float) -> float:
+           return a/b
+
+
+
+      (Open file: )
+      (Current directory: )
+      bash-$
+    agent: main
+    message_type: observation
+    tool_call_ids:
+      - call_zyAyd9wbLeSeRaFXrKwlQYwI
+replay_config:
+  env:
+    deployment:
+      image: tiny
+      port:
+      docker_args: []
+      startup_timeout: 180.0
+      pull: missing
+      remove_images: false
+      type: docker
+    repo:
+      path: /Users/fuchur/Documents/24/git_sync/swe-agent-test-repo
+      base_commit: HEAD
+      type: local
+    post_startup_commands: []
+    name: main
+  agent:
+    name: main
+    templates:
+      system_template: |-
+        You are a helpful assistant that can interact with a computer to solve tasks.
+
+        <IMPORTANT>
+        * If user provides a path, you should NOT assume it's relative to the current working directory. Instead, you should explore the file system to find the file before working on it.
+        * Do not try to install any packages with `pip`, `conda`, or any other way. This will usually not work. If the environment is not set up correctly, try to fix the issue without executing python code or running any tests that require the package installed.
+        </IMPORTANT>
+
+        The special interface consists of a file editor that shows you {{WINDOW}} lines of a file at a time.
+        In addition to typical bash commands, you can also use specific commands to help you navigate and edit files.
+        To call a command, you need to invoke it with a function call/tool call.
+
+        <notes>
+        Please note that THE EDIT COMMAND REQUIRES PROPER INDENTATION.
+
+        For example, if you are looking at this file:
+
+        def fct():
+            print("Hello world")
+
+        and you want to edit the file to read:
+
+        def fct():
+            print("Hello")
+            print("world")
+
+        you search string should be `Hello world` and your replace string should be `"Hello"\n    print("world")`
+        (note the extra spaces before the print statement!).
+
+        You could also get the same result by search for `    print("Hello world")` and replace with `    print("Hello")\n    print("world")`.
+        </notes>
+        <response_format>
+        Your shell prompt is formatted as follows:
+        (Open file: <path>)
+        (Current directory: <cwd>)
+        bash-$
+
+        First, you should _always_ include a general thought about what you're going to do next.
+        Then, for every response, you must include exactly _ONE_ tool call/function call.
+
+        Remember, you should always include a _SINGLE_ tool call/function call and then wait for a response from the shell before continuing with more discussion and commands. Everything you include in the DISCUSSION section will be saved for future reference.
+        If you'd like to issue two commands at once, PLEASE DO NOT DO THAT! Please instead first submit just the first tool call, and then after receiving a response you'll be able to issue the second .
+        Note that the environment does NOT support interactive session commands (e.g. python, vim), so please do not invoke them.
+        </response_format>
+      instance_template: |-
+        I've uploaded a python code repository in the directory {{working_dir}}. Consider the following PR description:
+
+        <pr_description>
+        {{problem_statement}}
+        </pr_description>
+
+        Can you help me implement the necessary changes to the repository so that the requirements specified in the <pr_description> are met?
+        I've already taken care of all changes to any of the test files described in the <pr_description>. This means you DON'T have to modify the testing logic or any of the tests in any way!
+        Your task is to make the minimal changes to non-tests files in the {{working_dir}} directory to ensure the <pr_description> is satisfied.
+        Follow these steps to resolve the issue:
+        1. As a first step, it might be a good idea to find and read code relevant to the <pr_description>
+        2. Create a script to reproduce the error and execute it with `python <filename.py>` using the bash tool, to confirm the error
+        3. Edit the sourcecode of the repo to resolve the issue
+        4. Rerun your reproduce script and confirm that the error is fixed!
+        5. Think about edgecases and make sure your fix handles them as well
+        Your thinking should be thorough and so it's fine if it's very long.
+
+        (Open file: {{open_file}})
+        (Current directory: {{working_dir}})
+        bash-$
+      next_step_template: |-
+        {{observation}}
+        (Open file: {{open_file}})
+        (Current directory: {{working_dir}})
+        bash-$
+      next_step_no_output_template: |-
+        Your command ran successfully and did not produce any output.
+        (Open file: {{open_file}})
+        (Current directory: {{working_dir}})
+        bash-$
+      strategy_template:
+      demonstration_template: |
+        Here is a demonstration of how to correctly accomplish this task.
+        It is included to show you how to correctly use the interface.
+        You do not need to follow exactly what is done in the demonstration.
+        --- DEMONSTRATION ---
+        {{demonstration}}
+        --- END OF DEMONSTRATION ---
+      demonstrations:
+        - trajectories/demonstrations/function_calling_simple.traj
+      put_demos_in_history: true
+      shell_check_error_template: |-
+        Your bash command contained syntax errors and was NOT executed. Please fix the syntax errors and try again. This can be the result of not adhering to the syntax for multi-line commands. Here is the output of `bash -n`:
+        {{bash_stdout}}
+        {{bash_stderr}}
+      command_cancelled_timeout_template: The command '{{command}}' was cancelled because it took more than {{timeout}} seconds. Please try a different command that completes more quickly.
+    tools:
+      filter:
+        blocklist_error_template: Operation '{{action}}' is not supported by this environment.
+        blocklist:
+          - vim
+          - vi
+          - emacs
+          - nano
+          - nohup
+          - git
+          - gdb
+          - less
+          - tail -f
+          - python -m venv
+        blocklist_standalone:
+          - python
+          - python3
+          - ipython
+          - bash
+          - sh
+          - /bin/bash
+          - /bin/sh
+          - nohup
+          - vi
+          - vim
+          - emacs
+          - nano
+          - su
+        block_unless_regex:
+          radare2: \b(?:radare2)\b.*\s+-c\s+.*
+          r2: \b(?:radare2)\b.*\s+-c\s+.*
+      bundles:
+        - path: tools/edit_anthropic
+          hidden_tools: []
+        - path: tools/submit
+          hidden_tools: []
+      env_variables:
+        WINDOW: 100
+        OVERLAP: 2
+      submit_command: submit
+      parse_function:
+        error_message: |
+          {%- if error_code == "missing" -%}
+          Your last output did not use any tool calls!
+          Please make sure your output includes exactly _ONE_ function call!
+          You must invoke the function directly using the function call format.
+          You cannot invoke commands with ```, you have to use the function call format.
+          If you think you have already resolved the issue, please submit your changes by running the `submit` command.
+          If you think you cannot solve the problem, please run `exit_forfeit` (if available).
+          Else, please continue with a new tool call!
+          {%- elif error_code == "multiple" -%}
+          Your last output included multiple tool calls!
+          Please make sure your output includes a thought and exactly _ONE_ function call.
+          {%- elif error_code == "unexpected_arg" -%}
+          Your action could not be parsed properly: {{exception_message}}.
+          Make sure your function call doesn't include any extra arguments that are not in the allowed arguments, and only use the allowed commands.
+          {%- else -%}
+          Your action could not be parsed properly: {{exception_message}}.
+          {% endif %}
+        type: function_calling
+      enable_bash_tool: true
+      format_error_template: |
+        {%- if error_code == "missing" -%}
+        Your last output did not use any tool calls!
+        Please make sure your output includes exactly _ONE_ function call!
+        You must invoke the function directly using the function call format.
+        You cannot invoke commands with ```, you have to use the function call format.
+        If you think you have already resolved the issue, please submit your changes by running the `submit` command.
+        If you think you cannot solve the problem, please run `exit_forfeit` (if available).
+        Else, please continue with a new tool call!
+        {%- elif error_code == "multiple" -%}
+        Your last output included multiple tool calls!
+        Please make sure your output includes a thought and exactly _ONE_ function call.
+        {%- elif error_code == "unexpected_arg" -%}
+        Your action could not be parsed properly: {{exception_message}}.
+        Make sure your function call doesn't include any extra arguments that are not in the allowed arguments, and only use the allowed commands.
+        {%- else -%}
+        Your action could not be parsed properly: {{exception_message}}.
+        {% endif %}
+      command_docs: |+
+        bash:
+          docstring: runs the given command directly in bash
+          signature: <command>
+          arguments:
+            - command (string) [required]: a command to run directly in the current shell
+
+        str_replace_editor:
+          docstring: Create, view, or edit a file.
+
+          signature: str_replace_editor <command> <path> [<file_text>] [<view_range>] [<old_str>] [<new_str>] [<insert_line>]
+
+          arguments:
+            - command (string) [required]: command to run: view, create, str_replace, insert, undo_edit
+            - path (string) [required]: path to file
+            - file_text (string) [optional]: Text to insert when evoking `create` (required for `create`)
+            - view_range (array) [optional]: Range of lines to display when evoking `view`. If not provided, the entire file is displayed.
+            - old_str (string) [optional]: String to replace when evoking `str_replace`
+            - new_str (string) [optional]: Replacement string when evoking `str_replace`
+            - insert_line (integer) [optional]: Required for `insert`: Line number to insert text after.
+
+        submit:
+          docstring: submits the current file
+          signature: submit
+
+      multi_line_command_endings: {}
+      submit_command_end_name:
+      reset_commands: []
+      execution_timeout: 30
+      install_timeout: 300
+    history_processors:
+      - n: 5
+        always_remove_output_for_tags:
+          - remove_output
+        always_keep_output_for_tags:
+          - keep_output
+        type: last_n_observations
+    model:
+      name: replay
+      per_instance_cost_limit: 3.0
+      total_cost_limit: 0.0
+      temperature: 1.0
+      top_p: 1.0
+      api_base:
+      api_version:
+      api_key:
+      stop: []
+      completion_kwargs: {}
+      convert_system_to_user: false
+      retry:
+        retries: 5
+        min_wait: 1.0
+        max_wait: 15.0
+      delay: 0.0
+      fallbacks: []
+    max_requeries: 3
+  problem_statement:
+    path: /Users/fuchur/Documents/24/git_sync/swe-agent-test-repo/problem_statements/1.md
+    extra_fields: {}
+    type: text_file
+    id: 1c2844
+  output_dir: DEFAULT
+  actions:
+    open_pr: false
+    pr_config:
+      skip_if_commits_reference_issue: true
+    apply_patch_locally: false
+  env_var_path:

package/rust/Cargo.toml

@@ -0,0 +1,100 @@
+[package]
+name = "elizaos-sweagent"
+version = "2.0.0"
+edition = "2021"
+authors = ["elizaOS Contributors"]
+description = "SWE-agent: Software Engineering Agent - Rust implementation with native and WASM support"
+license = "MIT"
+repository = "https://github.com/elizaos/eliza"
+keywords = ["ai", "agent", "software-engineering", "automation", "swe-agent"]
+categories = ["development-tools", "command-line-utilities"]
+readme = "README.md"
+
+[lib]
+crate-type = ["cdylib", "rlib"]
+
+[features]
+default = ["native"]
+native = ["tokio/full", "reqwest/default-tls"]
+wasm = ["wasm-bindgen", "wasm-bindgen-futures", "js-sys", "web-sys", "console_error_panic_hook", "getrandom/js", "reqwest/rustls-tls"]
+
+[dependencies]
+# HTTP client
+reqwest = { version = "0.12", default-features = false, features = ["json"] }
+
+# Serialization
+serde = { version = "1.0", features = ["derive"] }
+serde_json = "1.0"
+serde_yaml = "0.9"
+
+# Async runtime
+async-trait = "0.1"
+futures = "0.3"
+
+# Error handling
+thiserror = "2.0"
+anyhow = "1.0"
+
+# Logging
+tracing = "0.1"
+tracing-subscriber = { version = "0.3", features = ["env-filter"] }
+
+# UUID handling
+uuid = { version = "1.19", features = ["v4", "serde"] }
+
+# Regex for parsing
+regex = "1.10"
+
+# Template rendering
+handlebars = "6.0"
+
+# Command line interface
+clap = { version = "4.5", features = ["derive"] }
+
+# Docker interaction
+bollard = { version = "0.18", optional = true }
+
+# Git operations
+git2 = { version = "0.20", optional = true }
+
+# File globbing
+glob = "0.3"
+
+# Path manipulation
+pathdiff = "0.2"
+
+# Time utilities
+chrono = { version = "0.4", features = ["serde"] }
+
+# Random number generation
+rand = "0.8"
+
+# Environment loading
+dotenvy = "0.15"
+
+# Native-only dependencies
+tokio = { version = "1.0", features = ["rt-multi-thread", "macros", "process", "fs", "io-util", "sync"], optional = true }
+
+# WASM-only dependencies
+wasm-bindgen = { version = "0.2", optional = true }
+wasm-bindgen-futures = { version = "0.4", optional = true }
+js-sys = { version = "0.3", optional = true }
+web-sys = { version = "0.3", features = ["console"], optional = true }
+console_error_panic_hook = { version = "0.1", optional = true }
+getrandom = { version = "0.2", optional = true }
+
+[dev-dependencies]
+tokio = { version = "1.0", features = ["rt-multi-thread", "macros"] }
+pretty_assertions = "1.0"
+dotenvy = "0.15"
+tempfile = "3.10"
+rand = "0.8"
+
+[profile.release]
+lto = true
+opt-level = "z"
+
+[[bin]]
+name = "sweagent"
+path = "src/bin/sweagent.rs"
+required-features = ["native"]

package/rust/README.md

@@ -0,0 +1,49 @@
+# SWE-agent Rust Implementation
+
+Rust implementation of SWE-agent with native and WebAssembly support.
+
+## Features
+
+- **Native Feature** (default): Full async support with Tokio
+- **WASM Feature**: WebAssembly support for browser environments
+
+## Usage
+
+```rust
+use elizaos_sweagent::run::{RunSingle, RunSingleConfig};
+
+#[tokio::main]
+async fn main() -> anyhow::Result<()> {
+    let config = RunSingleConfig::default();
+    let mut runner = RunSingle::from_config(config)?;
+    let result = runner.run().await?;
+    println!("Exit status: {:?}", result.info.exit_status);
+    Ok(())
+}
+```
+
+## Building
+
+```bash
+# Build native
+cargo build --release
+
+# Build for WASM
+cargo build --target wasm32-unknown-unknown --features wasm --no-default-features
+```
+
+## Testing
+
+```bash
+cargo test
+```
+
+## CLI
+
+```bash
+cargo run --bin sweagent -- run --help
+```
+
+## License
+
+MIT