Resolve merge conflict in agent_session.py

.github/ISSUE_TEMPLATE/bug_template.yml

@@ -30,7 +30,6 @@ body:
       description: How are you running OpenHands?
       options:
         - Docker command in README
-        - GitHub resolver
         - Development workflow
         - app.all-hands.dev
         - Other

.github/dependabot.yml

@@ -10,6 +10,12 @@ updates:
       pre-commit:
         patterns:
           - "pre-commit"
+      llama:
+        patterns:
+          - "llama*"
+      chromadb:
+        patterns:
+          - "chromadb"
       browsergym:
         patterns:
           - "browsergym*"

.github/pull_request_template.md

@@ -1,12 +1,11 @@
-- [ ] This change is worth documenting at https://docs.all-hands.dev/
-- [ ] Include this change in the Release Notes. If checked, you **must** provide an **end-user friendly** description for your change below
+**End-user friendly description of the problem this fixes or functionality that this introduces**
+
+- [ ] Include this change in the Release Notes. If checked, you must provide an **end-user friendly** description for your change below
+
+---
+**Give a summary of what the PR does, explaining any non-trivial design decisions**
 
-**End-user friendly description of the problem this fixes or functionality that this introduces.**
 
 
 ---
-**Give a summary of what the PR does, explaining any non-trivial design decisions.**
-
-
----
-**Link of any specific issues this addresses.**
+**Link of any specific issues this addresses**

.github/workflows/clean-up.yml

@@ -46,7 +46,7 @@ on:
 
 jobs:
   del_runs:
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     permissions:
       actions: write
       contents: read

.github/workflows/deploy-docs.yml

@@ -24,20 +24,22 @@ jobs:
   build:
     if: github.repository == 'All-Hands-AI/OpenHands'
     name: Build Docusaurus
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
         with:
           fetch-depth: 0
-      - uses: useblacksmith/setup-node@v5
+      - uses: actions/setup-node@v4
         with:
           node-version: 18
           cache: npm
           cache-dependency-path: docs/package-lock.json
       - name: Set up Python
-        uses: useblacksmith/setup-python@v6
+        uses: actions/setup-python@v5
         with:
           python-version: '3.12'
+      - name: Generate Python Docs
+        run: rm -rf docs/modules/python && pip install pydoc-markdown && pydoc-markdown
       - name: Install dependencies
         run: cd docs && npm ci
       - name: Build website
@@ -52,7 +54,7 @@ jobs:
   deploy:
     if: github.ref == 'refs/heads/main' && github.repository == 'All-Hands-AI/OpenHands'
     name: Deploy to GitHub Pages
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     # This job only runs on "main" so only run one of these jobs at a time
     # otherwise it will fail if one is already running
     concurrency:

.github/workflows/dummy-agent-test.yml

@@ -16,27 +16,37 @@ concurrency:
 
 jobs:
   test:
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
+      - name: Free Disk Space (Ubuntu)
+        uses: jlumbroso/free-disk-space@main
+        with:
+          # this might remove tools that are actually needed,
+          # if set to "true" but frees about 6 GB
+          tool-cache: true
+          # all of these default to true, but feel free to set to
+          # "false" if necessary for your workflow
+          android: true
+          dotnet: true
+          haskell: true
+          large-packages: true
+          docker-images: false
+          swap-storage: true
       - name: Set up Docker Buildx
         id: buildx
         uses: docker/setup-buildx-action@v3
       - name: Install tmux
         run: sudo apt-get update && sudo apt-get install -y tmux
-      - name: Setup Node.js
-        uses: useblacksmith/setup-node@v5
-        with:
-          node-version: '22.x'
       - name: Install poetry via pipx
         run: pipx install poetry
       - name: Set up Python
-        uses: useblacksmith/setup-python@v6
+        uses: actions/setup-python@v5
         with:
           python-version: '3.12'
           cache: 'poetry'
       - name: Install Python dependencies using Poetry
-        run: poetry install --without evaluation
+        run: poetry install --without evaluation,llama-index
       - name: Build Environment
         run: make build
       - name: Run tests

.github/workflows/eval-runner.yml

@@ -0,0 +1,139 @@
+name: Run SWE-Bench Evaluation
+
+on:
+  pull_request:
+    types: [labeled]
+  workflow_dispatch:
+    inputs:
+      reason:
+        description: "Reason for manual trigger"
+        required: true
+        default: ""
+
+env:
+  N_PROCESSES: 32 # Global configuration for number of parallel processes for evaluation
+
+jobs:
+  run-evaluation:
+    if: github.event.label.name == 'eval-this' || github.event_name != 'pull_request'
+    runs-on: ubuntu-latest
+    permissions:
+      contents: "read"
+      id-token: "write"
+      pull-requests: "write"
+      issues: "write"
+    strategy:
+      matrix:
+        python-version: ["3.12"]
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Install tmux
+        run: sudo apt-get update && sudo apt-get install -y tmux
+      - name: Install poetry via pipx
+        run: pipx install poetry
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: "poetry"
+
+      - name: Comment on PR if 'eval-this' label is present
+        if: github.event_name == 'pull_request' && github.event.label.name == 'eval-this'
+        uses: KeisukeYamashita/create-comment@v1
+        with:
+          unique: false
+          comment: |
+            Hi! I started running the evaluation on your PR. You will receive a comment with the results shortly.
+
+      - name: Install Python dependencies using Poetry
+        run: poetry install
+
+      - name: Configure config.toml for evaluation
+        env:
+          DEEPSEEK_API_KEY: ${{ secrets.DEEPSEEK_LLM_API_KEY }}
+        run: |
+          echo "[llm.eval]" > config.toml
+          echo "model = \"deepseek/deepseek-chat\"" >> config.toml
+          echo "api_key = \"$DEEPSEEK_API_KEY\"" >> config.toml
+          echo "temperature = 0.0" >> config.toml
+
+      - name: Run SWE-Bench evaluation
+        env:
+          ALLHANDS_API_KEY: ${{ secrets.ALLHANDS_EVAL_RUNTIME_API_KEY }}
+          RUNTIME: remote
+          SANDBOX_REMOTE_RUNTIME_API_URL: https://runtime.eval.all-hands.dev
+          EVAL_DOCKER_IMAGE_PREFIX: us-central1-docker.pkg.dev/evaluation-092424/swe-bench-images
+
+        run: |
+          poetry run ./evaluation/benchmarks/swe_bench/scripts/run_infer.sh llm.eval HEAD CodeActAgent 300 30 $N_PROCESSES "princeton-nlp/SWE-bench_Lite" test
+          OUTPUT_FOLDER=$(find evaluation/evaluation_outputs/outputs/princeton-nlp__SWE-bench_Lite-test/CodeActAgent -name "deepseek-chat_maxiter_50_N_*-no-hint-run_1" -type d | head -n 1)
+          echo "OUTPUT_FOLDER for SWE-bench evaluation: $OUTPUT_FOLDER"
+          poetry run ./evaluation/benchmarks/swe_bench/scripts/eval_infer_remote.sh $OUTPUT_FOLDER/output.jsonl $N_PROCESSES "princeton-nlp/SWE-bench_Lite" test
+
+          poetry run ./evaluation/benchmarks/swe_bench/scripts/eval/summarize_outputs.py $OUTPUT_FOLDER/output.jsonl > summarize_outputs.log 2>&1
+          echo "SWEBENCH_REPORT<<EOF" >> $GITHUB_ENV
+          cat summarize_outputs.log >> $GITHUB_ENV
+          echo "EOF" >> $GITHUB_ENV
+
+      - name: Create tar.gz of evaluation outputs
+        run: |
+          TIMESTAMP=$(date +'%y-%m-%d-%H-%M')
+          tar -czvf evaluation_outputs_${TIMESTAMP}.tar.gz evaluation/evaluation_outputs/outputs
+
+      - name: Upload evaluation results as artifact
+        uses: actions/upload-artifact@v4
+        id: upload_results_artifact
+        with:
+          name: evaluation-outputs
+          path: evaluation_outputs_*.tar.gz
+
+      - name: Get artifact URL
+        run: echo "ARTIFACT_URL=${{ steps.upload_results_artifact.outputs.artifact-url }}" >> $GITHUB_ENV
+
+      - name: Authenticate to Google Cloud
+        uses: 'google-github-actions/auth@v2'
+        with:
+          credentials_json: ${{ secrets.GCP_RESEARCH_OBJECT_CREATOR_SA_KEY }}
+
+      - name: Set timestamp and trigger reason
+        run: |
+          echo "TIMESTAMP=$(date +'%Y-%m-%d-%H-%M')" >> $GITHUB_ENV
+          if [[ "${{ github.event_name }}" == "pull_request" ]]; then
+            echo "TRIGGER_REASON=pr-${{ github.event.pull_request.number }}" >> $GITHUB_ENV
+          elif [[ "${{ github.event_name }}" == "schedule" ]]; then
+            echo "TRIGGER_REASON=schedule" >> $GITHUB_ENV
+          else
+            echo "TRIGGER_REASON=manual-${{ github.event.inputs.reason }}" >> $GITHUB_ENV
+          fi
+
+      - name: Upload evaluation results to Google Cloud Storage
+        uses: 'google-github-actions/upload-cloud-storage@v2'
+        with:
+          path: 'evaluation/evaluation_outputs/outputs'
+          destination: 'openhands-oss-eval-results/${{ env.TIMESTAMP }}-${{ env.TRIGGER_REASON }}'
+
+      - name: Comment with evaluation results and artifact link
+        id: create_comment
+        uses: KeisukeYamashita/create-comment@v1
+        with:
+          number: ${{ github.event_name == 'pull_request' && github.event.pull_request.number || 4504 }}
+          unique: false
+          comment: |
+              Trigger by: ${{ github.event_name == 'pull_request' && format('Pull Request (eval-this label on PR #{0})', github.event.pull_request.number) || github.event_name == 'schedule' && 'Daily Schedule' || format('Manual Trigger: {0}', github.event.inputs.reason) }}
+              Commit: ${{ github.sha }}
+              **SWE-Bench Evaluation Report**
+              ${{ env.SWEBENCH_REPORT }}
+              ---
+              You can download the full evaluation outputs [here](${{ env.ARTIFACT_URL }}).
+
+      - name: Post to a Slack channel
+        id: slack
+        uses: slackapi/slack-github-action@v2.0.0
+        with:
+          channel-id: 'C07SVQSCR6F'
+          slack-message: "*Evaluation Trigger:* ${{ github.event_name == 'pull_request' && format('Pull Request (eval-this label on PR #{0})', github.event.pull_request.number) || github.event_name == 'schedule' && 'Daily Schedule' || format('Manual Trigger: {0}', github.event.inputs.reason) }}\n\nLink to summary: [here](https://github.com/${{ github.repository }}/issues/${{ github.event_name == 'pull_request' && github.event.pull_request.number || 4504 }}#issuecomment-${{ steps.create_comment.outputs.comment-id }})"
+        env:
+          SLACK_BOT_TOKEN: ${{ secrets.EVAL_NOTIF_SLACK_BOT_TOKEN }}

.github/workflows/fe-unit-tests.yml

@@ -21,7 +21,7 @@ jobs:
   # Run frontend unit tests
   fe-test:
     name: FE Unit Tests
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     strategy:
       matrix:
         node-version: [20, 22]
@@ -30,7 +30,7 @@ jobs:
       - name: Checkout
         uses: actions/checkout@v4
       - name: Set up Node.js
-        uses: useblacksmith/setup-node@v5
+        uses: actions/setup-node@v4
         with:
           node-version: ${{ matrix.node-version }}
       - name: Install dependencies

.github/workflows/ghcr-build.yml

@@ -32,7 +32,7 @@ jobs:
   # Builds the OpenHands Docker images
   ghcr_build_app:
     name: Build App Image
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     permissions:
       contents: read
       packages: write
@@ -41,10 +41,22 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/checkout@v4
+      - name: Free Disk Space (Ubuntu)
+        uses: jlumbroso/free-disk-space@main
         with:
-          ref: ${{ github.event.pull_request.head.sha }}
+          # this might remove tools that are actually needed,
+          # if set to "true" but frees about 6 GB
+          tool-cache: true
+          # all of these default to true, but feel free to set to
+          # "false" if necessary for your workflow
+          android: true
+          dotnet: true
+          haskell: true
+          large-packages: true
+          docker-images: false
+          swap-storage: true
       - name: Set up QEMU
-        uses: docker/setup-qemu-action@v3.6.0
+        uses: docker/setup-qemu-action@v3.2.0
         with:
           image: tonistiigi/binfmt:latest
       - name: Login to GHCR
@@ -56,22 +68,22 @@ jobs:
       - name: Set up Docker Buildx
         id: buildx
         uses: docker/setup-buildx-action@v3
-      - name: Lowercase Repository Owner
-        run: |
-          echo REPO_OWNER=$(echo ${{ github.repository_owner }} | tr '[:upper:]' '[:lower:]') >> $GITHUB_ENV
       - name: Build and push app image
         if: "!github.event.pull_request.head.repo.fork"
         run: |
-          ./containers/build.sh -i openhands -o ${{ env.REPO_OWNER }} --push
+          ./containers/build.sh -i openhands -o ${{ github.repository_owner }} --push
       - name: Build app image
         if: "github.event.pull_request.head.repo.fork"
         run: |
-          ./containers/build.sh -i openhands -o ${{ env.REPO_OWNER }} --load
+          ./containers/build.sh -i openhands -o ${{ github.repository_owner }} --load
       - name: Get hash in App Image
         id: get_hash_in_app_image
         run: |
+          # Lowercase the repository owner
+          export REPO_OWNER=${{ github.repository_owner }}
+          REPO_OWNER=$(echo $REPO_OWNER | tr '[:upper:]' '[:lower:]')
           # Run the build script in the app image
-          docker run -e SANDBOX_USER_ID=0 -v /var/run/docker.sock:/var/run/docker.sock ghcr.io/${{ env.REPO_OWNER }}/openhands:${{ env.RELEVANT_SHA }} /bin/bash -c "mkdir -p containers/runtime; python3 openhands/runtime/utils/runtime_build.py --base_image ${{ env.BASE_IMAGE_FOR_HASH_EQUIVALENCE_TEST }} --build_folder containers/runtime --force_rebuild" 2>&1 | tee docker-outputs.txt
+          docker run -e SANDBOX_USER_ID=0 -v /var/run/docker.sock:/var/run/docker.sock ghcr.io/${REPO_OWNER}/openhands:${{ env.RELEVANT_SHA }} /bin/bash -c "mkdir -p containers/runtime; python3 openhands/runtime/utils/runtime_build.py --base_image ${{ env.BASE_IMAGE_FOR_HASH_EQUIVALENCE_TEST }} --build_folder containers/runtime --force_rebuild" 2>&1 | tee docker-outputs.txt
           # Get the hash from the build script
           hash_from_app_image=$(cat docker-outputs.txt | grep "Hash for docker build directory" | awk -F "): " '{print $2}' | uniq | head -n1)
           echo "hash_from_app_image=$hash_from_app_image" >> $GITHUB_OUTPUT
@@ -80,7 +92,7 @@ jobs:
   # Builds the runtime Docker images
   ghcr_build_runtime:
     name: Build Image
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     permissions:
       contents: read
       packages: write
@@ -92,10 +104,22 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/checkout@v4
+      - name: Free Disk Space (Ubuntu)
+        uses: jlumbroso/free-disk-space@main
         with:
-          ref: ${{ github.event.pull_request.head.sha }}
+          # this might remove tools that are actually needed,
+          # if set to "true" but frees about 6 GB
+          tool-cache: true
+          # all of these default to true, but feel free to set to
+          # "false" if necessary for your workflow
+          android: true
+          dotnet: true
+          haskell: true
+          large-packages: true
+          docker-images: false
+          swap-storage: true
       - name: Set up QEMU
-        uses: docker/setup-qemu-action@v3.6.0
+        uses: docker/setup-qemu-action@v3.2.0
         with:
           image: tonistiigi/binfmt:latest
       - name: Login to GHCR
@@ -108,11 +132,11 @@ jobs:
         id: buildx
         uses: docker/setup-buildx-action@v3
       - name: Set up Python
-        uses: useblacksmith/setup-python@v6
+        uses: actions/setup-python@v5
         with:
           python-version: '3.12'
       - name: Cache Poetry dependencies
-        uses: useblacksmith/cache@v5
+        uses: actions/cache@v4
         with:
           path: |
             ~/.cache/pypoetry
@@ -126,19 +150,16 @@ jobs:
         run: make install-python-dependencies
       - name: Create source distribution and Dockerfile
         run: poetry run python3 openhands/runtime/utils/runtime_build.py --base_image ${{ matrix.base_image.image }} --build_folder containers/runtime --force_rebuild
-      - name: Lowercase Repository Owner
-        run: |
-          echo REPO_OWNER=$(echo ${{ github.repository_owner }} | tr '[:upper:]' '[:lower:]') >> $GITHUB_ENV
       - name: Build and push runtime image ${{ matrix.base_image.image }}
         if: github.event.pull_request.head.repo.fork != true
         run: |
-          ./containers/build.sh -i runtime -o ${{ env.REPO_OWNER }} --push -t ${{ matrix.base_image.tag }}
+          ./containers/build.sh -i runtime -o ${{ github.repository_owner }} --push -t ${{ matrix.base_image.tag }}
       # Forked repos can't push to GHCR, so we need to upload the image as an artifact
       - name: Build runtime image ${{ matrix.base_image.image }} for fork
         if: github.event.pull_request.head.repo.fork
         uses: docker/build-push-action@v6
         with:
-          tags: ghcr.io/${{ env.REPO_OWNER }}/runtime:${{ env.RELEVANT_SHA }}-${{ matrix.base_image.tag }}
+          tags: ghcr.io/all-hands-ai/runtime:${{ env.RELEVANT_SHA }}-${{ matrix.base_image.tag }}
           outputs: type=docker,dest=/tmp/runtime-${{ matrix.base_image.tag }}.tar
           context: containers/runtime
       - name: Upload runtime image for fork
@@ -150,7 +171,7 @@ jobs:
 
   verify_hash_equivalence_in_runtime_and_app:
     name: Verify Hash Equivalence in Runtime and Docker images
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     needs: [ghcr_build_runtime, ghcr_build_app]
     strategy:
       fail-fast: false
@@ -158,10 +179,8 @@ jobs:
         base_image: ['nikolaik']
     steps:
       - uses: actions/checkout@v4
-        with:
-          ref: ${{ github.event.pull_request.head.sha }}
       - name: Cache Poetry dependencies
-        uses: useblacksmith/cache@v5
+        uses: actions/cache@v4
         with:
           path: |
             ~/.cache/pypoetry
@@ -170,7 +189,7 @@ jobs:
           restore-keys: |
             ${{ runner.os }}-poetry-
       - name: Set up Python
-        uses: useblacksmith/setup-python@v6
+        uses: actions/setup-python@v5
         with:
           python-version: '3.12'
       - name: Install poetry via pipx
@@ -200,17 +219,31 @@ jobs:
             exit 1
           fi
 
-  # Run unit tests with the Docker runtime Docker images as root
+  # Run unit tests with the EventStream runtime Docker images as root
   test_runtime_root:
     name: RT Unit Tests (Root)
     needs: [ghcr_build_runtime]
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     strategy:
       fail-fast: false
       matrix:
         base_image: ['nikolaik']
     steps:
       - uses: actions/checkout@v4
+      - name: Free Disk Space (Ubuntu)
+        uses: jlumbroso/free-disk-space@main
+        with:
+          # this might remove tools that are actually needed,
+          # if set to "true" but frees about 6 GB
+          tool-cache: true
+          # all of these default to true, but feel free to set to
+          # "false" if necessary for your workflow
+          android: true
+          dotnet: true
+          haskell: true
+          large-packages: true
+          docker-images: false
+          swap-storage: true
       - name: Set up Docker Buildx
         id: buildx
         uses: docker/setup-buildx-action@v3
@@ -226,7 +259,7 @@ jobs:
         run: |
           docker load --input /tmp/runtime-${{ matrix.base_image }}.tar
       - name: Cache Poetry dependencies
-        uses: useblacksmith/cache@v5
+        uses: actions/cache@v4
         with:
           path: |
             ~/.cache/pypoetry
@@ -235,17 +268,14 @@ jobs:
           restore-keys: |
             ${{ runner.os }}-poetry-
       - name: Set up Python
-        uses: useblacksmith/setup-python@v6
+        uses: actions/setup-python@v5
         with:
           python-version: '3.12'
       - name: Install poetry via pipx
         run: pipx install poetry
       - name: Install Python dependencies using Poetry
         run: make install-python-dependencies
-      - name: Lowercase Repository Owner
-        run: |
-          echo REPO_OWNER=$(echo ${{ github.repository_owner }} | tr '[:upper:]' '[:lower:]') >> $GITHUB_ENV
-      - name: Run docker runtime tests
+      - name: Run runtime tests
         run: |
           # We install pytest-xdist in order to run tests across CPUs
           poetry run pip install pytest-xdist
@@ -253,9 +283,10 @@ jobs:
           # Install to be able to retry on failures for flaky tests
           poetry run pip install pytest-rerunfailures
 
-          image_name=ghcr.io/${{ env.REPO_OWNER }}/runtime:${{ env.RELEVANT_SHA }}-${{ matrix.base_image }}
+          image_name=ghcr.io/${{ github.repository_owner }}/runtime:${{ env.RELEVANT_SHA }}-${{ matrix.base_image }}
+          image_name=$(echo $image_name | tr '[:upper:]' '[:lower:]')
 
-          TEST_RUNTIME=docker \
+          TEST_RUNTIME=eventstream \
           SANDBOX_USER_ID=$(id -u) \
           SANDBOX_RUNTIME_CONTAINER_IMAGE=$image_name \
           TEST_IN_CI=true \
@@ -266,16 +297,30 @@ jobs:
         env:
           CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
 
-  # Run unit tests with the Docker runtime Docker images as openhands user
+  # Run unit tests with the EventStream runtime Docker images as openhands user
   test_runtime_oh:
     name: RT Unit Tests (openhands)
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     needs: [ghcr_build_runtime]
     strategy:
       matrix:
         base_image: ['nikolaik']
     steps:
       - uses: actions/checkout@v4
+      - name: Free Disk Space (Ubuntu)
+        uses: jlumbroso/free-disk-space@main
+        with:
+          # this might remove tools that are actually needed,
+          # if set to "true" but frees about 6 GB
+          tool-cache: true
+          # all of these default to true, but feel free to set to
+          # "false" if necessary for your workflow
+          android: true
+          dotnet: true
+          haskell: true
+          large-packages: true
+          docker-images: false
+          swap-storage: true
       - name: Set up Docker Buildx
         id: buildx
         uses: docker/setup-buildx-action@v3
@@ -291,7 +336,7 @@ jobs:
         run: |
           docker load --input /tmp/runtime-${{ matrix.base_image }}.tar
       - name: Cache Poetry dependencies
-        uses: useblacksmith/cache@v5
+        uses: actions/cache@v4
         with:
           path: |
             ~/.cache/pypoetry
@@ -300,16 +345,13 @@ jobs:
           restore-keys: |
             ${{ runner.os }}-poetry-
       - name: Set up Python
-        uses: useblacksmith/setup-python@v6
+        uses: actions/setup-python@v5
         with:
           python-version: '3.12'
       - name: Install poetry via pipx
         run: pipx install poetry
       - name: Install Python dependencies using Poetry
         run: make install-python-dependencies
-      - name: Lowercase Repository Owner
-        run: |
-          echo REPO_OWNER=$(echo ${{ github.repository_owner }} | tr '[:upper:]' '[:lower:]') >> $GITHUB_ENV
       - name: Run runtime tests
         run: |
           # We install pytest-xdist in order to run tests across CPUs
@@ -318,9 +360,10 @@ jobs:
           # Install to be able to retry on failures for flaky tests
           poetry run pip install pytest-rerunfailures
 
-          image_name=ghcr.io/${{ env.REPO_OWNER }}/runtime:${{ env.RELEVANT_SHA }}-${{ matrix.base_image }}
+          image_name=ghcr.io/${{ github.repository_owner }}/runtime:${{ env.RELEVANT_SHA }}-${{ matrix.base_image }}
+          image_name=$(echo $image_name | tr '[:upper:]' '[:lower:]')
 
-          TEST_RUNTIME=docker \
+          TEST_RUNTIME=eventstream \
           SANDBOX_USER_ID=$(id -u) \
           SANDBOX_RUNTIME_CONTAINER_IMAGE=$image_name \
           TEST_IN_CI=true \
@@ -338,7 +381,7 @@ jobs:
   runtime_tests_check_success:
     name: All Runtime Tests Passed
     if: ${{ !cancelled() && !contains(needs.*.result, 'failure') && !contains(needs.*.result, 'cancelled') }}
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     needs: [test_runtime_root, test_runtime_oh, verify_hash_equivalence_in_runtime_and_app]
     steps:
       - name: All tests passed
@@ -347,7 +390,7 @@ jobs:
   runtime_tests_check_fail:
     name: All Runtime Tests Passed
     if: ${{ cancelled() || contains(needs.*.result, 'failure') || contains(needs.*.result, 'cancelled') }}
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     needs: [test_runtime_root, test_runtime_oh, verify_hash_equivalence_in_runtime_and_app]
     steps:
       - name: Some tests failed
@@ -358,7 +401,7 @@ jobs:
     name: Update PR Description
     if: github.event_name == 'pull_request' && !github.event.pull_request.head.repo.fork && github.actor != 'dependabot[bot]'
     needs: [ghcr_build_runtime]
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     steps:
       - name: Checkout
         uses: actions/checkout@v4

.github/workflows/integration-runner.yml

@@ -18,7 +18,7 @@ env:
 jobs:
   run-integration-tests:
     if: github.event.label.name == 'integration-test' || github.event_name == 'workflow_dispatch' || github.event_name == 'schedule'
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     permissions:
       contents: "read"
       id-token: "write"
@@ -35,16 +35,11 @@ jobs:
         run: pipx install poetry
 
       - name: Set up Python
-        uses: useblacksmith/setup-python@v6
+        uses: actions/setup-python@v5
         with:
           python-version: ${{ matrix.python-version }}
           cache: "poetry"
 
-      - name: Setup Node.js
-        uses: useblacksmith/setup-node@v5
-        with:
-          node-version: '22.x'
-
       - name: Comment on PR if 'integration-test' label is present
         if: github.event_name == 'pull_request' && github.event.label.name == 'integration-test'
         uses: KeisukeYamashita/create-comment@v1
@@ -54,14 +49,13 @@ jobs:
             Hi! I started running the integration tests on your PR. You will receive a comment with the results shortly.
 
       - name: Install Python dependencies using Poetry
-        run: poetry install --without evaluation
+        run: poetry install --without evaluation,llama-index
 
       - name: Configure config.toml for testing with Haiku
         env:
           LLM_MODEL: "litellm_proxy/claude-3-5-haiku-20241022"
           LLM_API_KEY: ${{ secrets.LLM_API_KEY }}
           LLM_BASE_URL: ${{ secrets.LLM_BASE_URL }}
-          MAX_ITERATIONS: 10
         run: |
           echo "[llm.eval]" > config.toml
           echo "model = \"$LLM_MODEL\"" >> config.toml
@@ -76,7 +70,7 @@ jobs:
         env:
           SANDBOX_FORCE_REBUILD_RUNTIME: True
         run: |
-          poetry run ./evaluation/integration_tests/scripts/run_infer.sh llm.eval HEAD CodeActAgent '' 10 $N_PROCESSES '' 'haiku_run'
+          poetry run ./evaluation/integration_tests/scripts/run_infer.sh llm.eval HEAD CodeActAgent '' $N_PROCESSES '' 'haiku_run'
 
           # get integration tests report
           REPORT_FILE_HAIKU=$(find evaluation/evaluation_outputs/outputs/integration_tests/CodeActAgent/*haiku*_maxiter_10_N* -name "report.md" -type f | head -n 1)
@@ -94,7 +88,6 @@ jobs:
           LLM_MODEL: "litellm_proxy/deepseek-chat"
           LLM_API_KEY: ${{ secrets.LLM_API_KEY }}
           LLM_BASE_URL: ${{ secrets.LLM_BASE_URL }}
-          MAX_ITERATIONS: 10
         run: |
           echo "[llm.eval]" > config.toml
           echo "model = \"$LLM_MODEL\"" >> config.toml
@@ -106,7 +99,7 @@ jobs:
         env:
           SANDBOX_FORCE_REBUILD_RUNTIME: True
         run: |
-          poetry run ./evaluation/integration_tests/scripts/run_infer.sh llm.eval HEAD CodeActAgent '' 10 $N_PROCESSES '' 'deepseek_run'
+          poetry run ./evaluation/integration_tests/scripts/run_infer.sh llm.eval HEAD CodeActAgent '' $N_PROCESSES '' 'deepseek_run'
 
           # get integration tests report
           REPORT_FILE_DEEPSEEK=$(find evaluation/evaluation_outputs/outputs/integration_tests/CodeActAgent/deepseek*_maxiter_10_N* -name "report.md" -type f | head -n 1)
@@ -116,42 +109,11 @@ jobs:
           echo >> $GITHUB_ENV
           echo "EOF" >> $GITHUB_ENV
 
-      # -------------------------------------------------------------
-      # Run VisualBrowsingAgent tests for DeepSeek, limited to t05 and t06
-      - name: Wait a little bit (again)
-        run: sleep 5
-
-      - name: Configure config.toml for testing VisualBrowsingAgent (DeepSeek)
-        env:
-          LLM_MODEL: "litellm_proxy/deepseek-chat"
-          LLM_API_KEY: ${{ secrets.LLM_API_KEY }}
-          LLM_BASE_URL: ${{ secrets.LLM_BASE_URL }}
-          MAX_ITERATIONS: 15
-        run: |
-          echo "[llm.eval]" > config.toml
-          echo "model = \"$LLM_MODEL\"" >> config.toml
-          echo "api_key = \"$LLM_API_KEY\"" >> config.toml
-          echo "base_url = \"$LLM_BASE_URL\"" >> config.toml
-          echo "temperature = 0.0" >> config.toml
-      - name: Run integration test evaluation for VisualBrowsingAgent (DeepSeek)
-        env:
-          SANDBOX_FORCE_REBUILD_RUNTIME: True
-        run: |
-          poetry run ./evaluation/integration_tests/scripts/run_infer.sh llm.eval HEAD VisualBrowsingAgent '' 15 $N_PROCESSES "t05_simple_browsing,t06_github_pr_browsing.py" 'visualbrowsing_deepseek_run'
-
-          # Find and export the visual browsing agent test results
-          REPORT_FILE_VISUALBROWSING_DEEPSEEK=$(find evaluation/evaluation_outputs/outputs/integration_tests/VisualBrowsingAgent/deepseek*_maxiter_15_N* -name "report.md" -type f | head -n 1)
-          echo "REPORT_FILE_VISUALBROWSING_DEEPSEEK: $REPORT_FILE_VISUALBROWSING_DEEPSEEK"
-          echo "INTEGRATION_TEST_REPORT_VISUALBROWSING_DEEPSEEK<<EOF" >> $GITHUB_ENV
-          cat $REPORT_FILE_VISUALBROWSING_DEEPSEEK >> $GITHUB_ENV
-          echo >> $GITHUB_ENV
-          echo "EOF" >> $GITHUB_ENV
-
       - name: Create archive of evaluation outputs
         run: |
           TIMESTAMP=$(date +'%y-%m-%d-%H-%M')
           cd evaluation/evaluation_outputs/outputs  # Change to the outputs directory
-          tar -czvf ../../../integration_tests_${TIMESTAMP}.tar.gz integration_tests/CodeActAgent/* integration_tests/VisualBrowsingAgent/* # Only include the actual result directories
+          tar -czvf ../../../integration_tests_${TIMESTAMP}.tar.gz integration_tests/CodeActAgent/*  # Only include the actual result directories
 
       - name: Upload evaluation results as artifact
         uses: actions/upload-artifact@v4
@@ -193,7 +155,4 @@ jobs:
               DeepSeek LLM Test Results:
               ${{ env.INTEGRATION_TEST_REPORT_DEEPSEEK }}
               ---
-              **Integration Tests Report VisualBrowsing (DeepSeek)**
-              ${{ env.INTEGRATION_TEST_REPORT_VISUALBROWSING_DEEPSEEK }}
-              ---
               Download testing outputs (includes both Haiku and DeepSeek results): [Download](${{ steps.upload_results_artifact.outputs.artifact-url }})

.github/workflows/lint-fix.yml

@@ -9,7 +9,7 @@ jobs:
   lint-fix-frontend:
     if: github.event.label.name == 'lint-fix'
     name: Fix frontend linting issues
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     permissions:
       contents: write
       pull-requests: write
@@ -22,7 +22,7 @@ jobs:
           token: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Install Node.js 20
-        uses: useblacksmith/setup-node@v5
+        uses: actions/setup-node@v4
         with:
           node-version: 20
       - name: Install frontend dependencies
@@ -52,7 +52,7 @@ jobs:
   lint-fix-python:
     if: github.event.label.name == 'lint-fix'
     name: Fix Python linting issues
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     permissions:
       contents: write
       pull-requests: write
@@ -65,7 +65,7 @@ jobs:
           token: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Set up python
-        uses: useblacksmith/setup-python@v6
+        uses: actions/setup-python@v5
         with:
           python-version: 3.12
           cache: 'pip'

.github/workflows/lint.yml

@@ -19,11 +19,11 @@ jobs:
   # Run lint on the frontend code
   lint-frontend:
     name: Lint frontend
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
       - name: Install Node.js 20
-        uses: useblacksmith/setup-node@v5
+        uses: actions/setup-node@v4
         with:
           node-version: 20
       - name: Install dependencies
@@ -39,13 +39,13 @@ jobs:
   # Run lint on the python code
   lint-python:
     name: Lint python
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
         with:
           fetch-depth: 0
       - name: Set up python
-        uses: useblacksmith/setup-python@v6
+        uses: actions/setup-python@v5
         with:
           python-version: 3.12
           cache: 'pip'
@@ -57,11 +57,11 @@ jobs:
   # Check version consistency across documentation
   check-version-consistency:
     name: Check version consistency
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
       - name: Set up python
-        uses: useblacksmith/setup-python@v6
+        uses: actions/setup-python@v5
         with:
           python-version: 3.12
       - name: Run version consistency check

.github/workflows/openhands-resolver.yml

@@ -20,10 +20,6 @@ on:
         required: false
         type: string
         default: "anthropic/claude-3-5-sonnet-20241022"
-      LLM_API_VERSION:
-        required: false
-        type: string
-        default: ""
       base_container_image:
         required: false
         type: string
@@ -88,10 +84,8 @@ jobs:
         run: |
           python -m pip index versions openhands-ai > openhands_versions.txt
           OPENHANDS_VERSION=$(head -n 1 openhands_versions.txt | awk '{print $2}' | tr -d '()')
-
-          # Create a new requirements.txt locally within the workflow, ensuring no reference to the repo's file
-          echo "openhands-ai==${OPENHANDS_VERSION}" > /tmp/requirements.txt
-          cat /tmp/requirements.txt
+          echo "openhands-ai==${OPENHANDS_VERSION}" >> requirements.txt
+          cat requirements.txt
 
       - name: Cache pip dependencies
         if: |
@@ -109,16 +103,15 @@ jobs:
         uses: actions/cache@v4
         with:
           path: ${{ env.pythonLocation }}/lib/python3.12/site-packages/*
-          key: ${{ runner.os }}-pip-openhands-resolver-${{ hashFiles('/tmp/requirements.txt') }}
+          key: ${{ runner.os }}-pip-openhands-resolver-${{ hashFiles('requirements.txt') }}
           restore-keys: |
-            ${{ runner.os }}-pip-openhands-resolver-${{ hashFiles('/tmp/requirements.txt') }}
+            ${{ runner.os }}-pip-openhands-resolver-${{ hashFiles('requirements.txt') }}
 
       - name: Check required environment variables
         env:
           LLM_MODEL: ${{ secrets.LLM_MODEL || inputs.LLM_MODEL }}
           LLM_API_KEY: ${{ secrets.LLM_API_KEY }}
           LLM_BASE_URL: ${{ secrets.LLM_BASE_URL }}
-          LLM_API_VERSION: ${{ inputs.LLM_API_VERSION }}
           PAT_TOKEN: ${{ secrets.PAT_TOKEN }}
           PAT_USERNAME: ${{ secrets.PAT_USERNAME }}
           GITHUB_TOKEN: ${{ github.token }}
@@ -175,7 +168,7 @@ jobs:
           echo "SANDBOX_ENV_BASE_CONTAINER_IMAGE=${{ inputs.base_container_image }}" >> $GITHUB_ENV
 
           # Set branch variables
-          echo "TARGET_BRANCH=${{ inputs.target_branch || 'main' }}" >> $GITHUB_ENV
+          echo "TARGET_BRANCH=${{ inputs.target_branch }}" >> $GITHUB_ENV
 
       - name: Comment on issue with start message
         uses: actions/github-script@v7
@@ -191,7 +184,6 @@ jobs:
             });
 
       - name: Install OpenHands
-        id: install_openhands
         uses: actions/github-script@v7
         env:
           COMMENT_BODY: ${{ github.event.comment.body || '' }}
@@ -204,6 +196,7 @@ jobs:
             const reviewBody = process.env.REVIEW_BODY.trim();
             const labelName = process.env.LABEL_NAME.trim();
             const eventName = process.env.EVENT_NAME.trim();
+
             // Check conditions
             const isExperimentalLabel = labelName === "fix-me-experimental";
             const isIssueCommentExperimental =
@@ -212,9 +205,6 @@ jobs:
             const isReviewCommentExperimental =
               eventName === "pull_request_review" && reviewBody.includes("@openhands-agent-exp");
 
-            // Set output variable
-            core.setOutput('isExperimental', isExperimentalLabel || isIssueCommentExperimental || isReviewCommentExperimental);
-
             // Perform package installation
             if (isExperimentalLabel || isIssueCommentExperimental || isReviewCommentExperimental) {
               console.log("Installing experimental OpenHands...");
@@ -223,18 +213,16 @@ jobs:
             } else {
               console.log("Installing from requirements.txt...");
               await exec.exec("python -m pip install --upgrade pip");
-              await exec.exec("pip install -r /tmp/requirements.txt");
+              await exec.exec("pip install -r requirements.txt");
             }
 
       - name: Attempt to resolve issue
         env:
           GITHUB_TOKEN: ${{ secrets.PAT_TOKEN || github.token }}
           GITHUB_USERNAME: ${{ secrets.PAT_USERNAME || 'openhands-agent' }}
-          GIT_USERNAME: ${{ secrets.PAT_USERNAME || 'openhands-agent' }}
           LLM_MODEL: ${{ secrets.LLM_MODEL || inputs.LLM_MODEL }}
           LLM_API_KEY: ${{ secrets.LLM_API_KEY }}
           LLM_BASE_URL: ${{ secrets.LLM_BASE_URL }}
-          LLM_API_VERSION: ${{ inputs.LLM_API_VERSION }}
           PYTHONPATH: ""
         run: |
           cd /tmp && python -m openhands.resolver.resolve_issue \
@@ -242,8 +230,7 @@ jobs:
             --issue-number ${{ env.ISSUE_NUMBER }} \
             --issue-type ${{ env.ISSUE_TYPE }} \
             --max-iterations ${{ env.MAX_ITERATIONS }} \
-            --comment-id ${{ env.COMMENT_ID }} \
-            --is-experimental ${{ steps.install_openhands.outputs.isExperimental }}
+            --comment-id ${{ env.COMMENT_ID }}
 
       - name: Check resolution result
         id: check_result
@@ -267,17 +254,14 @@ jobs:
         env:
           GITHUB_TOKEN: ${{ secrets.PAT_TOKEN || github.token }}
           GITHUB_USERNAME: ${{ secrets.PAT_USERNAME || 'openhands-agent' }}
-          GIT_USERNAME: ${{ secrets.PAT_USERNAME || 'openhands-agent' }}
           LLM_MODEL: ${{ secrets.LLM_MODEL || inputs.LLM_MODEL }}
           LLM_API_KEY: ${{ secrets.LLM_API_KEY }}
           LLM_BASE_URL: ${{ secrets.LLM_BASE_URL }}
-          LLM_API_VERSION: ${{ inputs.LLM_API_VERSION }}
           PYTHONPATH: ""
         run: |
           if [ "${{ steps.check_result.outputs.RESOLUTION_SUCCESS }}" == "true" ]; then
             cd /tmp && python -m openhands.resolver.send_pull_request \
               --issue-number ${{ env.ISSUE_NUMBER }} \
-              --target-branch ${{ env.TARGET_BRANCH }} \
               --pr-type draft \
               --reviewer ${{ github.actor }} | tee pr_result.txt && \
               grep "draft created" pr_result.txt | sed 's/.*\///g' > pr_number.txt
@@ -295,12 +279,11 @@ jobs:
         if: always()
         env:
           AGENT_RESPONDED: ${{ env.AGENT_RESPONDED || 'false' }}
-          ISSUE_NUMBER: ${{ env.ISSUE_NUMBER }}
         with:
           github-token: ${{ secrets.PAT_TOKEN || github.token }}
           script: |
             const fs = require('fs');
-            const issueNumber = process.env.ISSUE_NUMBER;
+            const issueNumber = ${{ env.ISSUE_NUMBER }};
             let logContent = '';
 
             try {
@@ -331,15 +314,13 @@ jobs:
         if: always() # Comment on issue even if the previous steps fail
         env:
           AGENT_RESPONDED: ${{ env.AGENT_RESPONDED || 'false' }}
-          ISSUE_NUMBER: ${{ env.ISSUE_NUMBER }}
-          RESOLUTION_SUCCESS: ${{ steps.check_result.outputs.RESOLUTION_SUCCESS }}
         with:
           github-token: ${{ secrets.PAT_TOKEN || github.token }}
           script: |
             const fs = require('fs');
             const path = require('path');
-            const issueNumber = process.env.ISSUE_NUMBER;
-            const success = process.env.RESOLUTION_SUCCESS === 'true';
+            const issueNumber = ${{ env.ISSUE_NUMBER }};
+            const success = ${{ steps.check_result.outputs.RESOLUTION_SUCCESS }};
 
             let prNumber = '';
             let branchName = '';
@@ -404,12 +385,10 @@ jobs:
       - name: Fallback Error Comment
         uses: actions/github-script@v7
         if: ${{ env.AGENT_RESPONDED == 'false' }} # Only run if no conditions were met in previous steps
-        env:
-          ISSUE_NUMBER: ${{ env.ISSUE_NUMBER }}
         with:
           github-token: ${{ secrets.PAT_TOKEN || github.token }}
           script: |
-            const issueNumber = process.env.ISSUE_NUMBER;
+            const issueNumber = ${{ env.ISSUE_NUMBER }};
 
             github.rest.issues.createComment({
               issue_number: issueNumber,

.github/workflows/py-unit-tests-mac.yml

@@ -0,0 +1,98 @@
+# Workflow that runs python unit tests on mac
+name: Run Python Unit Tests Mac
+
+# This job is flaky so only run it nightly
+on:
+  schedule:
+    - cron: '0 0 * * *'
+
+jobs:
+  # Run python unit tests on macOS
+  test-on-macos:
+    name: Python Unit Tests on macOS
+    runs-on: macos-14
+    env:
+      INSTALL_DOCKER: '1' # Set to '0' to skip Docker installation
+    strategy:
+      matrix:
+        python-version: ['3.12']
+    steps:
+      - uses: actions/checkout@v4
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Cache Poetry dependencies
+        uses: actions/cache@v4
+        with:
+          path: |
+            ~/.cache/pypoetry
+            ~/.virtualenvs
+          key: ${{ runner.os }}-poetry-${{ hashFiles('**/poetry.lock') }}
+          restore-keys: |
+            ${{ runner.os }}-poetry-
+      - name: Install tmux
+        run: brew install tmux
+      - name: Install poetry via pipx
+        run: pipx install poetry
+      - name: Install Python dependencies using Poetry
+        run: poetry install --without evaluation,llama-index
+      - name: Install & Start Docker
+        if: env.INSTALL_DOCKER == '1'
+        run: |
+          INSTANCE_NAME="colima-${GITHUB_RUN_ID}"
+
+          # Uninstall colima to upgrade to the latest version
+          if brew list colima &>/dev/null; then
+            brew uninstall colima
+            # unlinking colima dependency: go
+            brew uninstall go@1.21
+          fi
+          rm -rf ~/.colima ~/.lima
+          brew install --HEAD colima
+          brew install docker
+
+          start_colima() {
+            # Find a free port in the range 10000-20000
+            RANDOM_PORT=$((RANDOM % 10001 + 10000))
+
+            # Original line:
+            if ! colima start --network-address --arch x86_64 --cpu=1 --memory=1 --verbose --ssh-port $RANDOM_PORT; then
+              echo "Failed to start Colima."
+              return 1
+            fi
+            return 0
+          }
+
+          # Attempt to start Colima for 5 total attempts:
+          ATTEMPT_LIMIT=5
+          for ((i=1; i<=ATTEMPT_LIMIT; i++)); do
+
+            if start_colima; then
+              echo "Colima started successfully."
+              break
+            else
+              colima stop -f
+              sleep 10
+              colima delete -f
+              if [ $i -eq $ATTEMPT_LIMIT ]; then
+                exit 1
+              fi
+              sleep 10
+            fi
+          done
+
+          # For testcontainers to find the Colima socket
+          # https://github.com/abiosoft/colima/blob/main/docs/FAQ.md#cannot-connect-to-the-docker-daemon-at-unixvarrundockersock-is-the-docker-daemon-running
+          sudo ln -sf $HOME/.colima/default/docker.sock /var/run/docker.sock
+      - name: Build Environment
+        run: make build
+      - name: Set up Docker Buildx
+        id: buildx
+        uses: docker/setup-buildx-action@v3
+      - name: Run Tests
+        run: poetry run pytest --forked --cov=openhands --cov-report=xml ./tests/unit --ignore=tests/unit/test_memory.py
+      - name: Upload coverage to Codecov
+        uses: codecov/codecov-action@v5
+        env:
+          CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

.github/workflows/py-unit-tests.yml

@@ -19,7 +19,7 @@ jobs:
   # Run python unit tests on Linux
   test-on-linux:
     name: Python Unit Tests on Linux
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     env:
       INSTALL_DOCKER: '0' # Set to '0' to skip Docker installation
     strategy:
@@ -32,23 +32,19 @@ jobs:
         uses: docker/setup-buildx-action@v3
       - name: Install tmux
         run: sudo apt-get update && sudo apt-get install -y tmux
-      - name: Setup Node.js
-        uses: useblacksmith/setup-node@v5
-        with:
-          node-version: '22.x'
       - name: Install poetry via pipx
         run: pipx install poetry
       - name: Set up Python
-        uses: useblacksmith/setup-python@v6
+        uses: actions/setup-python@v5
         with:
           python-version: ${{ matrix.python-version }}
           cache: 'poetry'
       - name: Install Python dependencies using Poetry
-        run: poetry install --without evaluation
+        run: poetry install --without evaluation,llama-index
       - name: Build Environment
         run: make build
       - name: Run Tests
-        run: poetry run pytest --forked -n auto --cov=openhands --cov-report=xml -svv ./tests/unit
+        run: poetry run pytest --forked -n auto --cov=openhands --cov-report=xml -svv ./tests/unit --ignore=tests/unit/test_memory.py
       - name: Upload coverage to Codecov
         uses: codecov/codecov-action@v5
         env:

.github/workflows/pypi-release.yml

@@ -12,10 +12,10 @@ on:
 
 jobs:
   release:
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: useblacksmith/setup-python@v6
+      - uses: actions/setup-python@v5
         with:
           python-version: 3.12
       - name: Install Poetry

.github/workflows/run-eval.yml

@@ -10,7 +10,7 @@ jobs:
   trigger-job:
     name: Trigger remote eval job
     if: ${{ github.event.label.name == 'run-eval-xs' || github.event.label.name == 'run-eval-s' || github.event.label.name == 'run-eval-m' }}
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
 
     steps:
       - name: Checkout PR branch

.github/workflows/stale.yml

@@ -8,7 +8,7 @@ on:
 
 jobs:
   stale:
-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ubuntu-latest
     steps:
       - uses: actions/stale@v9
         with:
@@ -19,4 +19,3 @@ jobs:
           close-issue-message: 'This issue was closed because it has been stalled for over 30 days with no activity.'
           close-pr-message: 'This PR was closed because it has been stalled for over 30 days with no activity.'
           days-before-close: 7
-          operations-per-run: 150

.openhands/microagents/glossary.md

@@ -1,172 +0,0 @@
-# OpenHands Glossary
-
-### Agent
-The core AI entity in OpenHands that can perform software development tasks by interacting with tools, browsing the web, and modifying code.
-
-#### Agent Controller
-A component that manages the agent's lifecycle, handles its state, and coordinates interactions between the agent and various tools.
-
-#### Agent Delegation
-The ability of an agent to hand off specific tasks to other specialized agents for better task completion.
-
-#### Agent Hub
-A central registry of different agent types and their capabilities, allowing for easy agent selection and instantiation.
-
-#### Agent Skill
-A specific capability or function that an agent can perform, such as file manipulation, web browsing, or code editing.
-
-#### Agent State
-The current context and status of an agent, including its memory, active tools, and ongoing tasks.
-
-#### CodeAct Agent
-[A generalist agent in OpenHands](https://arxiv.org/abs/2407.16741) designed to perform tasks by editing and executing code.
-
-### Browser
-A system for web-based interactions and tasks.
-
-#### Browser Gym
-A testing and evaluation environment for browser-based agent interactions and tasks.
-
-#### Web Browser Tool
-A tool that enables agents to interact with web pages and perform web-based tasks.
-
-### Commands
-Terminal and execution related functionality.
-
-#### Bash Session
-A persistent terminal session that maintains state and history for bash command execution.
-This uses tmux under the hood.
-
-### Configuration
-System-wide settings and options.
-
-#### Agent Configuration
-Settings that define an agent's behavior, capabilities, and limitations, including available tools and runtime settings.
-
-#### Configuration Options
-Settings that control various aspects of OpenHands behavior, including runtime, security, and agent settings.
-
-#### LLM Config
-Configuration settings for language models used by agents, including model selection and parameters.
-
-#### LLM Draft Config
-Settings for draft mode operations with language models, typically used for faster, lower-quality responses.
-
-#### Runtime Configuration
-Settings that define how the runtime environment should be set up and operated.
-
-#### Security Options
-Configuration settings that control security features and restrictions.
-
-### Conversation
-A sequence of interactions between a user and an agent, including messages, actions, and their results.
-
-#### Conversation Info
-Metadata about a conversation, including its status, participants, and timeline.
-
-#### Conversation Manager
-A component that handles the creation, storage, and retrieval of conversations.
-
-#### Conversation Metadata
-Additional information about conversations, such as tags, timestamps, and related resources.
-
-#### Conversation Status
-The current state of a conversation, including whether it's active, completed, or failed.
-
-#### Conversation Store
-A storage system for maintaining conversation history and related data.
-
-### Events
-
-#### Event
-Every Conversation comprises a series of Events. Each Event is either an Action or an Observation.
-
-#### Event Stream
-A continuous flow of events that represents the ongoing activities and interactions in the system.
-
-#### Action
-A specific operation or command that an agent executes through available tools, such as running a command or editing a file.
-
-#### Observation
-The response or result returned by a tool after an agent's action, providing feedback about the action's outcome.
-
-### Interface
-Different ways to interact with OpenHands.
-
-#### CLI Mode
-A command-line interface mode for interacting with OpenHands agents without a graphical interface.
-
-#### GUI Mode
-A graphical user interface mode for interacting with OpenHands agents through a web interface.
-
-#### Headless Mode
-A mode of operation where OpenHands runs without a user interface, suitable for automation and scripting.
-
-### Agent Memory
-The system that decides which parts of the Event Stream (i.e. the conversation history) should be passed into each LLM prompt.
-
-#### Memory Store
-A storage system for maintaining agent memory and context across sessions.
-
-#### Condenser
-A component that processes and summarizes conversation history to maintain context while staying within token limits.
-
-#### Truncation
-A very simple Condenser strategy. Reduces conversation history or content to stay within token limits.
-
-### Microagent
-A specialized prompt that enhances OpenHands with domain-specific knowledge, repository-specific context, and task-specific workflows.
-
-#### Microagent Registry
-A central repository of available microagents and their configurations.
-
-#### Public Microagent
-A general-purpose microagent available to all OpenHands users, triggered by specific keywords.
-
-#### Repository Microagent
-A type of microagent that provides repository-specific context and guidelines, stored in the `.openhands/microagents/` directory.
-
-### Prompt
-Components for managing and processing prompts.
-
-#### Prompt Caching
-A system for caching and reusing common prompts to improve performance.
-
-#### Prompt Manager
-A component that handles the loading, processing, and management of prompts used by agents, including microagents.
-
-#### Response Parsing
-The process of interpreting and structuring responses from language models and tools.
-
-### Runtime
-The execution environment where agents perform their tasks, which can be local, remote, or containerized.
-
-#### Action Execution Server
-A REST API that receives agent actions (e.g. bash commands, python code, browsing actions), executes them in the runtime environment, and returns the results.
-
-#### Action Execution Client
-A component that handles the execution of actions in the runtime environment, managing the communication between the agent and the runtime.
-
-#### Docker Runtime
-A containerized runtime environment that provides isolation and reproducibility for agent operations.
-
-#### E2B Runtime
-A specialized runtime environment built on E2B for secure and isolated code execution.
-
-#### Local Runtime
-A runtime environment that executes on the local machine, suitable for development and testing.
-
-#### Modal Runtime
-A runtime environment built on Modal for scalable and distributed agent operations.
-
-#### Remote Runtime
-A sandboxed environment that executes code and commands remotely, providing isolation and security for agent operations.
-
-#### Runtime Builder
-A component that builds a Docker image for the Action Execution Server based on a user-specified base image.
-
-### Security
-Security-related components and features.
-
-#### Security Analyzer
-A component that checks agent actions for potential security risks.

.openhands/microagents/repo.md

@@ -33,7 +33,6 @@ Frontend:
 - Testing:
   - Run tests: `npm run test`
   - To run specific tests: `npm run test -- -t "TestName"`
-  - Our test framework is vitest
 - Building:
   - Build for production: `npm run build`
 - Environment Variables:

.openhands/setup.sh

@@ -1,5 +0,0 @@
-#! /bin/bash
-
-echo "Setting up the environment..."
-
-python -m pip install pre-commit

CITATION.cff

@@ -1,55 +0,0 @@
-cff-version: 1.2.0
-message: "If you use this software, please cite it using the following metadata."
-title: "OpenHands: An Open Platform for AI Software Developers as Generalist Agents"
-authors:
-  - family-names: Wang
-    given-names: Xingyao
-  - family-names: Li
-    given-names: Boxuan
-  - family-names: Song
-    given-names: Yufan
-  - family-names: Xu
-    given-names: Frank F.
-  - family-names: Tang
-    given-names: Xiangru
-  - family-names: Zhuge
-    given-names: Mingchen
-  - family-names: Pan
-    given-names: Jiayi
-  - family-names: Song
-    given-names: Yueqi
-  - family-names: Li
-    given-names: Bowen
-  - family-names: Singh
-    given-names: Jaskirat
-  - family-names: Tran
-    given-names: Hoang H.
-  - family-names: Li
-    given-names: Fuqiang
-  - family-names: Ma
-    given-names: Ren
-  - family-names: Zheng
-    given-names: Mingzhang
-  - family-names: Qian
-    given-names: Bill
-  - family-names: Shao
-    given-names: Yanjun
-  - family-names: Muennighoff
-    given-names: Niklas
-  - family-names: Zhang
-    given-names: Yizhe
-  - family-names: Hui
-    given-names: Binyuan
-  - family-names: Lin
-    given-names: Junyang
-  - family-names: Brennan
-    given-names: Robert
-  - family-names: Peng
-    given-names: Hao
-  - family-names: Ji
-    given-names: Heng
-  - family-names: Neubig
-    given-names: Graham
-year: 2024
-doi: "10.48550/arXiv.2407.16741"
-url: "https://arxiv.org/abs/2407.16741"

CODE_OF_CONDUCT.md

@@ -113,20 +113,6 @@ individual, or aggression toward or disparagement of classes of individuals.
 **Consequence**: A permanent ban from any sort of public interaction within the
 community.
 
-### Slack and Discord Etiquettes
-
-These Slack and Discord etiquette guidelines are designed to foster an inclusive, respectful, and productive environment for all community members. By following these best practices, we ensure effective communication and collaboration while minimizing disruptions. Let’s work together to build a supportive and welcoming community!
-
-- Communicate respectfully and professionally, avoiding sarcasm or harsh language, and remember that tone can be difficult to interpret in text.
-- Use threads for specific discussions to keep channels organized and easier to follow.
-- Tag others only when their input is critical or urgent, and use @here, @channel or @everyone sparingly to minimize disruptions.
-- Be patient, as open-source contributors and maintainers often have other commitments and may need time to respond.
-- Post questions or discussions in the most relevant channel (e.g., for [slack - #general](https://app.slack.com/client/T06P212QSEA/C06P5NCGSFP) for general topics, [slack - #questions](https://openhands-ai.slack.com/archives/C06U8UTKSAD) for queries/questions, [discord - #general](https://discord.com/channels/1222935860639563850/1222935861386018885)).
-- When asking for help or raising issues, include necessary details like links, screenshots, or clear explanations to provide context.
-- Keep discussions in public channels whenever possible to allow others to benefit from the conversation, unless the matter is sensitive or private.
-- Always adhere to [our standards](https://github.com/All-Hands-AI/OpenHands/blob/main/CODE_OF_CONDUCT.md#our-standards) to ensure a welcoming and collaborative environment.
-- If you choose to mute a channel, consider setting up alerts for topics that still interest you to stay engaged. For Slack, Go to Settings → Notifications → My Keywords to add specific keywords that will notify you when mentioned. For example, if you're here for discussions about LLMs, mute the channel if it’s too busy, but set notifications to alert you only when “LLMs” appears in messages. Also for Discord, go to the channel notifications and choose the option that best describes your need.
-
 ## Attribution
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage],

Development.md

@@ -5,7 +5,7 @@ Otherwise, you can clone the OpenHands project directly.
 
 ## Start the Server for Development
 ### 1. Requirements
-* Linux, Mac OS, or [WSL on Windows](https://learn.microsoft.com/en-us/windows/wsl/install)  [Ubuntu >= 22.04]
+* Linux, Mac OS, or [WSL on Windows](https://learn.microsoft.com/en-us/windows/wsl/install)  [Ubuntu <= 22.04]
 * [Docker](https://docs.docker.com/engine/install/) (For those on MacOS, make sure to allow the default Docker socket to be used from advanced settings!)
 * [Python](https://www.python.org/downloads/) = 3.12
 * [NodeJS](https://nodejs.org/en/download/package-manager) >= 20.x
@@ -100,7 +100,7 @@ poetry run pytest ./tests/unit/test_*.py
 To reduce build time (e.g., if no changes were made to the client-runtime component), you can use an existing Docker container image by
 setting the SANDBOX_RUNTIME_CONTAINER_IMAGE environment variable to the desired Docker image.
 
-Example: `export SANDBOX_RUNTIME_CONTAINER_IMAGE=ghcr.io/all-hands-ai/runtime:0.29-nikolaik`
+Example: `export SANDBOX_RUNTIME_CONTAINER_IMAGE=ghcr.io/all-hands-ai/runtime:0.19-nikolaik`
 
 ## Develop inside Docker container
 
@@ -126,19 +126,3 @@ cd ./containers/dev
 ```
 
 You do need [Docker](https://docs.docker.com/engine/install/) installed on your host though.
-
-## Key Documentation Resources
-Here's a guide to the important documentation files in the repository:
-
-- `/README.md`: Main project overview, features, and basic setup instructions
-- `/Development.md` (this file): Comprehensive guide for developers working on OpenHands
-- `/CONTRIBUTING.md`: Guidelines for contributing to the project, including code style and PR process
-- `/docs/DOC_STYLE_GUIDE.md`: Standards for writing and maintaining project documentation
-- `/openhands/README.md`: Details about the backend Python implementation
-- `/frontend/README.md`: Frontend React application setup and development guide
-- `/containers/README.md`: Information about Docker containers and deployment
-- `/tests/unit/README.md`: Guide to writing and running unit tests
-- `/evaluation/README.md`: Documentation for the evaluation framework and benchmarks
-- `/microagents/README.md`: Information about the microagents architecture and implementation
-- `/openhands/server/README.md`: Server implementation details and API documentation
-- `/openhands/runtime/README.md`: Documentation for the runtime environment and execution model

ISSUE_TRIAGE.md

@@ -2,13 +2,12 @@
 These are the procedures and guidelines on how issues are triaged in this repo by the maintainers.
 
 ## General
-* All issues must be tagged with **enhancement**, **bug** or **troubleshooting/help**.
-* Issues may be tagged with what it relates to (**agent quality**, **frontend**, **resolver**, etc.).
+* Most issues must be tagged with **enhancement** or **bug**.
+* Issues may be tagged with what it relates to (**backend**, **frontend**, **agent quality**, etc.).
 
 ## Severity
 * **Low**: Minor issues or affecting single user.
 * **Medium**: Affecting multiple users.
-* **High**: High visibility issues or affecting many users.
 * **Critical**: Affecting all users or potential security issues.
 
 ## Effort
@@ -19,14 +18,8 @@ These are the procedures and guidelines on how issues are triaged in this repo b
 
 ## Not Enough Information
 * User is asked to provide more information (logs, how to reproduce, etc.) when the issue is not clear.
-* If an issue is unclear and the author does not provide more information or respond to a request,
-the issue may be closed as **not planned** (Usually after a week).
+* If an issue is unclear and the author does not provide more information or respond to a request, the issue may be closed as **not planned** (Usually after a week).
 
 ## Multiple Requests/Fixes in One Issue
 * These issues will be narrowed down to one request/fix so the issue is more easily tracked and fixed.
 * Issues may be broken down into multiple issues if required.
-
-## Stale and Auto Closures
-* In order to keep a maintainable backlog, issues that have no activity within 30 days are automatically marked as **Stale**.
-* If issues marked as **Stale** continue to have no activity for 7 more days, they will automatically be closed as not planned.
-* Issues may be reopened by maintainers if deemed important.

Makefile

@@ -1,4 +1,4 @@
-SHELL=/usr/bin/env bash
+SHELL=/bin/bash
 # Makefile for OpenHands project
 
 # Variables
@@ -81,10 +81,10 @@ check-nodejs:
 	@if command -v node > /dev/null; then \
 		NODE_VERSION=$(shell node --version | sed -E 's/v//g'); \
 		IFS='.' read -r -a NODE_VERSION_ARRAY <<< "$$NODE_VERSION"; \
-		if [ "$${NODE_VERSION_ARRAY[0]}" -ge 22 ]; then \
+		if [ "$${NODE_VERSION_ARRAY[0]}" -ge 20 ]; then \
 			echo "$(BLUE)Node.js $$NODE_VERSION is already installed.$(RESET)"; \
 		else \
-			echo "$(RED)Node.js 22.x or later is required. Please install Node.js 22.x or later to continue.$(RESET)"; \
+			echo "$(RED)Node.js 20.x or later is required. Please install Node.js 20.x or later to continue.$(RESET)"; \
 			exit 1; \
 		fi; \
 	else \
@@ -133,7 +133,7 @@ install-python-dependencies:
 		export HNSWLIB_NO_NATIVE=1; \
 		poetry run pip install chroma-hnswlib; \
 	fi
-	@poetry install
+	@poetry install --without llama-index
 	@if [ -f "/etc/manjaro-release" ]; then \
 		echo "$(BLUE)Detected Manjaro Linux. Installing Playwright dependencies...$(RESET)"; \
 		poetry run pip install playwright; \
@@ -265,6 +265,35 @@ setup-config-prompts:
 	@read -p "Enter your LLM base URL [mostly used for local LLMs, leave blank if not needed - example: http://localhost:5001/v1/]: " llm_base_url; \
 	 if [[ ! -z "$$llm_base_url" ]]; then echo "base_url=\"$$llm_base_url\"" >> $(CONFIG_FILE).tmp; fi
 
+	@echo "Enter your LLM Embedding Model"; \
+		echo "Choices are:"; \
+		echo "  - openai"; \
+		echo "  - azureopenai"; \
+		echo "  - Embeddings available only with OllamaEmbedding:"; \
+		echo "    - llama2"; \
+		echo "    - mxbai-embed-large"; \
+		echo "    - nomic-embed-text"; \
+		echo "    - all-minilm"; \
+		echo "    - stable-code"; \
+		echo "    - bge-m3"; \
+		echo "    - bge-large"; \
+		echo "    - paraphrase-multilingual"; \
+		echo "    - snowflake-arctic-embed"; \
+		echo "  - Leave blank to default to 'BAAI/bge-small-en-v1.5' via huggingface"; \
+		read -p "> " llm_embedding_model; \
+		echo "embedding_model=\"$$llm_embedding_model\"" >> $(CONFIG_FILE).tmp; \
+		if [ "$$llm_embedding_model" = "llama2" ] || [ "$$llm_embedding_model" = "mxbai-embed-large" ] || [ "$$llm_embedding_model" = "nomic-embed-text" ] || [ "$$llm_embedding_model" = "all-minilm" ] || [ "$$llm_embedding_model" = "stable-code" ]; then \
+			read -p "Enter the local model URL for the embedding model (will set llm.embedding_base_url): " llm_embedding_base_url; \
+				echo "embedding_base_url=\"$$llm_embedding_base_url\"" >> $(CONFIG_FILE).tmp; \
+		elif [ "$$llm_embedding_model" = "azureopenai" ]; then \
+			read -p "Enter the Azure endpoint URL (will overwrite llm.base_url): " llm_base_url; \
+				echo "base_url=\"$$llm_base_url\"" >> $(CONFIG_FILE).tmp; \
+			read -p "Enter the Azure LLM Embedding Deployment Name: " llm_embedding_deployment_name; \
+				echo "embedding_deployment_name=\"$$llm_embedding_deployment_name\"" >> $(CONFIG_FILE).tmp; \
+			read -p "Enter the Azure API Version: " llm_api_version; \
+				echo "api_version=\"$$llm_api_version\"" >> $(CONFIG_FILE).tmp; \
+		fi
+
 
 # Develop in container
 docker-dev:

README.md

@@ -12,7 +12,7 @@
   <a href="https://codecov.io/github/All-Hands-AI/OpenHands?branch=main"><img alt="CodeCov" src="https://img.shields.io/codecov/c/github/All-Hands-AI/OpenHands?style=for-the-badge&color=blue"></a>
   <a href="https://github.com/All-Hands-AI/OpenHands/blob/main/LICENSE"><img src="https://img.shields.io/github/license/All-Hands-AI/OpenHands?style=for-the-badge&color=blue" alt="MIT License"></a>
   <br/>
-  <a href="https://join.slack.com/t/openhands-ai/shared_invite/zt-2ngejmfw6-9gW4APWOC9XUp1n~SiQ6iw"><img src="https://img.shields.io/badge/Slack-Join%20Us-red?logo=slack&logoColor=white&style=for-the-badge" alt="Join our Slack community"></a>
+  <a href="https://join.slack.com/t/openhands-ai/shared_invite/zt-2wkh4pklz-w~h_DVDtEe9H5kyQlcNxVw"><img src="https://img.shields.io/badge/Slack-Join%20Us-red?logo=slack&logoColor=white&style=for-the-badge" alt="Join our Slack community"></a>
   <a href="https://discord.gg/ESHStjSjD4"><img src="https://img.shields.io/badge/Discord-Join%20Us-purple?logo=discord&logoColor=white&style=for-the-badge" alt="Join our Discord community"></a>
   <a href="https://github.com/All-Hands-AI/OpenHands/blob/main/CREDITS.md"><img src="https://img.shields.io/badge/Project-Credits-blue?style=for-the-badge&color=FFE165&logo=github&logoColor=white" alt="Credits"></a>
   <br/>
@@ -39,27 +39,23 @@ Learn more at [docs.all-hands.dev](https://docs.all-hands.dev), or jump to the [
 ## ⚡ Quick Start
 
 The easiest way to run OpenHands is in Docker.
-See the [Running OpenHands](https://docs.all-hands.dev/modules/usage/installation) guide for
+See the [Installation](https://docs.all-hands.dev/modules/usage/installation) guide for
 system requirements and more information.
 
 ```bash
-docker pull docker.all-hands.dev/all-hands-ai/runtime:0.29-nikolaik
+docker pull docker.all-hands.dev/all-hands-ai/runtime:0.19-nikolaik
 
 docker run -it --rm --pull=always \
-    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.29-nikolaik \
+    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.19-nikolaik \
     -e LOG_ALL_EVENTS=true \
     -v /var/run/docker.sock:/var/run/docker.sock \
     -v ~/.openhands-state:/.openhands-state \
     -p 3000:3000 \
     --add-host host.docker.internal:host-gateway \
     --name openhands-app \
-    docker.all-hands.dev/all-hands-ai/openhands:0.29
+    docker.all-hands.dev/all-hands-ai/openhands:0.19
 ```
 
-> [!WARNING]
-> On a public network? See our [Hardened Docker Installation](https://docs.all-hands.dev/modules/usage/runtimes/docker#hardened-docker-installation) guide 
-> to secure your deployment by restricting network binding and implementing additional security measures.
-
 You'll find OpenHands running at [http://localhost:3000](http://localhost:3000)!
 
 Finally, you'll need a model provider and API key.
@@ -73,7 +69,7 @@ run OpenHands in a scriptable [headless mode](https://docs.all-hands.dev/modules
 interact with it via a [friendly CLI](https://docs.all-hands.dev/modules/usage/how-to/cli-mode),
 or run it on tagged issues with [a github action](https://docs.all-hands.dev/modules/usage/how-to/github-action).
 
-Visit [Running OpenHands](https://docs.all-hands.dev/modules/usage/installation) for more information and setup instructions.
+Visit [Installation](https://docs.all-hands.dev/modules/usage/installation) for more information and setup instructions.
 
 > [!CAUTION]
 > OpenHands is meant to be run by a single user on their local workstation.
@@ -100,7 +96,7 @@ troubleshooting resources, and advanced configuration options.
 OpenHands is a community-driven project, and we welcome contributions from everyone. We do most of our communication
 through Slack, so this is the best place to start, but we also are happy to have you contact us on Discord or Github:
 
-- [Join our Slack workspace](https://join.slack.com/t/openhands-ai/shared_invite/zt-2ngejmfw6-9gW4APWOC9XUp1n~SiQ6iw) - Here we talk about research, architecture, and future development.
+- [Join our Slack workspace](https://join.slack.com/t/openhands-ai/shared_invite/zt-2wkh4pklz-w~h_DVDtEe9H5kyQlcNxVw) - Here we talk about research, architecture, and future development.
 - [Join our Discord server](https://discord.gg/ESHStjSjD4) - This is a community-run server for general discussion, questions, and feedback.
 - [Read or post Github Issues](https://github.com/All-Hands-AI/OpenHands/issues) - Check out the issues we're working on, or add your own ideas.
 

build.sh

@@ -1,4 +1,5 @@
-#!/usr/bin/env bash
+#!/bin/bash
 set -e
 
+cp pyproject.toml poetry.lock openhands
 poetry build -v

compose.yml

@@ -1,4 +1,4 @@
-
+#
 services:
   openhands:
     build:
@@ -7,8 +7,8 @@ services:
     image: openhands:latest
     container_name: openhands-app-${DATE:-}
     environment:
-      - SANDBOX_RUNTIME_CONTAINER_IMAGE=${SANDBOX_RUNTIME_CONTAINER_IMAGE:-docker.all-hands.dev/all-hands-ai/runtime:0.29-nikolaik}
-      #- SANDBOX_USER_ID=${SANDBOX_USER_ID:-1234} # enable this only if you want a specific non-root sandbox user but you will have to manually adjust permissions of openhands-state for this user
+      - SANDBOX_RUNTIME_CONTAINER_IMAGE=${SANDBOX_RUNTIME_CONTAINER_IMAGE:-ghcr.io/all-hands-ai/runtime:0.19-nikolaik}
+      - SANDBOX_USER_ID=${SANDBOX_USER_ID:-1234}
       - WORKSPACE_MOUNT_PATH=${WORKSPACE_BASE:-$PWD/workspace}
     ports:
       - "3000:3000"
@@ -16,7 +16,6 @@ services:
       - "host.docker.internal:host-gateway"
     volumes:
       - /var/run/docker.sock:/var/run/docker.sock
-      - ~/.openhands-state:/.openhands-state
       - ${WORKSPACE_BASE:-$PWD/workspace}:/opt/workspace_base
     pull_policy: build
     stdin_open: true

config.template.toml

@@ -17,39 +17,24 @@
 #modal_api_token_id = ""
 #modal_api_token_secret = ""
 
-# API key for Daytona
-#daytona_api_key = ""
-
-# Daytona Target
-#daytona_target = ""
-
 # Base path for the workspace
 workspace_base = "./workspace"
 
 # Cache directory path
 #cache_dir = "/tmp/cache"
 
-# Reasoning effort for o1 models (low, medium, high, or not set)
-#reasoning_effort = "medium"
-
 # Debugging enabled
 #debug = false
 
 # Disable color in terminal output
 #disable_color = false
 
+# Enable saving and restoring the session when run from CLI
+#enable_cli_session = false
+
 # Path to store trajectories, can be a folder or a file
 # If it's a folder, the session id will be used as the file name
-#save_trajectory_path="./trajectories"
-
-# Whether to save screenshots in the trajectory
-# The screenshots are encoded and can make trajectory json files very large
-#save_screenshots_in_trajectory = false
-
-# Path to replay a trajectory, must be a file path
-# If provided, trajectory will be loaded and replayed before the
-# agent responds to any user instruction
-#replay_trajectory_path = ""
+#trajectories_path="./trajectories"
 
 # File store path
 #file_store_path = "/tmp/file_store"
@@ -57,6 +42,9 @@ workspace_base = "./workspace"
 # File store type
 #file_store = "memory"
 
+# List of allowed file extensions for uploads
+#file_uploads_allowed_extensions = [".*"]
+
 # Maximum file size for uploads, in megabytes
 #file_uploads_max_file_size_mb = 0
 
@@ -79,7 +67,7 @@ workspace_base = "./workspace"
 #run_as_openhands = true
 
 # Runtime environment
-#runtime = "docker"
+#runtime = "eventstream"
 
 # Name of the default agent
 #default_agent = "CodeActAgent"
@@ -93,17 +81,6 @@ workspace_base = "./workspace"
 # List of allowed file extensions for uploads
 #file_uploads_allowed_extensions = [".*"]
 
-# Whether to enable the default LLM summarizing condenser when no condenser is specified in config
-# When true, a LLMSummarizingCondenserConfig will be used as the default condenser
-# When false, a NoOpCondenserConfig (no summarization) will be used
-#enable_default_condenser = true
-
-# Maximum number of concurrent conversations per user
-#max_concurrent_conversations = 3
-
-# Maximum age of conversations in seconds before they are automatically closed
-#conversation_max_age_seconds = 864000  # 10 days
-
 #################################### LLM #####################################
 # Configuration for LLM models (group name starts with 'llm')
 # use 'llm' for the default LLM config
@@ -119,7 +96,7 @@ workspace_base = "./workspace"
 #aws_secret_access_key = ""
 
 # API key to use (For Headless / CLI only -  In Web this is overridden by Session Init)
-api_key = ""
+api_key = "your-api-key"
 
 # API base URL (For Headless / CLI only -  In Web this is overridden by Session Init)
 #base_url = ""
@@ -136,6 +113,15 @@ api_key = ""
 # Custom LLM provider
 #custom_llm_provider = ""
 
+# Embedding API base URL
+#embedding_base_url = ""
+
+# Embedding deployment name
+#embedding_deployment_name = ""
+
+# Embedding model to use
+embedding_model = "local"
+
 # Maximum number of characters in an observation's content
 #max_message_chars = 10000
 
@@ -200,10 +186,8 @@ model = "gpt-4o"
 # https://github.com/All-Hands-AI/OpenHands/pull/4711
 #native_tool_calling = None
 
-
-
 [llm.gpt4o-mini]
-api_key = ""
+api_key = "your-api-key"
 model = "gpt-4o"
 
 
@@ -215,28 +199,33 @@ model = "gpt-4o"
 ##############################################################################
 [agent]
 
-# Whether the browsing tool is enabled
+# whether the browsing tool is enabled
 codeact_enable_browsing = true
 
-# Whether the LLM draft editor is enabled
+# whether the LLM draft editor is enabled
 codeact_enable_llm_editor = false
 
-# Whether the IPython tool is enabled
+# whether the IPython tool is enabled
 codeact_enable_jupyter = true
 
+# Name of the micro agent to use for this agent
+#micro_agent_name = ""
+
+# Memory enabled
+#memory_enabled = false
+
+# Memory maximum threads
+#memory_max_threads = 3
+
 # LLM config group to use
 #llm_config = 'your-llm-config-group'
 
-# Whether to use prompt extension (e.g., microagent, repo/runtime info) at all
-#enable_prompt_extensions = true
+# Whether to use microagents at all
+#use_microagents = true
 
 # List of microagents to disable
 #disabled_microagents = []
 
-# Whether history should be truncated to continue the session when hitting LLM context
-# length limit
-enable_history_truncation = true
-
 [agent.RepoExplorerAgent]
 # Example: use a cheaper model for RepoExplorerAgent to reduce cost, especially
 # useful when an agent doesn't demand high quality but uses a lot of tokens
@@ -258,7 +247,7 @@ llm_config = 'gpt3'
 # Use host network
 #use_host_network = false
 
-# Runtime extra build args
+# runtime extra build args
 #runtime_extra_build_args = ["--network=host", "--add-host=host.docker.internal:host-gateway"]
 
 # Enable auto linting after editing
@@ -276,33 +265,6 @@ llm_config = 'gpt3'
 # BrowserGym environment to use for evaluation
 #browsergym_eval_env = ""
 
-# Platform to use for building the runtime image (e.g., "linux/amd64")
-#platform = ""
-
-# Force rebuild of runtime image even if it exists
-#force_rebuild_runtime = false
-
-# Runtime container image to use (if not provided, will be built from base_container_image)
-#runtime_container_image = ""
-
-# Keep runtime alive after session ends
-#keep_runtime_alive = false
-
-# Pause closed runtimes instead of stopping them
-#pause_closed_runtimes = false
-
-# Delay in seconds before closing idle runtimes
-#close_delay = 300
-
-# Remove all containers when stopping the runtime
-#rm_all_containers = false
-
-# Enable GPU support in the runtime
-#enable_gpu = false
-
-# Additional Docker runtime kwargs
-#docker_runtime_kwargs = {}
-
 #################################### Security ###################################
 # Configuration for security features
 ##############################################################################
@@ -314,72 +276,6 @@ llm_config = 'gpt3'
 # The security analyzer to use (For Headless / CLI only -  In Web this is overridden by Session Init)
 #security_analyzer = ""
 
-# Whether to enable security analyzer
-#enable_security_analyzer = false
-
-#################################### Condenser #################################
-# Condensers control how conversation history is managed and compressed when
-# the context grows too large. Each agent uses one condenser configuration.
-##############################################################################
-[condenser]
-# The type of condenser to use. Available options:
-# - "noop": No condensing, keeps full history (default)
-# - "observation_masking": Keeps full event structure but masks older observations
-# - "recent": Keeps only recent events and discards older ones
-# - "llm": Uses an LLM to summarize conversation history
-# - "amortized": Intelligently forgets older events while preserving important context
-# - "llm_attention": Uses an LLM to prioritize most relevant context
-type = "noop"
-
-# Examples for each condenser type (uncomment and modify as needed):
-
-# 1. NoOp Condenser - No additional settings needed
-#type = "noop"
-
-# 2. Observation Masking Condenser
-#type = "observation_masking"
-# Number of most-recent events where observations will not be masked
-#attention_window = 100
-
-# 3. Recent Events Condenser
-#type = "recent"
-# Number of initial events to always keep (typically includes task description)
-#keep_first = 1
-# Maximum number of events to keep in history
-#max_events = 100
-
-# 4. LLM Summarizing Condenser
-#type = "llm"
-# Reference to an LLM config to use for summarization
-#llm_config = "condenser"
-# Number of initial events to always keep (typically includes task description)
-#keep_first = 1
-# Maximum size of history before triggering summarization
-#max_size = 100
-
-# 5. Amortized Forgetting Condenser
-#type = "amortized"
-# Number of initial events to always keep (typically includes task description)
-#keep_first = 1
-# Maximum size of history before triggering forgetting
-#max_size = 100
-
-# 6. LLM Attention Condenser
-#type = "llm_attention"
-# Reference to an LLM config to use for attention scoring
-#llm_config = "condenser"
-# Number of initial events to always keep (typically includes task description)
-#keep_first = 1
-# Maximum size of history before triggering attention mechanism
-#max_size = 100
-
-# Example of a custom LLM configuration for condensers that require an LLM
-# If not provided, it falls back to the default LLM
-#[llm.condenser]
-#model = "gpt-4o"
-#temperature = 0.1
-#max_tokens = 1024
-
 #################################### Eval ####################################
 # Configuration for the evaluation, please refer to the specific evaluation
 # plugin for the available options

containers/app/Dockerfile

@@ -26,7 +26,7 @@ RUN apt-get update -y \
 
 COPY ./pyproject.toml ./poetry.lock ./
 RUN touch README.md
-RUN export POETRY_CACHE_DIR && poetry install --without evaluation --no-root && rm -rf $POETRY_CACHE_DIR
+RUN export POETRY_CACHE_DIR && poetry install --without evaluation,llama-index --no-root && rm -rf $POETRY_CACHE_DIR
 
 FROM python:3.12.3-slim AS openhands-app
 

containers/build.sh

@@ -1,4 +1,4 @@
-#!/usr/bin/env bash
+#!/bin/bash
 set -eo pipefail
 
 # Initialize variables with default values

containers/dev/compose.yml

@@ -11,7 +11,7 @@ services:
       - BACKEND_HOST=${BACKEND_HOST:-"0.0.0.0"}
       - SANDBOX_API_HOSTNAME=host.docker.internal
       #
-      - SANDBOX_RUNTIME_CONTAINER_IMAGE=${SANDBOX_RUNTIME_CONTAINER_IMAGE:-ghcr.io/all-hands-ai/runtime:0.29-nikolaik}
+      - SANDBOX_RUNTIME_CONTAINER_IMAGE=${SANDBOX_RUNTIME_CONTAINER_IMAGE:-ghcr.io/all-hands-ai/runtime:0.19-nikolaik}
       - SANDBOX_USER_ID=${SANDBOX_USER_ID:-1234}
       - WORKSPACE_MOUNT_PATH=${WORKSPACE_BASE:-$PWD/workspace}
     ports:

containers/dev/dev.sh

@@ -1,4 +1,4 @@
-#!/usr/bin/env bash
+#!/bin/bash
 set -o pipefail
 
 function get_docker() {

dev_config/python/ruff.toml

@@ -24,6 +24,3 @@ inline-quotes = "single"
 
 [format]
 quote-style = "single"
-
-[lint.flake8-bugbear]
-extend-immutable-calls = ["Depends", "fastapi.Depends", "fastapi.params.Depends"]

docs/DOC_STYLE_GUIDE.md

@@ -46,11 +46,3 @@ docker run -it \
     -e THAT=that
     ...
 ```
-
-### Referring to UI Elements
-
-When referencing UI elements, use ``.
-
-Example:
-1. Toggle the `Advanced` option
-2. Enter your model in the `Custom Model` textbox.

docs/docusaurus.config.ts

@@ -75,6 +75,12 @@ const config: Config = {
           position: "left",
           label: "User Guides",
         },
+        {
+          type: "docSidebar",
+          sidebarId: "apiSidebar",
+          position: "left",
+          label: "Python API",
+        },
         {
           type: 'localeDropdown',
           position: 'left',

docs/i18n/fr/code.json

@@ -402,26 +402,5 @@
   "theme.unlistedContent.message": {
     "message": "Cette page n'est pas répertoriée. Les moteurs de recherche ne l'indexeront pas, et seuls les utilisateurs ayant un lien direct peuvent y accéder.",
     "description": "The unlisted content banner message"
-  },
-  "Use AI to tackle the toil in your backlog. Our agents have all the same tools as a human developer: they can modify code, run commands, browse the web, call APIs, and yes-even copy code snippets from StackOverflow.": {
-    "message": "Utilisez l'IA pour gérer les tâches répétitives de votre backlog. Nos agents disposent des mêmes outils qu'un développeur humain : ils peuvent modifier du code, exécuter des commandes, naviguer sur le web, appeler des API et même copier des extraits de code depuis StackOverflow."
-  },
-  "Get started with OpenHands.": {
-    "message": "Commencer avec OpenHands"
-  },
-  "Most Popular Links": {
-    "message": "Liens Populaires"
-  },
-  "Customizing OpenHands to a repository": {
-    "message": "Personnaliser OpenHands pour un dépôt"
-  },
-  "Integrating OpenHands with Github": {
-    "message": "Intégrer OpenHands avec Github"
-  },
-  "Recommended models to use": {
-    "message": "Modèles recommandés"
-  },
-  "Connecting OpenHands to your filesystem": {
-    "message": "Connecter OpenHands à votre système de fichiers"
   }
 }

docs/i18n/fr/docusaurus-plugin-content-docs/current/usage/architecture/runtime.md

@@ -1,8 +1,8 @@
 
 
-# 📦 Runtime Docker
+# 📦 Runtime EventStream
 
-Le Runtime Docker d'OpenHands est le composant principal qui permet l'exécution sécurisée et flexible des actions des agents d'IA.
+Le Runtime EventStream d'OpenHands est le composant principal qui permet l'exécution sécurisée et flexible des actions des agents d'IA.
 Il crée un environnement en bac à sable (sandbox) en utilisant Docker, où du code arbitraire peut être exécuté en toute sécurité sans risquer le système hôte.
 
 ## Pourquoi avons-nous besoin d'un runtime en bac à sable ?

docs/i18n/fr/docusaurus-plugin-content-docs/current/usage/configuration-options.md

@@ -1,3 +1,5 @@
+
+
 # Options de configuration
 
 Ce guide détaille toutes les options de configuration disponibles pour OpenHands, vous aidant à personnaliser son comportement et à l'intégrer avec d'autres services.
@@ -11,39 +13,41 @@ la priorité.
 
 # Table des matières
 
-1. [Configuration de base](#core-configuration)
-   - [Clés API](#api-keys)
-   - [Espace de travail](#workspace)
-   - [Débogage et journalisation](#debugging-and-logging)
-   - [Trajectoires](#trajectories)
-   - [Stockage de fichiers](#file-store)
-   - [Gestion des tâches](#task-management)
-   - [Configuration du bac à sable](#sandbox-configuration)
-   - [Divers](#miscellaneous)
-2. [Configuration LLM](#llm-configuration)
-   - [Informations d'identification AWS](#aws-credentials)
-   - [Configuration de l'API](#api-configuration)
-   - [Fournisseur LLM personnalisé](#custom-llm-provider)
+1. [Configuration de base](#configuration-de-base)
+   - [Clés API](#clés-api)
+   - [Espace de travail](#espace-de-travail)
+   - [Débogage et journalisation](#débogage-et-journalisation)
+   - [Gestion des sessions](#gestion-des-sessions)
+   - [Trajectoires](#trajectoires)
+   - [Stockage de fichiers](#stockage-de-fichiers)
+   - [Gestion des tâches](#gestion-des-tâches)
+   - [Configuration du bac à sable](#configuration-du-bac-à-sable)
+   - [Divers](#divers)
+2. [Configuration LLM](#configuration-llm)
+   - [Informations d'identification AWS](#informations-didentification-aws)
+   - [Configuration de l'API](#configuration-de-lapi)
+   - [Fournisseur LLM personnalisé](#fournisseur-llm-personnalisé)
    - [Embeddings](#embeddings)
-   - [Gestion des messages](#message-handling)
-   - [Sélection du modèle](#model-selection)
-   - [Nouvelles tentatives](#retrying)
-   - [Options avancées](#advanced-options)
-3. [Configuration de l'agent](#agent-configuration)
-   - [Configuration de la mémoire](#memory-configuration)
-   - [Configuration LLM](#llm-configuration-1)
-   - [Configuration de l'espace d'action](#actionspace-configuration)
-   - [Utilisation du micro-agent](#microagent-usage)
-4. [Configuration du bac à sable](#sandbox-configuration-1)
-   - [Exécution](#execution)
-   - [Image de conteneur](#container-image)
-   - [Mise en réseau](#networking)
-   - [Linting et plugins](#linting-and-plugins)
-   - [Dépendances et environnement](#dependencies-and-environment)
-   - [Évaluation](#evaluation)
-5. [Configuration de sécurité](#security-configuration)
-   - [Mode de confirmation](#confirmation-mode)
-   - [Analyseur de sécurité](#security-analyzer)
+   - [Gestion des messages](#gestion-des-messages)
+   - [Sélection du modèle](#sélection-du-modèle)
+   - [Nouvelles tentatives](#nouvelles-tentatives)
+   - [Options avancées](#options-avancées)
+3. [Configuration de l'agent](#configuration-de-lagent)
+   - [Configuration du micro-agent](#configuration-du-micro-agent)
+   - [Configuration de la mémoire](#configuration-de-la-mémoire)
+   - [Configuration LLM](#configuration-llm-2)
+   - [Configuration de l'espace d'action](#configuration-de-lespace-daction)
+   - [Utilisation du micro-agent](#utilisation-du-micro-agent)
+4. [Configuration du bac à sable](#configuration-du-bac-à-sable-2)
+   - [Exécution](#exécution)
+   - [Image de conteneur](#image-de-conteneur)
+   - [Mise en réseau](#mise-en-réseau)
+   - [Linting et plugins](#linting-et-plugins)
+   - [Dépendances et environnement](#dépendances-et-environnement)
+   - [Évaluation](#évaluation)
+5. [Configuration de sécurité](#configuration-de-sécurité)
+   - [Mode de confirmation](#mode-de-confirmation)
+   - [Analyseur de sécurité](#analyseur-de-sécurité)
 
 ---
 
@@ -90,7 +94,7 @@ Les options de configuration de base sont définies dans la section `[core]` du
   - Description : Désactiver la couleur dans la sortie du terminal
 
 **Trajectoires**
-- `save_trajectory_path`
+- `trajectories_path`
   - Type : `str`
   - Valeur par défaut : `"./trajectories"`
   - Description : Chemin pour stocker les trajectoires (peut être un dossier ou un fichier). Si c'est un dossier, les trajectoires seront enregistrées dans un fichier nommé avec l'ID de session et l'extension .json, dans ce dossier.
@@ -161,7 +165,7 @@ Les options de configuration de base sont définies dans la section `[core]` du
 
 - `runtime`
   - Type : `str`
-  - Valeur par défaut : `"docker"`
+  - Valeur par défaut : `"eventstream"`
   - Description : Environnement d'exécution
 
 - `default_agent`
@@ -180,10 +184,6 @@ Les options de configuration LLM (Large Language Model) sont définies dans la s
 
 Pour les utiliser avec la commande docker, passez `-e LLM_<option>`. Exemple : `-e LLM_NUM_RETRIES`.
 
-:::note
-Pour les configurations de développement, vous pouvez également définir des configurations LLM personnalisées. Voir [Configurations LLM personnalisées](./llms/custom-llm-configs) pour plus de détails.
-:::
-
 **Informations d'identification AWS**
 - `aws_access_key_id`
   - Type : `str`
@@ -331,6 +331,12 @@ Pour les configurations de développement, vous pouvez également définir des c
 
 Les options de configuration de l'agent sont définies dans les sections `[agent]` et `[agent.<agent_name>]` du fichier `config.toml`.
 
+**Configuration du micro-agent**
+- `micro_agent_name`
+  - Type : `str`
+  - Valeur par défaut : `""`
+  - Description : Nom du micro-agent à utiliser pour cet agent
+
 **Configuration de la mémoire**
 - `memory_enabled`
   - Type : `bool`
@@ -362,26 +368,4 @@ Les options de configuration de l'agent sont définies dans les sections `[agent
 - `codeact_enable_llm_editor`
   - Type : `bool`
   - Valeur par défaut : `false`
-  - Description : Si l'éditeur LLM est activé dans l'espace d'action (fonctionne uniquement avec l'appel de fonction)
-
-**Utilisation du micro-agent**
-- `enable_prompt_extensions`
-  - Type : `bool`
-  - Valeur par défaut : `true`
-  - Description : Indique si l'utilisation des micro-agents est activée ou non
-
-- `disabled_microagents`
-  - Type : `list of str`
-  - Valeur par défaut : `None`
-  - Description : Liste des micro-agents à désactiver
-
-### Exécution
-- `timeout`
-  - Type : `int`
-  - Valeur par défaut : `120`
-  - Description : Délai d'expiration du bac à sable, en secondes
-
-- `user_id`
-  - Type : `int`
-  - Valeur par défaut : `1000`
-  - Description : ID de l'utilisateur du bac à sable
+  - Description : Si l'éditeur LLM est activé dans l'espace d'action (foncti

docs/i18n/fr/docusaurus-plugin-content-docs/current/usage/custom_sandbox_guide.md

@@ -42,11 +42,10 @@ Créez un fichier ```config.toml``` dans le répertoire OpenHands et entrez ces
 [core]
 workspace_base="./workspace"
 run_as_openhands=true
-[sandbox]
-base_container_image="image_personnalisée"
+sandbox_base_container_image="image_personnalisée"
 ```
 
-> Assurez-vous que ```base_container_image``` est défini sur le nom de votre image personnalisée précédente.
+> Assurez-vous que ```sandbox_base_container_image``` est défini sur le nom de votre image personnalisée précédente.
 
 ## Exécution
 
@@ -83,17 +82,20 @@ dockerfile_content = (
 ## Dépannage / Erreurs
 
 ### Erreur: ```useradd: UID 1000 est non unique```
-Si vous voyez cette erreur dans la sortie de la console, il s'agit du fait que OpenHands essaie de créer le utilisateur openhands dans le sandbox avec un ID d'utilisateur de 1000, cependant cet ID d'utilisateur est déjà utilisé dans l'image (pour une raison inconnue). Pour résoudre ce problème, changez la valeur du champ user_id dans le fichier config.toml en une valeur différente:
+Si vous voyez cette erreur dans la sortie de la console, il s'agit du fait que OpenHands essaie de créer le utilisateur openhands dans le sandbox avec un ID d'utilisateur de 1000, cependant cet ID d'utilisateur est déjà utilisé dans l'image (pour une raison inconnue). Pour résoudre ce problème, changez la valeur du champ sandbox_user_id dans le fichier config.toml en une valeur différente:
 
 ```toml
 [core]
 workspace_base="./workspace"
 run_as_openhands=true
-[sandbox]
-base_container_image="image_personnalisée"
-user_id="1001"
+sandbox_base_container_image="image_personnalisée"
+sandbox_user_id="1001"
 ```
 
 ### Erreurs de port d'utilisation
 
 Si vous voyez un message d'erreur indiquant que le port est utilisé ou indisponible, essayez de supprimer toutes les containers docker en cours d'exécution (exécutez `docker ps` et `docker rm` des containers concernés) puis ré-exécutez ```make run```
+
+## Discuter
+
+Pour d'autres problèmes ou questions rejoignez le [Slack](https://join.slack.com/t/openhands-ai/shared_invite/zt-2wkh4pklz-w~h_DVDtEe9H5kyQlcNxVw) ou le [Discord](https://discord.gg/ESHStjSjD4) et demandez!

docs/i18n/fr/docusaurus-plugin-content-docs/current/usage/how-to/cli-mode.md

@@ -52,7 +52,7 @@ LLM_API_KEY="sk_test_12345"
 ```bash
 docker run -it \
     --pull=always \
-    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.29-nikolaik \
+    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.19-nikolaik \
     -e SANDBOX_USER_ID=$(id -u) \
     -e WORKSPACE_MOUNT_PATH=$WORKSPACE_BASE \
     -e LLM_API_KEY=$LLM_API_KEY \
@@ -61,7 +61,7 @@ docker run -it \
     -v /var/run/docker.sock:/var/run/docker.sock \
     --add-host host.docker.internal:host-gateway \
     --name openhands-app-$(date +%Y%m%d%H%M%S) \
-    docker.all-hands.dev/all-hands-ai/openhands:0.29 \
+    docker.all-hands.dev/all-hands-ai/openhands:0.19 \
     python -m openhands.core.cli
 ```
 

docs/i18n/fr/docusaurus-plugin-content-docs/current/usage/how-to/custom-sandbox-guide.md

@@ -44,13 +44,12 @@ Tout d'abord, assurez-vous de pouvoir exécuter OpenHands en suivant les instruc
 
 ### Spécifier l'Image de Base du Sandbox
 
-Dans le fichier `config.toml` dans le répertoire OpenHands, définissez `base_container_image` sur l'image que vous souhaitez utiliser. Cela peut être une image que vous avez déjà extraite ou une que vous avez construite :
+Dans le fichier `config.toml` dans le répertoire OpenHands, définissez `sandbox_base_container_image` sur l'image que vous souhaitez utiliser. Cela peut être une image que vous avez déjà extraite ou une que vous avez construite :
 
 ```bash
 [core]
 ...
-[sandbox]
-base_container_image="custom-image"
+sandbox_base_container_image="custom-image"
 ```
 
 ### Exécution

docs/i18n/fr/docusaurus-plugin-content-docs/current/usage/how-to/evaluation-harness.md

@@ -114,7 +114,7 @@ Pour créer un workflow d'évaluation pour votre benchmark, suivez ces étapes :
    def get_config(instance: pd.Series, metadata: EvalMetadata) -> AppConfig:
        config = AppConfig(
            default_agent=metadata.agent_class,
-           runtime='docker',
+           runtime='eventstream',
            max_iterations=metadata.max_iterations,
            sandbox=SandboxConfig(
                base_container_image='your_container_image',

docs/i18n/fr/docusaurus-plugin-content-docs/current/usage/how-to/headless-mode.md

@@ -46,7 +46,7 @@ LLM_API_KEY="sk_test_12345"
 ```bash
 docker run -it \
     --pull=always \
-    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.29-nikolaik \
+    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.19-nikolaik \
     -e SANDBOX_USER_ID=$(id -u) \
     -e WORKSPACE_MOUNT_PATH=$WORKSPACE_BASE \
     -e LLM_API_KEY=$LLM_API_KEY \
@@ -56,6 +56,6 @@ docker run -it \
     -v /var/run/docker.sock:/var/run/docker.sock \
     --add-host host.docker.internal:host-gateway \
     --name openhands-app-$(date +%Y%m%d%H%M%S) \
-    docker.all-hands.dev/all-hands-ai/openhands:0.29 \
+    docker.all-hands.dev/all-hands-ai/openhands:0.19 \
     python -m openhands.core.main -t "write a bash script that prints hi" --no-auto-continue
 ```

docs/i18n/fr/docusaurus-plugin-content-docs/current/usage/installation.mdx

@@ -13,16 +13,16 @@
 La façon la plus simple d'exécuter OpenHands est avec Docker.
 
 ```bash
-docker pull docker.all-hands.dev/all-hands-ai/runtime:0.29-nikolaik
+docker pull docker.all-hands.dev/all-hands-ai/runtime:0.19-nikolaik
 
 docker run -it --rm --pull=always \
-    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.29-nikolaik \
+    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.19-nikolaik \
     -e LOG_ALL_EVENTS=true \
     -v /var/run/docker.sock:/var/run/docker.sock \
     -p 3000:3000 \
     --add-host host.docker.internal:host-gateway \
     --name openhands-app \
-    docker.all-hands.dev/all-hands-ai/openhands:0.29
+    docker.all-hands.dev/all-hands-ai/openhands:0.19
 ```
 
 Vous pouvez également exécuter OpenHands en mode [headless scriptable](https://docs.all-hands.dev/modules/usage/how-to/headless-mode), en tant que [CLI interactive](https://docs.all-hands.dev/modules/usage/how-to/cli-mode), ou en utilisant l'[Action GitHub OpenHands](https://docs.all-hands.dev/modules/usage/how-to/github-action).

docs/i18n/fr/docusaurus-plugin-content-docs/current/usage/intro.mdx

@@ -42,7 +42,7 @@ Explorez le code source d'OpenHands sur [GitHub](https://github.com/All-Hands-AI
   />
 </a>
 <br></br>
-<a href="https://join.slack.com/t/openhands-ai/shared_invite/zt-2ngejmfw6-9gW4APWOC9XUp1n~SiQ6iw">
+<a href="https://join.slack.com/t/openhands-ai/shared_invite/zt-2wkh4pklz-w~h_DVDtEe9H5kyQlcNxVw">
   <img
     src="https://img.shields.io/badge/Slack-Join%20Us-red?logo=slack&logoColor=white&style=for-the-badge"
     alt="Join our Slack community"

docs/i18n/fr/docusaurus-plugin-content-docs/current/usage/llms/custom-llm-configs.md

@@ -1,106 +0,0 @@
-# Configurations LLM personnalisées
-
-OpenHands permet de définir plusieurs configurations LLM nommées dans votre fichier `config.toml`. Cette fonctionnalité vous permet d'utiliser différentes configurations LLM pour différents usages, comme utiliser un modèle moins coûteux pour les tâches qui ne nécessitent pas de réponses de haute qualité, ou utiliser différents modèles avec différents paramètres pour des agents spécifiques.
-
-## Comment ça fonctionne
-
-Les configurations LLM nommées sont définies dans le fichier `config.toml` en utilisant des sections qui commencent par `llm.`. Par exemple :
-
-```toml
-# Configuration LLM par défaut
-[llm]
-model = "gpt-4"
-api_key = "votre-clé-api"
-temperature = 0.0
-
-# Configuration LLM personnalisée pour un modèle moins coûteux
-[llm.gpt3]
-model = "gpt-3.5-turbo"
-api_key = "votre-clé-api"
-temperature = 0.2
-
-# Une autre configuration personnalisée avec des paramètres différents
-[llm.haute-creativite]
-model = "gpt-4"
-api_key = "votre-clé-api"
-temperature = 0.8
-top_p = 0.9
-```
-
-Chaque configuration nommée hérite de tous les paramètres de la section `[llm]` par défaut et peut remplacer n'importe lequel de ces paramètres. Vous pouvez définir autant de configurations personnalisées que nécessaire.
-
-## Utilisation des configurations personnalisées
-
-### Avec les agents
-
-Vous pouvez spécifier quelle configuration LLM un agent doit utiliser en définissant le paramètre `llm_config` dans la section de configuration de l'agent :
-
-```toml
-[agent.RepoExplorerAgent]
-# Utiliser la configuration GPT-3 moins coûteuse pour cet agent
-llm_config = 'gpt3'
-
-[agent.CodeWriterAgent]
-# Utiliser la configuration haute créativité pour cet agent
-llm_config = 'haute-creativite'
-```
-
-### Options de configuration
-
-Chaque configuration LLM nommée prend en charge toutes les mêmes options que la configuration LLM par défaut. Celles-ci incluent :
-
-- Sélection du modèle (`model`)
-- Configuration de l'API (`api_key`, `base_url`, etc.)
-- Paramètres du modèle (`temperature`, `top_p`, etc.)
-- Paramètres de nouvelle tentative (`num_retries`, `retry_multiplier`, etc.)
-- Limites de jetons (`max_input_tokens`, `max_output_tokens`)
-- Et toutes les autres options de configuration LLM
-
-Pour une liste complète des options disponibles, consultez la section Configuration LLM dans la documentation des [Options de configuration](../configuration-options).
-
-## Cas d'utilisation
-
-Les configurations LLM personnalisées sont particulièrement utiles dans plusieurs scénarios :
-
-- **Optimisation des coûts** : Utiliser des modèles moins coûteux pour les tâches qui ne nécessitent pas de réponses de haute qualité, comme l'exploration de dépôt ou les opérations simples sur les fichiers.
-- **Réglage spécifique aux tâches** : Configurer différentes valeurs de température et de top_p pour les tâches qui nécessitent différents niveaux de créativité ou de déterminisme.
-- **Différents fournisseurs** : Utiliser différents fournisseurs LLM ou points d'accès API pour différentes tâches.
-- **Tests et développement** : Basculer facilement entre différentes configurations de modèles pendant le développement et les tests.
-
-## Exemple : Optimisation des coûts
-
-Un exemple pratique d'utilisation des configurations LLM personnalisées pour optimiser les coûts :
-
-```toml
-# Configuration par défaut utilisant GPT-4 pour des réponses de haute qualité
-[llm]
-model = "gpt-4"
-api_key = "votre-clé-api"
-temperature = 0.0
-
-# Configuration moins coûteuse pour l'exploration de dépôt
-[llm.repo-explorer]
-model = "gpt-3.5-turbo"
-temperature = 0.2
-
-# Configuration pour la génération de code
-[llm.code-gen]
-model = "gpt-4"
-temperature = 0.0
-max_output_tokens = 2000
-
-[agent.RepoExplorerAgent]
-llm_config = 'repo-explorer'
-
-[agent.CodeWriterAgent]
-llm_config = 'code-gen'
-```
-
-Dans cet exemple :
-- L'exploration de dépôt utilise un modèle moins coûteux car il s'agit principalement de comprendre et de naviguer dans le code
-- La génération de code utilise GPT-4 avec une limite de jetons plus élevée pour générer des blocs de code plus importants
-- La configuration par défaut reste disponible pour les autres tâches
-
-:::note
-Les configurations LLM personnalisées ne sont disponibles que lors de l'utilisation d'OpenHands en mode développement, via `main.py` ou `cli.py`. Lors de l'exécution via `docker run`, veuillez utiliser les options de configuration standard.
-:::

docs/i18n/fr/docusaurus-plugin-content-docs/current/usage/runtimes.md

@@ -13,7 +13,7 @@ C'est le Runtime par défaut qui est utilisé lorsque vous démarrez OpenHands.
 
 ```
 docker run # ...
-    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.29-nikolaik \
+    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.19-nikolaik \
     -v /var/run/docker.sock:/var/run/docker.sock \
     # ...
 ```

docs/i18n/zh-Hans/code.json

@@ -402,26 +402,5 @@
   "theme.unlistedContent.message": {
     "message": "此页面未列出。搜索引擎不会对其索引，只有拥有直接链接的用户才能访问。",
     "description": "The unlisted content banner message"
-  },
-  "Use AI to tackle the toil in your backlog. Our agents have all the same tools as a human developer: they can modify code, run commands, browse the web, call APIs, and yes-even copy code snippets from StackOverflow.": {
-    "message": "使用AI处理您积压的工作。我们的代理拥有与人类开发者相同的工具：它们可以修改代码、运行命令、浏览网页、调用API，甚至从StackOverflow复制代码片段。"
-  },
-  "Get started with OpenHands.": {
-    "message": "开始使用OpenHands"
-  },
-  "Most Popular Links": {
-    "message": "热门链接"
-  },
-  "Customizing OpenHands to a repository": {
-    "message": "为仓库定制OpenHands"
-  },
-  "Integrating OpenHands with Github": {
-    "message": "将OpenHands与Github集成"
-  },
-  "Recommended models to use": {
-    "message": "推荐使用的模型"
-  },
-  "Connecting OpenHands to your filesystem": {
-    "message": "将OpenHands连接到您的文件系统"
   }
 }

docs/i18n/zh-Hans/docusaurus-plugin-content-docs/current/usage/architecture/runtime.md

@@ -1,8 +1,8 @@
 以下是翻译后的内容:
 
-# 📦 Docker 运行时
+# 📦 EventStream 运行时
 
-OpenHands Docker 运行时是实现 AI 代理操作安全灵活执行的核心组件。
+OpenHands EventStream 运行时是实现 AI 代理操作安全灵活执行的核心组件。
 它使用 Docker 创建一个沙盒环境,可以安全地运行任意代码而不会危及主机系统。
 
 ## 为什么我们需要沙盒运行时?

docs/i18n/zh-Hans/docusaurus-plugin-content-docs/current/usage/configuration-options.md

@@ -10,39 +10,41 @@
 
 # 目录
 
-1. [核心配置](#core-configuration)
+1. [核心配置](#核心配置)
    - [API Keys](#api-keys)
-   - [工作区](#workspace)
-   - [调试和日志记录](#debugging-and-logging)
-   - [轨迹](#trajectories)
-   - [文件存储](#file-store)
-   - [任务管理](#task-management)
-   - [沙箱配置](#sandbox-configuration)
-   - [其他](#miscellaneous)
-2. [LLM 配置](#llm-configuration)
-   - [AWS 凭证](#aws-credentials)
-   - [API 配置](#api-configuration)
-   - [自定义 LLM Provider](#custom-llm-provider)
+   - [工作区](#工作区)
+   - [调试和日志记录](#调试和日志记录)
+   - [会话管理](#会话管理)
+   - [轨迹](#轨迹)
+   - [文件存储](#文件存储)
+   - [任务管理](#任务管理)
+   - [沙箱配置](#沙箱配置)
+   - [其他](#其他)
+2. [LLM 配置](#llm-配置)
+   - [AWS 凭证](#aws-凭证)
+   - [API 配置](#api-配置)
+   - [自定义 LLM Provider](#自定义-llm-provider)
    - [Embeddings](#embeddings)
-   - [消息处理](#message-handling)
-   - [模型选择](#model-selection)
-   - [重试](#retrying)
-   - [高级选项](#advanced-options)
-3. [Agent 配置](#agent-configuration)
-   - [内存配置](#memory-configuration)
-   - [LLM 配置](#llm-configuration-1)
-   - [ActionSpace 配置](#actionspace-configuration)
-   - [Microagent 使用](#microagent-usage)
-4. [沙箱配置](#sandbox-configuration-1)
-   - [执行](#execution)
-   - [容器镜像](#container-image)
-   - [网络](#networking)
-   - [Linting 和插件](#linting-and-plugins)
-   - [依赖和环境](#dependencies-and-environment)
-   - [评估](#evaluation)
-5. [安全配置](#security-configuration)
-   - [确认模式](#confirmation-mode)
-   - [安全分析器](#security-analyzer)
+   - [消息处理](#消息处理)
+   - [模型选择](#模型选择)
+   - [重试](#重试)
+   - [高级选项](#高级选项)
+3. [Agent 配置](#agent-配置)
+   - [Microagent 配置](#microagent-配置)
+   - [内存配置](#内存配置)
+   - [LLM 配置](#llm-配置-2)
+   - [ActionSpace 配置](#actionspace-配置)
+   - [Microagent 使用](#microagent-使用)
+4. [沙箱配置](#沙箱配置-2)
+   - [执行](#执行)
+   - [容器镜像](#容器镜像)
+   - [网络](#网络)
+   - [Linting 和插件](#linting-和插件)
+   - [依赖和环境](#依赖和环境)
+   - [评估](#评估)
+5. [安全配置](#安全配置)
+   - [确认模式](#确认模式)
+   - [安全分析器](#安全分析器)
 
 ---
 
@@ -89,7 +91,7 @@
   - 描述: 禁用终端输出中的颜色
 
 **轨迹**
-- `save_trajectory_path`
+- `trajectories_path`
   - 类型: `str`
   - 默认值: `"./trajectories"`
   - 描述: 存储轨迹的路径(可以是文件夹或文件)。如果是文件夹,轨迹将保存在该文件夹中以会话 ID 命名的 .json 文件中。
@@ -160,7 +162,7 @@
 
 - `runtime`
   - 类型: `str`
-  - 默认值: `"docker"`
+  - 默认值: `"eventstream"`
   - 描述: 运行时环境
 
 - `default_agent`
@@ -326,6 +328,12 @@ LLM(大语言模型)配置选项在 `config.toml` 文件的 `[llm]` 部分中定
 
 Agent 配置选项在 `config.toml` 文件的 `[agent]` 和 `[agent.<agent_name>]` 部分中定义。
 
+**Microagent 配置**
+- `micro_agent_name`
+  - 类型: `str`
+  - 默认值: `""`
+  - 描述: 用于此 agent 的 micro agent 名称
+
 **内存配置**
 - `memory_enabled`
   - 类型: `bool`
@@ -365,7 +373,7 @@ Agent 配置选项在 `config.toml` 文件的 `[agent]` 和 `[agent.<agent_name>
   - 描述: 是否在 action space 中启用 Jupyter
 
 **Microagent 使用**
-- `enable_prompt_extensions`
+- `use_microagents`
   - 类型: `bool`
   - 默认值: `true`
   - 描述: 是否使用 microagents

docs/i18n/zh-Hans/docusaurus-plugin-content-docs/current/usage/custom_sandbox_guide.md

@@ -58,11 +58,10 @@ docker build -t custom_image .
 [core]
 workspace_base="./workspace"
 run_as_openhands=true
-[sandbox]
-base_container_image="custom_image"
+sandbox_base_container_image="custom_image"
 ```
 
-对于 `base_container_image` 的值, 您可以选择以下任意一项：
+对于 `sandbox_base_container_image` 的值, 您可以选择以下任意一项：
 1. 在上一步中您构建的自定义镜像的名称（例如，`“custom_image”`）
 2. 从 Docker Hub 拉取的镜像（例如，`“node:20”`，如果你需要一个预装 `Node.js` 的沙箱环境）
 
@@ -84,17 +83,20 @@ base_container_image="custom_image"
 
 ### 错误：```useradd: UID 1000 is not unique```
 
-如果在控制台输出中看到此错误，说明 OpenHands 尝试在沙箱中以 UID 1000 创建 openhands 用户，但该 UID 已经被映像中的其他部分使用（不知何故）。要解决这个问题，请更改 config.toml 文件中的 user_id 字段为不同的值：
+如果在控制台输出中看到此错误，说明 OpenHands 尝试在沙箱中以 UID 1000 创建 openhands 用户，但该 UID 已经被映像中的其他部分使用（不知何故）。要解决这个问题，请更改 config.toml 文件中的 sandbox_user_id 字段为不同的值：
 
 ```
 [core]
 workspace_base="./workspace"
 run_as_openhands=true
-[sandbox]
-base_container_image="custom_image"
-user_id="1001"
+sandbox_base_container_image="custom_image"
+sandbox_user_id="1001"
 ```
 
 ### 端口使用错误
 
 如果您遇到端口被占用或不可用的错误提示，可以尝试先用`docker ps`命令列出所有运行中的 Docker 容器，然后使用`docker rm`命令删除相关容器，最后再重新执行```make run```命令。
+
+## 讨论
+
+对于其他问题或疑问，请加入 [Slack](https://join.slack.com/t/openhands-ai/shared_invite/zt-2wkh4pklz-w~h_DVDtEe9H5kyQlcNxVw) 或 [Discord](https://discord.gg/ESHStjSjD4) 提问！

docs/i18n/zh-Hans/docusaurus-plugin-content-docs/current/usage/how-to/cli-mode.md

@@ -50,7 +50,7 @@ LLM_API_KEY="sk_test_12345"
 ```bash
 docker run -it \
     --pull=always \
-    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.29-nikolaik \
+    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.19-nikolaik \
     -e SANDBOX_USER_ID=$(id -u) \
     -e WORKSPACE_MOUNT_PATH=$WORKSPACE_BASE \
     -e LLM_API_KEY=$LLM_API_KEY \
@@ -59,7 +59,7 @@ docker run -it \
     -v /var/run/docker.sock:/var/run/docker.sock \
     --add-host host.docker.internal:host-gateway \
     --name openhands-app-$(date +%Y%m%d%H%M%S) \
-    docker.all-hands.dev/all-hands-ai/openhands:0.29 \
+    docker.all-hands.dev/all-hands-ai/openhands:0.19 \
     python -m openhands.core.cli
 ```
 

docs/i18n/zh-Hans/docusaurus-plugin-content-docs/current/usage/how-to/custom-sandbox-guide.md

@@ -42,13 +42,12 @@ docker build -t custom-image .
 
 ### 指定基础沙箱镜像
 
-在 OpenHands 目录中的 `config.toml` 文件中，将 `base_container_image` 设置为你要使用的镜像。这可以是你已经拉取的镜像或你构建的镜像：
+在 OpenHands 目录中的 `config.toml` 文件中，将 `sandbox_base_container_image` 设置为你要使用的镜像。这可以是你已经拉取的镜像或你构建的镜像：
 
 ```bash
 [core]
 ...
-[sandbox]
-base_container_image="custom-image"
+sandbox_base_container_image="custom-image"
 ```
 
 ### 运行

docs/i18n/zh-Hans/docusaurus-plugin-content-docs/current/usage/how-to/evaluation-harness.md

@@ -112,7 +112,7 @@ OpenHands 的主要入口点在 `openhands/core/main.py` 中。以下是它的
    def get_config(instance: pd.Series, metadata: EvalMetadata) -> AppConfig:
        config = AppConfig(
            default_agent=metadata.agent_class,
-           runtime='docker',
+           runtime='eventstream',
            max_iterations=metadata.max_iterations,
            sandbox=SandboxConfig(
                base_container_image='your_container_image',

docs/i18n/zh-Hans/docusaurus-plugin-content-docs/current/usage/how-to/headless-mode.md

@@ -47,7 +47,7 @@ LLM_API_KEY="sk_test_12345"
 ```bash
 docker run -it \
     --pull=always \
-    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.29-nikolaik \
+    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.19-nikolaik \
     -e SANDBOX_USER_ID=$(id -u) \
     -e WORKSPACE_MOUNT_PATH=$WORKSPACE_BASE \
     -e LLM_API_KEY=$LLM_API_KEY \
@@ -57,6 +57,6 @@ docker run -it \
     -v /var/run/docker.sock:/var/run/docker.sock \
     --add-host host.docker.internal:host-gateway \
     --name openhands-app-$(date +%Y%m%d%H%M%S) \
-    docker.all-hands.dev/all-hands-ai/openhands:0.29 \
+    docker.all-hands.dev/all-hands-ai/openhands:0.19 \
     python -m openhands.core.main -t "write a bash script that prints hi" --no-auto-continue
 ```

docs/i18n/zh-Hans/docusaurus-plugin-content-docs/current/usage/installation.mdx

@@ -11,16 +11,16 @@
 在 Docker 中运行 OpenHands 是最简单的方式。
 
 ```bash
-docker pull docker.all-hands.dev/all-hands-ai/runtime:0.29-nikolaik
+docker pull docker.all-hands.dev/all-hands-ai/runtime:0.19-nikolaik
 
 docker run -it --rm --pull=always \
-    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.29-nikolaik \
+    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.19-nikolaik \
     -e LOG_ALL_EVENTS=true \
     -v /var/run/docker.sock:/var/run/docker.sock \
     -p 3000:3000 \
     --add-host host.docker.internal:host-gateway \
     --name openhands-app \
-    docker.all-hands.dev/all-hands-ai/openhands:0.29
+    docker.all-hands.dev/all-hands-ai/openhands:0.19
 ```
 
 你也可以在可脚本化的[无头模式](https://docs.all-hands.dev/modules/usage/how-to/headless-mode)下运行 OpenHands，作为[交互式 CLI](https://docs.all-hands.dev/modules/usage/how-to/cli-mode)，或使用 [OpenHands GitHub Action](https://docs.all-hands.dev/modules/usage/how-to/github-action)。

docs/i18n/zh-Hans/docusaurus-plugin-content-docs/current/usage/intro.mdx

@@ -42,7 +42,7 @@ OpenHands 是一个**自主 AI 软件工程师**，能够执行复杂的工程
   />
 </a>
 <br></br>
-<a href="https://join.slack.com/t/openhands-ai/shared_invite/zt-2ngejmfw6-9gW4APWOC9XUp1n~SiQ6iw">
+<a href="https://join.slack.com/t/openhands-ai/shared_invite/zt-2wkh4pklz-w~h_DVDtEe9H5kyQlcNxVw">
   <img
     src="https://img.shields.io/badge/Slack-Join%20Us-red?logo=slack&logoColor=white&style=for-the-badge"
     alt="Join our Slack community"

docs/i18n/zh-Hans/docusaurus-plugin-content-docs/current/usage/runtimes.md

@@ -11,7 +11,7 @@
 
 ```
 docker run # ...
-    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.29-nikolaik \
+    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.19-nikolaik \
     -v /var/run/docker.sock:/var/run/docker.sock \
     # ...
 ```

docs/modules/usage/architecture/runtime.md

@@ -1,6 +1,6 @@
-# 📦 Docker Runtime
+# 📦 EventStream Runtime
 
-The OpenHands Docker Runtime is the core component that enables secure and flexible execution of AI agent's action.
+The OpenHands EventStream Runtime is the core component that enables secure and flexible execution of AI agent's action.
 It creates a sandboxed environment using Docker, where arbitrary code can be run safely without risking the host system.
 
 ## Why do we need a sandboxed runtime?
@@ -54,13 +54,14 @@ graph TD
 6. Action Execution: The runtime client receives actions from the backend, executes them in the sandboxed environment, and sends back observations
 7. Observation Return: The action execution server sends execution results back to the OpenHands backend as observations
 
-The role of the client:
 
+The role of the client:
 - It acts as an intermediary between the OpenHands backend and the sandboxed environment
 - It executes various types of actions (shell commands, file operations, Python code, etc.) safely within the container
 - It manages the state of the sandboxed environment, including the current working directory and loaded plugins
 - It formats and returns observations to the backend, ensuring a consistent interface for processing results
 
+
 ## How OpenHands builds and maintains OH Runtime images
 
 OpenHands' approach to building and managing runtime images ensures efficiency, consistency, and flexibility in creating and maintaining Docker images for both production and development environments.
@@ -77,15 +78,16 @@ Tags may be in one of 2 formats:
 - **Source Tag**: `oh_v{openhands_version}_{16_digit_lock_hash}_{16_digit_source_hash}`
   (e.g.: `oh_v0.9.9_1234567890abcdef_1234567890abcdef`)
 
+
 #### Source Tag - Most Specific
 
 This is the first 16 digits of the MD5 of the directory hash for the source directory. This gives a hash
 for only the openhands source
 
+
 #### Lock Tag
 
 This hash is built from the first 16 digits of the MD5 of:
-
 - The name of the base image upon which the image was built (e.g.: `nikolaik/python-nodejs:python3.12-nodejs22`)
 - The content of the `pyproject.toml` included in the image.
 - The content of the `poetry.lock` included in the image.

docs/modules/usage/cloud/cloud-github-resolver.md

@@ -1,33 +0,0 @@
-# Cloud GitHub Resolver
-
-The GitHub Resolver automates code fixes and provides intelligent assistance for your repositories.
-
-## Setup
-
-The Cloud GitHub Resolver is available automatically when you
-[grant OpenHands Cloud repository access](./openhands-cloud.md#adding-repository-access).
-
-## Usage
-
-After granting OpenHands Cloud repository access, you can use the Cloud GitHub Resolver on the issues and pull requests
-on the repository.
-
-### Issues
-
-On your repository, label an issue with `openhands`. OpenHands will:
-1. Comment on the issue to let you know it is working on it.
-    - You can click on the link to track the progress on OpenHands Cloud.
-2. Open a pull request if it determines that the issue has been successfully resolved.
-3. Comment on the issue with a summary of the performed tasks and a link to the pull request.
-
-
-### Pull Requests
-
-To get OpenHands to work on pull requests, use `@openhands` in top level or inline comments to:
-     - Ask questions
-     - Request updates
-     - Get code explanations
-
-OpenHands will:
-1. Comment on the PR to let you know it is working on it.
-2. Perform the task.

docs/modules/usage/cloud/openhands-cloud.md

@@ -1,45 +0,0 @@
-# Openhands Cloud
-
-OpenHands Cloud is the cloud hosted version of OpenHands by All Hands AI.
-
-## Accessing OpenHands Cloud
-
-Currently, users are being admitted to access OpenHands Cloud in waves. To sign up,
-[join the waitlist](https://www.all-hands.dev/join-waitlist). Once you are approved, you will get an email with
-instructions on how to access it.
-
-## Getting Started
-
-After visiting OpenHands Cloud, you will be asked to connect with your GitHub account:
-1. After reading and accepting the terms of service, click `Connect to GitHub`.
-2. Review the permissions requested by OpenHands and then click `Authorize OpenHands AI`.
-   - OpenHands will require some permissions from your GitHub account. To read more about these permissions,
-     you can click the `Learn more` link on the GitHub authorize page.
-
-## Repository Access
-
-### Adding Repository Access
-
-You can grant OpenHands specific repository access:
-1. Click the `Select a GitHub project` dropdown, select `Add more repositories...`.
-2. Select the organization, then choose the specific repositories to grant OpenHands access to.
-   - Openhands requests short-lived tokens (8-hour expiry) with these permissions:
-     - Actions: Read and write
-     - Administration: Read-only
-     - Commit statuses: Read and write
-     - Contents: Read and write
-     - Issues: Read and write
-     - Metadata: Read-only
-     - Pull requests: Read and write
-     - Webhooks: Read and write
-     - Workflows: Read and write
-   - Repository access for a user is granted based on:
-     - Granted permission for the repository.
-     - User's GitHub permissions (owner/collaborator).
-3. Click on `Install & Authorize`.
-
-### Modifying Repository Access
-
-You can modify repository access at any time by:
-* Using the same `Select a GitHub project > Add more repositories` workflow, or
-* Visiting the Settings page and selecting `Configure GitHub Repositories` under the `GitHub Settings` section.

docs/modules/usage/configuration-options.md

@@ -7,11 +7,53 @@ If you are running in [GUI Mode](https://docs.all-hands.dev/modules/usage/how-to
 take precedence.
 :::
 
+---
+
+# Table of Contents
+
+- [Core Configuration](#core-configuration)
+   - [API Keys](#api-keys)
+   - [Workspace](#workspace)
+   - [Debugging and Logging](#debugging-and-logging)
+   - [Session Management](#session-management)
+   - [Trajectories](#trajectories)
+   - [File Store](#file-store)
+   - [Task Management](#task-management)
+   - [Sandbox Configuration](#sandbox-configuration)
+   - [Miscellaneous](#miscellaneous)
+- [LLM Configuration](#llm-configuration)
+   - [AWS Credentials](#aws-credentials)
+   - [API Configuration](#api-configuration)
+   - [Custom LLM Provider](#custom-llm-provider)
+   - [Embeddings](#embeddings)
+   - [Message Handling](#message-handling)
+   - [Model Selection](#model-selection)
+   - [Retrying](#retrying)
+   - [Advanced Options](#advanced-options)
+- [Agent Configuration](#agent-configuration)
+   - [Microagent Configuration](#microagent-configuration)
+   - [Memory Configuration](#memory-configuration)
+   - [LLM Configuration](#llm-configuration-2)
+   - [ActionSpace Configuration](#actionspace-configuration)
+   - [Microagent Usage](#microagent-usage)
+- [Sandbox Configuration](#sandbox-configuration)
+   - [Execution](#execution)
+   - [Container Image](#container-image)
+   - [Networking](#networking)
+   - [Linting and Plugins](#linting-and-plugins)
+   - [Dependencies and Environment](#dependencies-and-environment)
+   - [Evaluation](#evaluation)
+- [Security Configuration](#security-configuration)
+   - [Confirmation Mode](#confirmation-mode)
+   - [Security Analyzer](#security-analyzer)
+
+---
+
 ## Core Configuration
 
 The core configuration options are defined in the `[core]` section of the `config.toml` file.
 
-### API Keys
+**API Keys**
 - `e2b_api_key`
   - Type: `str`
   - Default: `""`
@@ -27,7 +69,7 @@ The core configuration options are defined in the `[core]` section of the `confi
   - Default: `""`
   - Description: API token secret for Modal
 
-### Workspace
+**Workspace**
 - `workspace_base`
   - Type: `str`
   - Default: `"./workspace"`
@@ -38,7 +80,7 @@ The core configuration options are defined in the `[core]` section of the `confi
   - Default: `"/tmp/cache"`
   - Description: Cache directory path
 
-### Debugging and Logging
+**Debugging and Logging**
 - `debug`
   - Type: `bool`
   - Default: `false`
@@ -49,18 +91,13 @@ The core configuration options are defined in the `[core]` section of the `confi
   - Default: `false`
   - Description: Disable color in terminal output
 
-### Trajectories
-- `save_trajectory_path`
+**Trajectories**
+- `trajectories_path`
   - Type: `str`
   - Default: `"./trajectories"`
   - Description: Path to store trajectories (can be a folder or a file). If it's a folder, the trajectories will be saved in a file named with the session id name and .json extension, in that folder.
 
-- `replay_trajectory_path`
-  - Type: `str`
-  - Default: `""`
-  - Description: Path to load a trajectory and replay. If given, must be a path to the trajectory file in JSON format. The actions in the trajectory file would be replayed first before any user instruction is executed.
-
-### File Store
+**File Store**
 - `file_store_path`
   - Type: `str`
   - Default: `"/tmp/file_store"`
@@ -91,7 +128,7 @@ The core configuration options are defined in the `[core]` section of the `confi
   - Default: `[".*"]`
   - Description: List of allowed file extensions for uploads
 
-### Task Management
+**Task Management**
 - `max_budget_per_task`
   - Type: `float`
   - Default: `0.0`
@@ -102,7 +139,7 @@ The core configuration options are defined in the `[core]` section of the `confi
   - Default: `100`
   - Description: Maximum number of iterations
 
-### Sandbox Configuration
+**Sandbox Configuration**
 - `workspace_mount_path_in_sandbox`
   - Type: `str`
   - Default: `"/workspace"`
@@ -118,7 +155,7 @@ The core configuration options are defined in the `[core]` section of the `confi
   - Default: `""`
   - Description: Path to rewrite the workspace mount path to. You can usually ignore this, it refers to special cases of running inside another container.
 
-### Miscellaneous
+**Miscellaneous**
 - `run_as_openhands`
   - Type: `bool`
   - Default: `true`
@@ -126,7 +163,7 @@ The core configuration options are defined in the `[core]` section of the `confi
 
 - `runtime`
   - Type: `str`
-  - Default: `"docker"`
+  - Default: `"eventstream"`
   - Description: Runtime environment
 
 - `default_agent`
@@ -145,10 +182,6 @@ The LLM (Large Language Model) configuration options are defined in the `[llm]`
 
 To use these with the docker command, pass in `-e LLM_<option>`. Example: `-e LLM_NUM_RETRIES`.
 
-:::note
-For development setups, you can also define custom named LLM configurations. See [Custom LLM Configurations](./llms/custom-llm-configs) for details.
-:::
-
 **AWS Credentials**
 - `aws_access_key_id`
   - Type: `str`
@@ -165,7 +198,7 @@ For development setups, you can also define custom named LLM configurations. See
   - Default: `""`
   - Description: AWS secret access key
 
-### API Configuration
+**API Configuration**
 - `api_key`
   - Type: `str`
   - Default: `None`
@@ -191,14 +224,29 @@ For development setups, you can also define custom named LLM configurations. See
   - Default: `0.0`
   - Description: Cost per output token
 
-### Custom LLM Provider
+**Custom LLM Provider**
 - `custom_llm_provider`
   - Type: `str`
   - Default: `""`
   - Description: Custom LLM provider
 
+**Embeddings**
+- `embedding_base_url`
+  - Type: `str`
+  - Default: `""`
+  - Description: Embedding API base URL
 
-### Message Handling
+- `embedding_deployment_name`
+  - Type: `str`
+  - Default: `""`
+  - Description: Embedding deployment name
+
+- `embedding_model`
+  - Type: `str`
+  - Default: `"local"`
+  - Description: Embedding model to use
+
+**Message Handling**
 - `max_message_chars`
   - Type: `int`
   - Default: `30000`
@@ -214,13 +262,13 @@ For development setups, you can also define custom named LLM configurations. See
   - Default: `0`
   - Description: Maximum number of output tokens
 
-### Model Selection
+**Model Selection**
 - `model`
   - Type: `str`
   - Default: `"claude-3-5-sonnet-20241022"`
   - Description: Model to use
 
-### Retrying
+**Retrying**
 - `num_retries`
   - Type: `int`
   - Default: `8`
@@ -241,7 +289,7 @@ For development setups, you can also define custom named LLM configurations. See
   - Default: `2.0`
   - Description: Multiplier for exponential backoff calculation
 
-### Advanced Options
+**Advanced Options**
 - `drop_params`
   - Type: `bool`
   - Default: `false`
@@ -281,13 +329,30 @@ For development setups, you can also define custom named LLM configurations. See
 
 The agent configuration options are defined in the `[agent]` and `[agent.<agent_name>]` sections of the `config.toml` file.
 
-### LLM Configuration
+**Microagent Configuration**
+- `micro_agent_name`
+  - Type: `str`
+  - Default: `""`
+  - Description: Name of the micro agent to use for this agent
+
+**Memory Configuration**
+- `memory_enabled`
+  - Type: `bool`
+  - Default: `false`
+  - Description: Whether long-term memory (embeddings) is enabled
+
+- `memory_max_threads`
+  - Type: `int`
+  - Default: `3`
+  - Description: The maximum number of threads indexing at the same time for embeddings
+
+**LLM Configuration**
 - `llm_config`
   - Type: `str`
   - Default: `'your-llm-config-group'`
   - Description: The name of the LLM config to use
 
-### ActionSpace Configuration
+**ActionSpace Configuration**
 - `function_calling`
   - Type: `bool`
   - Default: `true`
@@ -308,13 +373,8 @@ The agent configuration options are defined in the `[agent]` and `[agent.<agent_
   - Default: `false`
   - Description: Whether Jupyter is enabled in the action space
 
-- `enable_history_truncation`
-  - Type: `bool`
-  - Default: `true`
-  - Description: Whether history should be truncated to continue the session when hitting LLM context length limit
-
-### Microagent Usage
-- `enable_prompt_extensions`
+**Microagent Usage**
+- `use_microagents`
   - Type: `bool`
   - Default: `true`
   - Description: Whether to use microagents at all
@@ -330,7 +390,7 @@ The sandbox configuration options are defined in the `[sandbox]` section of the
 
 To use these with the docker command, pass in `-e SANDBOX_<option>`. Example: `-e SANDBOX_TIMEOUT`.
 
-### Execution
+**Execution**
 - `timeout`
   - Type: `int`
   - Default: `120`
@@ -341,24 +401,19 @@ To use these with the docker command, pass in `-e SANDBOX_<option>`. Example: `-
   - Default: `1000`
   - Description: Sandbox user ID
 
-### Container Image
+**Container Image**
 - `base_container_image`
   - Type: `str`
   - Default: `"nikolaik/python-nodejs:python3.12-nodejs22"`
   - Description: Container image to use for the sandbox
 
-### Networking
+**Networking**
 - `use_host_network`
   - Type: `bool`
   - Default: `false`
   - Description: Use host network
 
-- `runtime_binding_address`
-  - Type: `str`
-  - Default: `0.0.0.0`
-  - Description: The binding address for the runtime ports.  It specifies which network interface on the host machine Docker should bind the runtime ports to.
-
-### Linting and Plugins
+**Linting and Plugins**
 - `enable_auto_lint`
   - Type: `bool`
   - Default: `false`
@@ -369,7 +424,7 @@ To use these with the docker command, pass in `-e SANDBOX_<option>`. Example: `-
   - Default: `true`
   - Description: Whether to initialize plugins
 
-### Dependencies and Environment
+**Dependencies and Environment**
 - `runtime_extra_deps`
   - Type: `str`
   - Default: `""`
@@ -380,7 +435,7 @@ To use these with the docker command, pass in `-e SANDBOX_<option>`. Example: `-
   - Default: `{}`
   - Description: Environment variables to set at the launch of the runtime
 
-### Evaluation
+**Evaluation**
 - `browsergym_eval_env`
   - Type: `str`
   - Default: `""`
@@ -392,13 +447,13 @@ The security configuration options are defined in the `[security]` section of th
 
 To use these with the docker command, pass in `-e SECURITY_<option>`. Example: `-e SECURITY_CONFIRMATION_MODE`.
 
-### Confirmation Mode
+**Confirmation Mode**
 - `confirmation_mode`
   - Type: `bool`
   - Default: `false`
   - Description: Enable confirmation mode
 
-### Security Analyzer
+**Security Analyzer**
 - `security_analyzer`
   - Type: `str`
   - Default: `""`

docs/modules/usage/customization/repository.md

@@ -1,24 +0,0 @@
-# Repository Customization
-
-You can customize how OpenHands works with your repository by creating a
-`.openhands` directory at the root level.
-
-## Microagents
-You can use microagents to extend the OpenHands prompts with information
-about your project and how you want OpenHands to work. See
-[Repository Microagents](../prompting/microagents-repo) for more information.
-
-
-## Setup Script
-You can add `.openhands/setup.sh`, which will be run every time OpenHands begins
-working with your repository. This is a good place to install dependencies, set
-environment variables, etc.
-
-For example:
-```bash
-#!/bin/bash
-export MY_ENV_VAR="my value"
-sudo apt-get update
-sudo apt-get install -y lsof
-cd frontend && npm install ; cd ..
-```

docs/modules/usage/feedback.md

@@ -36,7 +36,7 @@ At this time, we will follow the following release process:
 1. All people who contributed public feedback will receive an email describing the data release and being given an opportunity to opt out.
 2. The person or people in charge of the data release will perform quality control of the data, removing low-quality feedback,
 removing email submitter email addresses, and attempting to remove any sensitive information.
-3. The data will be released publicly under the MIT license through commonly used sites such as GitHub or Hugging Face.
+3. The data will be released publicly under the MIT license through commonly used sites such as github or Hugging Face.
 
 ### What if I want my data deleted?
 

docs/modules/usage/getting-started.mdx

@@ -1,6 +1,6 @@
 # Getting Started with OpenHands
 
-So you've [run OpenHands](./installation) and have
+So you've [installed OpenHands](./installation) and have
 [set up your LLM](./installation#setup). Now what?
 
 OpenHands can help you tackle a wide variety of engineering tasks. But the technology

docs/modules/usage/how-to/cli-mode.md

@@ -35,7 +35,7 @@ To run OpenHands in CLI mode with Docker:
 ```bash
 docker run -it \
     --pull=always \
-    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.29-nikolaik \
+    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.19-nikolaik \
     -e SANDBOX_USER_ID=$(id -u) \
     -e WORKSPACE_MOUNT_PATH=$WORKSPACE_BASE \
     -e LLM_API_KEY=$LLM_API_KEY \
@@ -45,7 +45,7 @@ docker run -it \
     -v ~/.openhands-state:/.openhands-state \
     --add-host host.docker.internal:host-gateway \
     --name openhands-app-$(date +%Y%m%d%H%M%S) \
-    docker.all-hands.dev/all-hands-ai/openhands:0.29 \
+    docker.all-hands.dev/all-hands-ai/openhands:0.19 \
     python -m openhands.core.cli
 ```
 
@@ -58,7 +58,7 @@ Here are some examples of CLI commands and their expected outputs:
 ### Example 1: Simple Task
 
 ```bash
->> Write a Python script that prints "Hello, World!"
+How can I help? >> Write a Python script that prints "Hello, World!"
 ```
 
 Expected Output:
@@ -72,7 +72,7 @@ Expected Output:
 ### Example 2: Bash Command
 
 ```bash
->> Create a directory named "test_dir"
+How can I help? >> Create a directory named "test_dir"
 ```
 
 Expected Output:
@@ -86,7 +86,7 @@ Expected Output:
 ### Example 3: Error Handling
 
 ```bash
->> Delete a non-existent file
+How can I help? >> Delete a non-existent file
 ```
 
 Expected Output:

docs/modules/usage/how-to/custom-sandbox-guide.md

@@ -18,21 +18,15 @@ If you choose the first option, you can skip the `Create Your Docker Image` sect
 
 To create a custom Docker image, it must be Debian based.
 
-For example, if you want OpenHands to have `ruby` installed, you could create a `Dockerfile` with the following content:
+For example, if you want OpenHands to have `ruby` installed, create a `Dockerfile` with the following content:
 
 ```dockerfile
-FROM nikolaik/python-nodejs:python3.12-nodejs22
+FROM debian:latest
 
 # Install required packages
 RUN apt-get update && apt-get install -y ruby
 ```
 
-Or you could use a Ruby-specific base image:
-
-```dockerfile
-FROM ruby:latest
-```
-
 Save this file in a folder. Then, build your Docker image (e.g., named custom-image) by navigating to the folder in
 the terminal and running::
 ```bash
@@ -41,16 +35,8 @@ docker build -t custom-image .
 
 This will produce a new image called `custom-image`, which will be available in Docker.
 
-## Using the Docker Command
-
-When running OpenHands using [the docker command](/modules/usage/installation#start-the-app), replace
-`-e SANDBOX_RUNTIME_CONTAINER_IMAGE=...` with `-e SANDBOX_BASE_CONTAINER_IMAGE=<custom image name>`:
-
-```commandline
-docker run -it --rm --pull=always \
-    -e SANDBOX_BASE_CONTAINER_IMAGE=custom-image \
-    ...
-```
+> Note that in the configuration described in this document, OpenHands will run as user "openhands" inside the
+> sandbox and thus all packages installed via the docker file should be available to all users on the system, not just root.
 
 ## Using the Development Workflow
 
@@ -60,36 +46,13 @@ First, ensure you can run OpenHands by following the instructions in [Developmen
 
 ### Specify the Base Sandbox Image
 
-In the `config.toml` file within the OpenHands directory, set the `base_container_image` to the image you want to use.
+In the `config.toml` file within the OpenHands directory, set the `sandbox_base_container_image` to the image you want to use.
 This can be an image you’ve already pulled or one you’ve built:
 
 ```bash
 [core]
 ...
-[sandbox]
-base_container_image="custom-image"
-```
-
-### Additional Configuration Options
-
-The `config.toml` file supports several other options for customizing your sandbox:
-
-```toml
-[core]
-# Install additional dependencies when the runtime is built
-# Can contain any valid shell commands
-# If you need the path to the Python interpreter in any of these commands, you can use the $OH_INTERPRETER_PATH variable
-runtime_extra_deps = """
-pip install numpy pandas
-apt-get update && apt-get install -y ffmpeg
-"""
-
-# Set environment variables for the runtime
-# Useful for configuration that needs to be available at runtime
-runtime_startup_env_vars = { DATABASE_URL = "postgresql://user:pass@localhost/db" }
-
-# Specify platform for multi-architecture builds (e.g., "linux/amd64" or "linux/arm64")
-platform = "linux/amd64"
+sandbox_base_container_image="custom-image"
 ```
 
 ### Run

docs/modules/usage/how-to/development-overview.md

@@ -1,74 +0,0 @@
----
-sidebar_position: 9
----
-
-# Development Overview
-
-This guide provides an overview of the key documentation resources available in the OpenHands repository. Whether you're looking to contribute, understand the architecture, or work on specific components, these resources will help you navigate the codebase effectively.
-
-## Core Documentation
-
-### Project Fundamentals
-- **Main Project Overview** (`/README.md`)
-  The primary entry point for understanding OpenHands, including features and basic setup instructions.
-
-- **Development Guide** (`/Development.md`)
-  Comprehensive guide for developers working on OpenHands, including setup, requirements, and development workflows.
-
-- **Contributing Guidelines** (`/CONTRIBUTING.md`)
-  Essential information for contributors, covering code style, PR process, and contribution workflows.
-
-### Component Documentation
-
-#### Frontend
-- **Frontend Application** (`/frontend/README.md`)
-  Complete guide for setting up and developing the React-based frontend application.
-
-#### Backend
-- **Backend Implementation** (`/openhands/README.md`)
-  Detailed documentation of the Python backend implementation and architecture.
-
-- **Server Documentation** (`/openhands/server/README.md`)
-  Server implementation details, API documentation, and service architecture.
-
-- **Runtime Environment** (`/openhands/runtime/README.md`)
-  Documentation covering the runtime environment, execution model, and runtime configurations.
-
-#### Infrastructure
-- **Container Documentation** (`/containers/README.md`)
-  Comprehensive information about Docker containers, deployment strategies, and container management.
-
-### Testing and Evaluation
-- **Unit Testing Guide** (`/tests/unit/README.md`)
-  Instructions for writing, running, and maintaining unit tests.
-
-- **Evaluation Framework** (`/evaluation/README.md`)
-  Documentation for the evaluation framework, benchmarks, and performance testing.
-
-### Advanced Features
-- **Microagents Architecture** (`/microagents/README.md`)
-  Detailed information about the microagents architecture, implementation, and usage.
-
-### Documentation Standards
-- **Documentation Style Guide** (`/docs/DOC_STYLE_GUIDE.md`)
-  Standards and guidelines for writing and maintaining project documentation.
-
-## Getting Started with Development
-
-If you're new to developing with OpenHands, we recommend following this sequence:
-
-1. Start with the main `README.md` to understand the project's purpose and features
-2. Review the `CONTRIBUTING.md` guidelines if you plan to contribute
-3. Follow the setup instructions in `Development.md`
-4. Dive into specific component documentation based on your area of interest:
-   - Frontend developers should focus on `/frontend/README.md`
-   - Backend developers should start with `/openhands/README.md`
-   - Infrastructure work should begin with `/containers/README.md`
-
-## Documentation Updates
-
-When making changes to the codebase, please ensure that:
-1. Relevant documentation is updated to reflect your changes
-2. New features are documented in the appropriate README files
-3. Any API changes are reflected in the server documentation
-4. Documentation follows the style guide in `/docs/DOC_STYLE_GUIDE.md`

docs/modules/usage/how-to/evaluation-harness.md

@@ -112,7 +112,7 @@ To create an evaluation workflow for your benchmark, follow these steps:
    def get_config(instance: pd.Series, metadata: EvalMetadata) -> AppConfig:
        config = AppConfig(
            default_agent=metadata.agent_class,
-           runtime='docker',
+           runtime='eventstream',
            max_iterations=metadata.max_iterations,
            sandbox=SandboxConfig(
                base_container_image='your_container_image',

docs/modules/usage/how-to/github-action.md

@@ -39,13 +39,12 @@ You can provide custom directions for OpenHands by following the [README for the
 
 ### Custom configurations
 
-GitHub resolver will automatically check for valid [repository secrets](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions?tool=webui#creating-secrets-for-a-repository) or [repository variables](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/store-information-in-variables#creating-configuration-variables-for-a-repository) to customize its behavior.
+Github resolver will automatically check for valid [repository secrets](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions?tool=webui#creating-secrets-for-a-repository) or [repository variables](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/store-information-in-variables#creating-configuration-variables-for-a-repository) to customize its behavior.
 The customization options you can set are:
 
-| **Attribute name**               | **Type** | **Purpose**                                                                                         | **Example**                                        |
-| -------------------------------- | -------- | --------------------------------------------------------------------------------------------------- | -------------------------------------------------- |
-| `LLM_MODEL`                      | Variable | Set the LLM to use with OpenHands                                                                   | `LLM_MODEL="anthropic/claude-3-5-sonnet-20241022"` |
-| `OPENHANDS_MAX_ITER`             | Variable | Set max limit for agent iterations                                                                  | `OPENHANDS_MAX_ITER=10`                            |
-| `OPENHANDS_MACRO`                | Variable | Customize default macro for invoking the resolver                                                   | `OPENHANDS_MACRO=@resolveit`                       |
-| `OPENHANDS_BASE_CONTAINER_IMAGE` | Variable | Custom Sandbox ([learn more](https://docs.all-hands.dev/modules/usage/how-to/custom-sandbox-guide)) | `OPENHANDS_BASE_CONTAINER_IMAGE="custom_image"`    |
-| `TARGET_BRANCH`                  | Variable | Merge to branch other than `main`                                                                   | `TARGET_BRANCH="dev"`                              |
+| **Attribute name**               | **Type** | **Purpose**                                                                                                 | **Example**                                          |
+|----------------------------------| -------- |-------------------------------------------------------------------------------------------------------------|------------------------------------------------------|
+| `LLM_MODEL`                      | Variable | Set the LLM to use with OpenHands                                                                           | `LLM_MODEL="anthropic/claude-3-5-sonnet-20241022"`   |
+| `OPENHANDS_MAX_ITER`             | Variable | Set max limit for agent iterations                                                                          | `OPENHANDS_MAX_ITER=10`                              |
+| `OPENHANDS_MACRO`                | Variable | Customize default macro for invoking the resolver                                                           | `OPENHANDS_MACRO=@resolveit`                         |
+| `OPENHANDS_BASE_CONTAINER_IMAGE` | Variable | Custom Sandbox ([learn more](https://docs.all-hands.dev/modules/usage/how-to/custom-sandbox-guide))         | `OPENHANDS_BASE_CONTAINER_IMAGE="custom_image"`      |

docs/modules/usage/how-to/gui-mode.md

@@ -1,109 +1,117 @@
 # GUI Mode
 
-OpenHands provides a Graphical User Interface (GUI) mode for interacting with the AI assistant.
+## Introduction
+
+OpenHands provides a user-friendly Graphical User Interface (GUI) mode for interacting with the AI assistant.
+This mode offers an intuitive way to set up the environment, manage settings, and communicate with the AI.
 
 ## Installation and Setup
 
-1. Follow the installation instructions to install OpenHands.
+1. Follow the instructions in the [Installation](../installation) guide to install OpenHands.
 2. After running the command, access OpenHands at [http://localhost:3000](http://localhost:3000).
 
 ## Interacting with the GUI
 
 ### Initial Setup
 
-1. Upon first launch, you'll see a settings page.
-2. Select an `LLM Provider` and `LLM Model` from the dropdown menus. If the required model does not exist in the list,
-   toggle `Advanced` options and enter it with the correct prefix in the `Custom Model` text box.
+1. Upon first launch, you'll see a settings modal.
+2. Select an `LLM Provider` and `LLM Model` from the dropdown menus.
 3. Enter the corresponding `API Key` for your chosen provider.
-4. Click `Save Changes` to apply the settings.
+4. Click "Save" to apply the settings.
 
 ### GitHub Token Setup
 
 OpenHands automatically exports a `GITHUB_TOKEN` to the shell environment if it is available. This can happen in two ways:
 
-**Local Installation**: The user directly inputs their GitHub token.
-<details>
-  <summary>Setting Up a GitHub Token</summary>
+- **Locally (OSS)**: The user directly inputs their GitHub token.
+- **Online (SaaS)**: The token is obtained through GitHub OAuth authentication.
 
-  1. **Generate a Personal Access Token (PAT)**:
-   - On GitHub, go to Settings > Developer Settings > Personal Access Tokens > Tokens (classic).
-   - **New token (classic)**
-     - Required scopes:
+#### Setting Up a Local GitHub Token
+
+1. **Generate a Personal Access Token (PAT)**:
+   - Go to GitHub Settings > Developer Settings > Personal Access Tokens > Tokens (classic).
+   - Click "Generate new token (classic)".
+   - Required scopes:
      - `repo` (Full control of private repositories)
-   - **Fine-Grained Tokens**
-     - All Repositories (You can select specific repositories, but this will impact what returns in repo search)
-     - Minimal Permissions ( Select **Meta Data = Read-only** read for search, **Pull Requests = Read and Write**, **Content = Read and Write** for branch creation)
-  2. **Enter Token in OpenHands**:
-   - Click the Settings button (gear icon).
-   - Navigate to the `GitHub Settings` section.
-   - Paste your token in the `GitHub Token` field.
-   - Click `Save Changes` to apply the changes.
-</details>
+     - `workflow` (Update GitHub Action workflows)
+     - `read:org` (Read organization data)
 
-<details>
-  <summary>Organizational Token Policies</summary>
+2. **Enter Token in OpenHands**:
+   - Click the Settings button (gear icon) in the top right.
+   - Navigate to the "GitHub" section.
+   - Paste your token in the "GitHub Token" field.
+   - Click "Save" to apply the changes.
 
-  If you're working with organizational repositories, additional setup may be required:
+#### Organizational Token Policies
 
-  1. **Check Organization Requirements**:
+If you're working with organizational repositories, additional setup may be required:
+
+1. **Check Organization Requirements**:
    - Organization admins may enforce specific token policies.
    - Some organizations require tokens to be created with SSO enabled.
    - Review your organization's [token policy settings](https://docs.github.com/en/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization).
-  2. **Verify Organization Access**:
+
+2. **Verify Organization Access**:
    - Go to your token settings on GitHub.
-   - Look for the organization under `Organization access`.
-   - If required, click `Enable SSO` next to your organization.
+   - Look for the organization under "Organization access".
+   - If required, click "Enable SSO" next to your organization.
    - Complete the SSO authorization process.
-</details>
 
-<details>
-  <summary>Troubleshooting</summary>
+#### OAuth Authentication (Online Mode)
 
-  Common issues and solutions:
+When using OpenHands in online mode, the GitHub OAuth flow:
 
-  - **Token Not Recognized**:
-     - Ensure the token is properly saved in settings.
-     - Check that the token hasn't expired.
-     - Verify the token has the required scopes.
-     - Try regenerating the token.
-
-  - **Organization Access Denied**:
-     - Check if SSO is required but not enabled.
-     - Verify organization membership.
-     - Contact organization admin if token policies are blocking access.
-
-  - **Verifying Token Works**:
-     - The app will show a green checkmark if the token is valid.
-     - Try accessing a repository to confirm permissions.
-     - Check the browser console for any error messages.
-</details>
-
-**OpenHands Cloud**: The token is obtained through GitHub OAuth authentication.
-
-<details>
-  <summary>OAuth Authentication</summary>
-
-  When using OpenHands Cloud, the GitHub OAuth flow requests the following permissions:
+1. Requests the following permissions:
    - Repository access (read/write)
    - Workflow management
    - Organization read access
 
-  To authenticate OpenHands:
-   - Click `Sign in with GitHub` when prompted.
+2. Authentication steps:
+   - Click "Sign in with GitHub" when prompted.
    - Review the requested permissions.
    - Authorize OpenHands to access your GitHub account.
    - If using an organization, authorize organization access if prompted.
-</details>
+
+#### Troubleshooting
+
+Common issues and solutions:
+
+1. **Token Not Recognized**:
+   - Ensure the token is properly saved in settings.
+   - Check that the token hasn't expired.
+   - Verify the token has the required scopes.
+   - Try regenerating the token.
+
+2. **Organization Access Denied**:
+   - Check if SSO is required but not enabled.
+   - Verify organization membership.
+   - Contact organization admin if token policies are blocking access.
+
+3. **Verifying Token Works**:
+   - The app will show a green checkmark if the token is valid.
+   - Try accessing a repository to confirm permissions.
+   - Check the browser console for any error messages.
+   - Use the "Test Connection" button in settings if available.
 
 ### Advanced Settings
 
-1. Inside the Settings page, toggle `Advanced` options to access additional settings.
+1. Toggle `Advanced Options` to access additional settings.
 2. Use the `Custom Model` text box to manually enter a model if it's not in the list.
 3. Specify a `Base URL` if required by your LLM provider.
 
+### Main Interface
+
+The main interface consists of several key components:
+
+- **Chat Window**: The central area where you can view the conversation history with the AI assistant.
+- **Input Box**: Located at the bottom of the screen, use this to type your messages or commands to the AI.
+- **Send Button**: Click this to send your message to the AI.
+- **Settings Button**: A gear icon that opens the settings modal, allowing you to adjust your configuration at any time.
+- **Workspace Panel**: Displays the files and folders in your workspace, allowing you to navigate and view files, or the agent's past commands or web browsing history.
+
 ### Interacting with the AI
 
-1. Type your prompt in the input box.
+1. Type your question, request, or task description in the input box.
 2. Click the send button or press Enter to submit your message.
 3. The AI will process your input and provide a response in the chat window.
 4. You can continue the conversation by asking follow-up questions or providing additional information.

docs/modules/usage/how-to/headless-mode.md

@@ -32,7 +32,7 @@ To run OpenHands in Headless mode with Docker:
 ```bash
 docker run -it \
     --pull=always \
-    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.29-nikolaik \
+    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.19-nikolaik \
     -e SANDBOX_USER_ID=$(id -u) \
     -e WORKSPACE_MOUNT_PATH=$WORKSPACE_BASE \
     -e LLM_API_KEY=$LLM_API_KEY \
@@ -43,7 +43,7 @@ docker run -it \
     -v ~/.openhands-state:/.openhands-state \
     --add-host host.docker.internal:host-gateway \
     --name openhands-app-$(date +%Y%m%d%H%M%S) \
-    docker.all-hands.dev/all-hands-ai/openhands:0.29 \
+    docker.all-hands.dev/all-hands-ai/openhands:0.19 \
     python -m openhands.core.main -t "write a bash script that prints hi"
 ```
 

docs/modules/usage/how-to/persist-session-data.md

@@ -0,0 +1,16 @@
+# Persisting Session Data
+
+Using the standard Development Workflow, the session data is stored in memory. Currently, if OpenHands' service is restarted,
+previous sessions become invalid (a new secret is generated) and thus not recoverable.
+
+## How to Persist Session Data
+
+### Development Workflow
+In the `config.toml` file, specify the following:
+```
+[core]
+...
+file_store="local"
+file_store_path="/absolute/path/to/openhands/cache/directory"
+jwt_secret="secretpass"
+```

docs/modules/usage/installation.mdx

@@ -1,74 +1,27 @@
-# Running OpenHands
+# Installation
 
 ## System Requirements
 
-- MacOS with [Docker Desktop support](https://docs.docker.com/desktop/setup/install/mac-install/#system-requirements)
-- Linux
-- Windows with [WSL](https://learn.microsoft.com/en-us/windows/wsl/install) and [Docker Desktop support](https://docs.docker.com/desktop/setup/install/windows-install/#system-requirements)
+- Docker version 26.0.0+ or Docker Desktop 4.31.0+.
+- You must be using Linux or Mac OS.
+  - If you are on Windows, you must use [WSL](https://learn.microsoft.com/en-us/windows/wsl/install).
 
-A system with a modern processor and a minimum of **4GB RAM** is recommended to run OpenHands.
-
-## Prerequisites
-
-<details>
-  <summary>MacOS</summary>
-
-  **Docker Desktop**
-
-  1. [Install Docker Desktop on Mac](https://docs.docker.com/desktop/setup/install/mac-install).
-  2. Open Docker Desktop, go to `Settings > Advanced` and ensure `Allow the default Docker socket to be used` is enabled.
-</details>
-
-<details>
-  <summary>Linux</summary>
-
-  :::note
-  Tested with Ubuntu 22.04.
-  :::
-
-  **Docker Desktop**
-
-  1. [Install Docker Desktop on Linux](https://docs.docker.com/desktop/setup/install/linux/).
-
-</details>
-
-<details>
-  <summary>Windows</summary>
-
-  **WSL**
-
-  1. [Install WSL](https://learn.microsoft.com/en-us/windows/wsl/install).
-  2. Run `wsl --version` in powershell and confirm `Default Version: 2`.
-
-  **Docker Desktop**
-
-  1. [Install Docker Desktop on Windows](https://docs.docker.com/desktop/setup/install/windows-install).
-  2. Open Docker Desktop, go to `Settings` and confirm the following:
-  - General: `Use the WSL 2 based engine` is enabled.
-  - Resources > WSL Integration: `Enable integration with my default WSL distro` is enabled.
-
-  :::note
-  The docker command below to start the app must be run inside the WSL terminal.
-  :::
-
-</details>
-
-## Start the App
+## Start the app
 
 The easiest way to run OpenHands is in Docker.
 
 ```bash
-docker pull docker.all-hands.dev/all-hands-ai/runtime:0.29-nikolaik
+docker pull docker.all-hands.dev/all-hands-ai/runtime:0.19-nikolaik
 
 docker run -it --rm --pull=always \
-    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.29-nikolaik \
+    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.19-nikolaik \
     -e LOG_ALL_EVENTS=true \
     -v /var/run/docker.sock:/var/run/docker.sock \
     -v ~/.openhands-state:/.openhands-state \
     -p 3000:3000 \
     --add-host host.docker.internal:host-gateway \
     --name openhands-app \
-    docker.all-hands.dev/all-hands-ai/openhands:0.29
+    docker.all-hands.dev/all-hands-ai/openhands:0.19
 ```
 
 You'll find OpenHands running at http://localhost:3000!
@@ -76,26 +29,28 @@ You'll find OpenHands running at http://localhost:3000!
 You can also [connect OpenHands to your local filesystem](https://docs.all-hands.dev/modules/usage/runtimes#connecting-to-your-filesystem),
 run OpenHands in a scriptable [headless mode](https://docs.all-hands.dev/modules/usage/how-to/headless-mode),
 interact with it via a [friendly CLI](https://docs.all-hands.dev/modules/usage/how-to/cli-mode),
-or run it on tagged issues with [a GitHub action](https://docs.all-hands.dev/modules/usage/how-to/github-action).
+or run it on tagged issues with [a github action](https://docs.all-hands.dev/modules/usage/how-to/github-action).
 
 ## Setup
 
-Upon launching OpenHands, you'll see a Settings page. You **must** select an `LLM Provider` and `LLM Model` and enter a corresponding `API Key`.
+Upon launching OpenHands, you'll see a settings modal. You **must** select an `LLM Provider` and `LLM Model` and enter a corresponding `API Key`.
 These can be changed at any time by selecting the `Settings` button (gear icon) in the UI.
 
-If the required model does not exist in the list, you can toggle `Advanced` options and manually enter it with the correct prefix
+If the required `LLM Model` does not exist in the list, you can toggle `Advanced Options` and manually enter it with the correct prefix
 in the `Custom Model` text box.
-The `Advanced` options also allow you to specify a `Base URL` if required.
+The `Advanced Options` also allow you to specify a `Base URL` if required.
 
-Now you're ready to [get started with OpenHands](./getting-started).
+<div style={{ display: 'flex', justifyContent: 'center', gap: '20px' }}>
+  <img src="/img/settings-screenshot.png" alt="settings-modal" width="340" />
+  <img src="/img/settings-advanced.png" alt="settings-modal" width="335" />
+</div>
 
 ## Versions
 
-The [docker command above](./installation#start-the-app) pulls the most recent stable release of OpenHands. You have other options as well:
-- For a specific release, replace $VERSION in `openhands:$VERSION` and `runtime:$VERSION`, with the version number.
-We use SemVer so `0.9` will automatically point to the latest `0.9.x` release, and `0` will point to the latest `0.x.x` release.
-- For the most up-to-date development version, replace $VERSION in `openhands:$VERSION` and `runtime:$VERSION`, with `main`.
-This version is unstable and is recommended for testing or development purposes only.
+The command above pulls the most recent stable release of OpenHands. You have other options as well:
+- For a specific release, use `docker.all-hands.dev/all-hands-ai/openhands:$VERSION`, replacing $VERSION with the version number.
+- We use semver, and release major, minor, and patch tags. So `0.9` will automatically point to the latest `0.9.x` release, and `0` will point to the latest `0.x.x` release.
+- For the most up-to-date development version, you can use `docker.all-hands.dev/all-hands-ai/openhands:main`. This version is unstable and is recommended for testing or development purposes only.
 
 You can choose the tag that best suits your needs based on stability requirements and desired features.
 

docs/modules/usage/key-features.md

@@ -1,60 +0,0 @@
-
-# OpenHands Feature Overview
-
-![overview](https://www.all-hands.dev/assets/product/product-slide-1.webp)
-
-## 1. Workspace
-The Workspace feature provides a comprehensive development environment with the following key capabilities:
-- File Explorer: Browse, view, and manage project files and directories
-- Project Management: Import, create, and navigate between different projects
-- Integrated Development Tools: Seamless integration with various development workflows
-- File Operations:
-  * View file contents
-  * Create new files and folders
-  * Upload and download files
-  * Basic file manipulation
-
-## 2. Jupyter Notebook
-The Jupyter Notebook feature offers an interactive coding and data analysis environment:
-- Interactive Code Cells: Execute Python code in a cell-based interface
-- Input and Output Tracking: Maintain a history of code inputs and their corresponding outputs
-- Persistent Session: Preserve code execution context between cells
-- Supports various Python operations and data analysis tasks
-- Real-time code execution and result visualization
-
-## 3. Browser (Beta)
-The Browser feature provides web interaction capabilities:
-- Web Page Navigation: Open and browse websites within the application
-- Screenshot Capture: Automatically generate screenshots of web pages
-- Interaction Tools:
-  * Click elements
-  * Fill out forms
-  * Scroll pages
-  * Navigate through web content
-- Supports 15 different browser interaction functions
-
-## 4. Terminal
-The Terminal feature offers a command-line interface within the application:
-- Execute Shell Commands: Run bash and system commands
-- Command History: Track and recall previous commands
-- Environment Interaction: Interact directly with the system's command line
-- Support for various programming and system administration tasks
-
-## 5. Chat / AI Conversation
-The Chat interface provides an AI-powered conversational experience:
-- Interactive AI Assistant: Engage in natural language conversations
-- Context-Aware Responses: AI understands and responds to development-related queries
-- Action Suggestions: Provides actionable recommendations for tasks
-- Conversation Management: Create, delete, and manage different conversation threads
-
-## 6. App (Beta)
-The main application interface combines all these features:
-- Integrated Workspace: Seamless integration of workspace, browser, terminal, and AI chat
-- Configurable Layout: Customize the arrangement of different feature panels
-- State Management: Maintain context and state across different features
-- Security and Privacy Controls: Manage application settings and permissions
-
-### Additional Notes
-- The application is currently in beta, with ongoing improvements and feature additions
-- Supports various development workflows and AI-assisted coding
-- Designed to enhance developer productivity through integrated tools and AI assistance

docs/modules/usage/llms/azure-llms.md

@@ -5,7 +5,7 @@ OpenHands uses LiteLLM to make calls to Azure's chat models. You can find their
 ## Azure OpenAI Configuration
 
 When running OpenHands, you'll need to set the following environment variable using `-e` in the
-[docker run command](../installation#running-openhands):
+[docker run command](/modules/usage/installation#start-the-app):
 
 ```
 LLM_API_VERSION="<api-version>"              # e.g. "2023-05-15"
@@ -25,17 +25,23 @@ You will need your ChatGPT deployment name which can be found on the deployments
 &lt;deployment-name&gt; below.
 :::
 
-1. Enable `Advanced` options
+1. Enable `Advanced Options`
 2. Set the following:
    - `Custom Model` to azure/&lt;deployment-name&gt;
    - `Base URL` to your Azure API Base URL (e.g. `https://example-endpoint.openai.azure.com`)
    - `API Key` to your Azure API key
 
+## Embeddings
+
+OpenHands uses llama-index for embeddings. You can find their documentation on Azure [here](https://docs.llamaindex.ai/en/stable/api_reference/embeddings/azure_openai/).
+
 ### Azure OpenAI Configuration
 
-When running OpenHands, set the following environment variable using `-e` in the
-[docker run command](../installation#running-openhands):
+When running OpenHands, set the following environment variables using `-e` in the
+[docker run command](/modules/usage/installation#start-the-app):
 
 ```
+LLM_EMBEDDING_MODEL="azureopenai"
+LLM_EMBEDDING_DEPLOYMENT_NAME="<your-embedding-deployment-name>"   # e.g. "TextEmbedding...<etc>"
 LLM_API_VERSION="<api-version>"                                    # e.g. "2024-02-15-preview"
 ```

docs/modules/usage/llms/custom-llm-configs.md

@@ -1,136 +0,0 @@
-# Custom LLM Configurations
-
-OpenHands supports defining multiple named LLM configurations in your `config.toml` file. This feature allows you to use different LLM configurations for different purposes, such as using a cheaper model for tasks that don't require high-quality responses, or using different models with different parameters for specific agents.
-
-## How It Works
-
-Named LLM configurations are defined in the `config.toml` file using sections that start with `llm.`. For example:
-
-```toml
-# Default LLM configuration
-[llm]
-model = "gpt-4"
-api_key = "your-api-key"
-temperature = 0.0
-
-# Custom LLM configuration for a cheaper model
-[llm.gpt3]
-model = "gpt-3.5-turbo"
-api_key = "your-api-key"
-temperature = 0.2
-
-# Another custom configuration with different parameters
-[llm.high-creativity]
-model = "gpt-4"
-api_key = "your-api-key"
-temperature = 0.8
-top_p = 0.9
-```
-
-Each named configuration inherits all settings from the default `[llm]` section and can override any of those settings. You can define as many custom configurations as needed.
-
-## Using Custom Configurations
-
-### With Agents
-
-You can specify which LLM configuration an agent should use by setting the `llm_config` parameter in the agent's configuration section:
-
-```toml
-[agent.RepoExplorerAgent]
-# Use the cheaper GPT-3 configuration for this agent
-llm_config = 'gpt3'
-
-[agent.CodeWriterAgent]
-# Use the high creativity configuration for this agent
-llm_config = 'high-creativity'
-```
-
-### Configuration Options
-
-Each named LLM configuration supports all the same options as the default LLM configuration. These include:
-
-- Model selection (`model`)
-- API configuration (`api_key`, `base_url`, etc.)
-- Model parameters (`temperature`, `top_p`, etc.)
-- Retry settings (`num_retries`, `retry_multiplier`, etc.)
-- Token limits (`max_input_tokens`, `max_output_tokens`)
-- And all other LLM configuration options
-
-For a complete list of available options, see the LLM Configuration section in the [Configuration Options](../configuration-options) documentation.
-
-## Use Cases
-
-Custom LLM configurations are particularly useful in several scenarios:
-
-- **Cost Optimization**: Use cheaper models for tasks that don't require high-quality responses, like repository exploration or simple file operations.
-- **Task-Specific Tuning**: Configure different temperature and top_p values for tasks that require different levels of creativity or determinism.
-- **Different Providers**: Use different LLM providers or API endpoints for different tasks.
-- **Testing and Development**: Easily switch between different model configurations during development and testing.
-
-## Example: Cost Optimization
-
-A practical example of using custom LLM configurations to optimize costs:
-
-```toml
-# Default configuration using GPT-4 for high-quality responses
-[llm]
-model = "gpt-4"
-api_key = "your-api-key"
-temperature = 0.0
-
-# Cheaper configuration for repository exploration
-[llm.repo-explorer]
-model = "gpt-3.5-turbo"
-temperature = 0.2
-
-# Configuration for code generation
-[llm.code-gen]
-model = "gpt-4"
-temperature = 0.0
-max_output_tokens = 2000
-
-[agent.RepoExplorerAgent]
-llm_config = 'repo-explorer'
-
-[agent.CodeWriterAgent]
-llm_config = 'code-gen'
-```
-
-In this example:
-- Repository exploration uses a cheaper model since it mainly involves understanding and navigating code
-- Code generation uses GPT-4 with a higher token limit for generating larger code blocks
-- The default configuration remains available for other tasks
-
-# Custom Configurations with Reserved Names
-
-OpenHands can use custom LLM configurations named with reserved names, for specific use cases. If you specify the model and other settings under the reserved names, then OpenHands will load and them for a specific purpose. As of now, one such configuration is implemented: draft editor.
-
-## Draft Editor Configuration
-
-The `draft_editor` configuration is a group of settings you can provide, to specify the model to use for preliminary drafting of code edits, for any tasks that involve editing and refining code. You need to provide it under the section `[llm.draft_editor]`.
-
-For example, you can define in `config.toml` a draft editor like this:
-
-```toml
-[llm.draft_editor]
-model = "gpt-4"
-temperature = 0.2
-top_p = 0.95
-presence_penalty = 0.0
-frequency_penalty = 0.0
-```
-
-This configuration:
-- Uses GPT-4 for high-quality edits and suggestions
-- Sets a low temperature (0.2) to maintain consistency while allowing some flexibility
-- Uses a high top_p value (0.95) to consider a wide range of token options
-- Disables presence and frequency penalties to maintain focus on the specific edits needed
-
-Use this configuration when you want to let an LLM draft edits before making them. In general, it may be useful to:
-- Review and suggest code improvements
-- Refine existing content while maintaining its core meaning
-- Make precise, focused changes to code or text
-
-:::note
-Custom LLM configurations are only available when using OpenHands in development mode, via `main.py` or `cli.py`. When running via `docker run`, please use the standard configuration options.
-:::

docs/modules/usage/llms/google-llms.md

@@ -10,13 +10,13 @@ OpenHands uses LiteLLM to make calls to Google's chat models. You can find their
 When running OpenHands, you'll need to set the following in the OpenHands UI through the Settings:
 - `LLM Provider` to `Gemini`
 - `LLM Model` to the model you will be using.
-If the model is not in the list, toggle `Advanced` options, and enter it in `Custom Model` (e.g. gemini/<model-name> like `gemini/gemini-2.0-flash`).
+If the model is not in the list, toggle `Advanced Options`, and enter it in `Custom Model` (e.g. gemini/<model-name> like `gemini/gemini-1.5-pro`).
 - `API Key` to your Gemini API key
 
 ## VertexAI - Google Cloud Platform Configs
 
 To use Vertex AI through Google Cloud Platform when running OpenHands, you'll need to set the following environment
-variables using `-e` in the [docker run command](../installation#running-openhands):
+variables using `-e` in the [docker run command](/modules/usage/installation#start-the-app):
 
 ```
 GOOGLE_APPLICATION_CREDENTIALS="<json-dump-of-gcp-service-account-json>"
@@ -27,4 +27,4 @@ VERTEXAI_LOCATION="<your-gcp-location>"
 Then set the following in the OpenHands UI through the Settings:
 - `LLM Provider` to `VertexAI`
 - `LLM Model` to the model you will be using.
-If the model is not in the list, toggle `Advanced` options, and enter it in `Custom Model` (e.g. vertex_ai/&lt;model-name&gt;).
+If the model is not in the list, toggle `Advanced Options`, and enter it in `Custom Model` (e.g. vertex_ai/&lt;model-name&gt;).

docs/modules/usage/llms/groq.md

@@ -8,7 +8,7 @@ When running OpenHands, you'll need to set the following in the OpenHands UI thr
 - `LLM Provider` to `Groq`
 - `LLM Model` to the model you will be using. [Visit here to see the list of
 models that Groq hosts](https://console.groq.com/docs/models). If the model is not in the list, toggle
-`Advanced` options, and enter it in `Custom Model` (e.g. groq/<model-name> like `groq/llama3-70b-8192`).
+`Advanced Options`, and enter it in `Custom Model` (e.g. groq/<model-name> like `groq/llama3-70b-8192`).
 - `API key` to your Groq API key. To find or create your Groq API Key, [see here](https://console.groq.com/keys).
 
 
@@ -17,7 +17,7 @@ models that Groq hosts](https://console.groq.com/docs/models). If the model is n
 
 The Groq endpoint for chat completion is [mostly OpenAI-compatible](https://console.groq.com/docs/openai). Therefore, you can access Groq models as you
 would access any OpenAI-compatible endpoint. In the OpenHands UI through the Settings:
-1. Enable `Advanced` options
+1. Enable `Advanced Options`
 2. Set the following:
    - `Custom Model` to the prefix `openai/` + the model you will be using (e.g. `openai/llama3-70b-8192`)
    - `Base URL` to `https://api.groq.com/openai/v1`

docs/modules/usage/llms/litellm-proxy.md

@@ -8,7 +8,7 @@ To use LiteLLM proxy with OpenHands, you need to:
 
 1. Set up a LiteLLM proxy server (see [LiteLLM documentation](https://docs.litellm.ai/docs/proxy/quick_start))
 2. When running OpenHands, you'll need to set the following in the OpenHands UI through the Settings:
-  * Enable `Advanced` options
+  * Enable `Advanced Options`
   * `Custom Model` to the prefix `litellm_proxy/` + the model you will be using (e.g. `litellm_proxy/anthropic.claude-3-5-sonnet-20241022-v2:0`)
   * `Base URL` to your LiteLLM proxy URL (e.g. `https://your-litellm-proxy.com`)
   * `API Key` to your LiteLLM proxy API key

docs/modules/usage/llms/llms.md

@@ -5,14 +5,23 @@ OpenHands can connect to any LLM supported by LiteLLM. However, it requires a po
 ## Model Recommendations
 
 Based on our evaluations of language models for coding tasks (using the SWE-bench dataset), we can provide some
-recommendations for model selection. Our latest benchmarking results can be found in [this spreadsheet](https://docs.google.com/spreadsheets/d/1wOUdFCMyY6Nt0AIqF705KN4JKOWgeI4wUGUP60krXXs/edit?gid=0).
+recommendations for model selection. Some analyses can be found in [this blog article comparing LLMs](https://www.all-hands.dev/blog/evaluation-of-llms-as-coding-agents-on-swe-bench-at-30x-speed) and
+[this blog article with some more recent results](https://www.all-hands.dev/blog/openhands-codeact-21-an-open-state-of-the-art-software-development-agent).
+
+When choosing a model, consider both the quality of outputs and the associated costs. Here's a summary of the findings:
+
+- Claude 3.5 Sonnet is the best by a fair amount, achieving a 53% resolve rate on SWE-Bench Verified with the default agent in OpenHands.
+- GPT-4o lags behind, and o1-mini actually performed somewhat worse than GPT-4o. We went in and analyzed the results a little, and briefly it seemed like o1 was sometimes "overthinking" things, performing extra environment configuration tasks when it could just go ahead and finish the task.
+- Finally, the strongest open models were Llama 3.1 405 B and deepseek-v2.5, and they performed reasonably, even besting some of the closed models.
+
+Please refer to the [full article](https://www.all-hands.dev/blog/evaluation-of-llms-as-coding-agents-on-swe-bench-at-30x-speed) for more details.
 
 Based on these findings and community feedback, the following models have been verified to work reasonably well with OpenHands:
 
-- anthropic/claude-3-5-sonnet-20241022 (recommended)
-- anthropic/claude-3-5-haiku-20241022
-- deepseek/deepseek-chat
-- gpt-4o
+- claude-3-5-sonnet (recommended)
+- gpt-4 / gpt-4o
+- llama-3.1-405b
+- deepseek-v2.5
 
 :::warning
 OpenHands will issue many prompts to the LLM you configure. Most of these LLMs cost money, so be sure to set spending
@@ -38,10 +47,10 @@ The following can be set in the OpenHands UI through the Settings:
 - `LLM Provider`
 - `LLM Model`
 - `API Key`
-- `Base URL` (through `Advanced` settings)
+- `Base URL` (through `Advanced Settings`)
 
 There are some settings that may be necessary for some LLMs/providers that cannot be set through the UI. Instead, these
-can be set through environment variables passed to the docker run command when starting the app
+can be set through environment variables passed to the [docker run command](/modules/usage/installation#start-the-app)
 using `-e`:
 
 - `LLM_API_VERSION`
@@ -63,22 +72,22 @@ We have a few guides for running OpenHands with specific model providers:
 ### API retries and rate limits
 
 LLM providers typically have rate limits, sometimes very low, and may require retries. OpenHands will automatically
-retry requests if it receives a Rate Limit Error (429 error code).
+retry requests if it receives a Rate Limit Error (429 error code), API connection error, or other transient errors.
 
 You can customize these options as you need for the provider you're using. Check their documentation, and set the
 following environment variables to control the number of retries and the time between retries:
 
-- `LLM_NUM_RETRIES` (Default of 4 times)
-- `LLM_RETRY_MIN_WAIT` (Default of 5 seconds)
-- `LLM_RETRY_MAX_WAIT` (Default of 30 seconds)
+- `LLM_NUM_RETRIES` (Default of 8)
+- `LLM_RETRY_MIN_WAIT` (Default of 15 seconds)
+- `LLM_RETRY_MAX_WAIT` (Default of 120 seconds)
 - `LLM_RETRY_MULTIPLIER` (Default of 2)
 
 If you are running OpenHands in development mode, you can also set these options in the `config.toml` file:
 
 ```toml
 [llm]
-num_retries = 4
-retry_min_wait = 5
-retry_max_wait = 30
+num_retries = 8
+retry_min_wait = 15
+retry_max_wait = 120
 retry_multiplier = 2
 ```

docs/modules/usage/llms/openai-llms.md

@@ -8,7 +8,7 @@ When running OpenHands, you'll need to set the following in the OpenHands UI thr
 * `LLM Provider` to `OpenAI`
 * `LLM Model` to the model you will be using.
 [Visit here to see a full list of OpenAI models that LiteLLM supports.](https://docs.litellm.ai/docs/providers/openai#openai-chat-completion-models)
-If the model is not in the list, toggle `Advanced` options, and enter it in `Custom Model` (e.g. openai/<model-name> like `openai/gpt-4o`).
+If the model is not in the list, toggle `Advanced Options`, and enter it in `Custom Model` (e.g. openai/<model-name> like `openai/gpt-4o`).
 * `API Key` to your OpenAI API key. To find or create your OpenAI Project API Key, [see here](https://platform.openai.com/api-keys).
 
 ## Using OpenAI-Compatible Endpoints
@@ -18,7 +18,7 @@ Just as for OpenAI Chat completions, we use LiteLLM for OpenAI-compatible endpoi
 ## Using an OpenAI Proxy
 
 If you're using an OpenAI proxy, in the OpenHands UI through the Settings:
-1. Enable `Advanced` options
+1. Enable `Advanced Options`
 2. Set the following:
    - `Custom Model` to openai/<model-name> (e.g. `openai/gpt-4o` or openai/<proxy-prefix>/<model-name>)
    - `Base URL` to the URL of your OpenAI proxy

docs/modules/usage/llms/openrouter.md

@@ -8,5 +8,5 @@ When running OpenHands, you'll need to set the following in the OpenHands UI thr
 * `LLM Provider` to `OpenRouter`
 * `LLM Model` to the model you will be using.
 [Visit here to see a full list of OpenRouter models](https://openrouter.ai/models).
-If the model is not in the list, toggle `Advanced` options, and enter it in `Custom Model` (e.g. openrouter/<model-name> like `openrouter/anthropic/claude-3.5-sonnet`).
+If the model is not in the list, toggle `Advanced Options`, and enter it in `Custom Model` (e.g. openrouter/<model-name> like `openrouter/anthropic/claude-3.5-sonnet`).
 * `API Key` to your OpenRouter API key.

docs/modules/usage/prompting/microagents-overview.md

@@ -1,36 +0,0 @@
-# Microagents Overview
-
-Microagents are specialized prompts that enhance OpenHands with domain-specific knowledge, repository-specific context
-and task-specific workflows. They help by providing expert guidance, automating common tasks, and ensuring
-consistent practices across projects.
-
-## Microagent Types
-
-Currently OpenHands supports the following types of microagents:
-
-* [Repository Microagents](./microagents-repo): Repository-specific context and guidelines for OpenHands.
-* [Public Microagents](./microagents-public): General guidelines triggered by keywords for all OpenHands users.
-
-When OpenHands works with a repository, it:
-
-1. Loads repository-specific instructions from `.openhands/microagents/` if present in the repository.
-2. Loads general guidelines triggered by keywords in conversations.
-See current [Public Microagents](https://github.com/All-Hands-AI/OpenHands/tree/main/microagents/knowledge).
-
-## Microagent Format
-
-All microagents use markdown files with YAML frontmatter that have special instructions to help OpenHands accomplish
-tasks:
-```
----
-name: <Name of the microagent>
-type: <MicroAgent type>
-version: <MicroAgent version>
-agent: <The agent type (Typically CodeActAgent)>
-triggers:
-- <Optional keywords triggering the microagent. If triggers are removed, it will always be included>
----
-
-<Markdown with any special guidelines, instructions, and prompts that OpenHands should follow.
-Check out the specific documentation for each microagent on best practices for more information.>
-```

docs/modules/usage/prompting/microagents-public.md

@@ -1,21 +1,31 @@
-# Public Microagents
+# Public Micro-Agents
+
+OpenHands uses specialized micro-agents to handle specific tasks and contexts efficiently. These micro-agents are small,
+focused components that provide specialized behavior and knowledge for particular scenarios.
 
 ## Overview
 
-Public microagents are specialized guidelines triggered by keywords for all OpenHands users.
-They are defined in markdown files under the
+Public micro-agents are defined in markdown files under the
 [`microagents/knowledge/`](https://github.com/All-Hands-AI/OpenHands/tree/main/microagents/knowledge) directory.
+Each micro-agent is configured with:
 
-Public microagents:
+- A unique name.
+- The agent type (typically CodeActAgent).
+- Trigger keywords that activate the agent.
+- Specific instructions and capabilities.
+
+### Integration
+
+Public micro-agents are automatically integrated into OpenHands' workflow. They:
 - Monitor incoming commands for their trigger words.
 - Activate when relevant triggers are detected.
 - Apply their specialized knowledge and capabilities.
 - Follow their specific guidelines and restrictions.
 
-## Current Public Microagents
+## Available Public Micro-Agents
 
-For more information about specific microagents, refer to their individual documentation files in
-the [`microagents/knowledge/`](https://github.com/All-Hands-AI/OpenHands/tree/main/microagents/knowledge/) directory.
+For more information about specific micro-agents, refer to their individual documentation files in
+the [`micro-agents`](https://github.com/All-Hands-AI/OpenHands/tree/main/microagents) directory.
 
 ### GitHub Agent
 **File**: `github.md`
@@ -56,54 +66,105 @@ Usage Example:
 yes | npm install package-name
 ```
 
-## Contributing a Public Microagent
+### Custom Public Micro-Agents
 
-You can create your own public microagents by adding new markdown files to the
-[`microagents/knowledge/`](https://github.com/All-Hands-AI/OpenHands/tree/main/microagents/knowledge/) directory.
+You can create your own public micro-agents by adding new markdown files to the `microagents/knowledge/` directory.
+Each file should follow this structure:
 
-### Public Microagents Best Practices
+```markdown
+---
+name: agent_name
+agent: CodeActAgent
+triggers:
+- trigger_word1
+- trigger_word2
+---
 
-- **Clear Scope**: Keep the microagent focused on a specific domain or task.
+Instructions and capabilities for the micro-agent...
+```
+
+## Working With Public Micro-Agents
+
+When working with public micro-agents:
+- **Use Appropriate Triggers**: Ensure your commands include the relevant trigger words to activate the correct micro-agent.
+- **Follow Agent Guidelines**: Each agent has specific instructions and limitations. Respect these for optimal results.
+- **API-First Approach**: When available, use API endpoints rather than web interfaces.
+- **Automation Friendly**: Design commands that work well in non-interactive environments.
+
+## Contributing a Public Micro-Agent
+
+Best practices for creating public micro-agents:
+
+- **Clear Scope**: Keep the micro-agent focused on a specific domain or task.
 - **Explicit Instructions**: Provide clear, unambiguous guidelines.
 - **Useful Examples**: Include practical examples of common use cases.
 - **Safety First**: Include necessary warnings and constraints.
-- **Integration Awareness**: Consider how the microagent interacts with other components.
+- **Integration Awareness**: Consider how the micro-agent interacts with other components.
 
-### Steps to Contribute a Public Microagent
+To contribute a new micro-agent to OpenHands:
 
-#### 1. Plan the Public Microagent
+### 1. Plan the Public Micro-Agent
 
-Before creating a public microagent, consider:
+Before creating a public micro-agent, consider:
 - What specific problem or use case will it address?
 - What unique capabilities or knowledge should it have?
 - What trigger words make sense for activating it?
 - What constraints or guidelines should it follow?
 
-#### 2. Create File
+### 2. File Structure
 
-Create a new markdown file in [`microagents/knowledge/`](https://github.com/All-Hands-AI/OpenHands/tree/main/microagents/knowledge/)
-with a descriptive name (e.g., `docker.md` for a Docker-focused agent).
+Create a new markdown file in `microagents/knowledge/` with a descriptive name (e.g., `docker.md` for a Docker-focused agent).
 
-Update the file with the required frontmatter [according to the required format](./microagents-overview#microagent-format)
-and the required specialized guidelines while following the [best practices above](#public-microagents-best-practices).
+### 3. Required Components
 
-#### 3. Testing the Public Microagent
+The micro-agent file must include:
 
+- **Front Matter**: YAML metadata at the start of the file:
+```markdown
+---
+name: your_agent_name
+agent: CodeActAgent
+triggers:
+- trigger_word1
+- trigger_word2
+---
+```
+
+- **Instructions**: Clear, specific guidelines for the agent's behavior:
+```markdown
+You are responsible for [specific task/domain].
+
+Key responsibilities:
+1. [Responsibility 1]
+2. [Responsibility 2]
+
+Guidelines:
+- [Guideline 1]
+- [Guideline 2]
+
+Examples of usage:
+[Example 1]
+[Example 2]
+```
+
+### 4. Testing the Public Micro-Agent
+
+Before submitting:
 - Test the agent with various prompts.
 - Verify trigger words activate the agent correctly.
 - Ensure instructions are clear and comprehensive.
 - Check for potential conflicts with existing agents.
 
-#### 4. Submission Process
+### 5. Submission Process
 
 Submit a pull request with:
-- The new microagent file.
+- The new micro-agent file.
 - Updated documentation if needed.
 - Description of the agent's purpose and capabilities.
 
-### Example Public Microagent Implementation
+### Example Public Micro-Agent Implementation
 
-Here's a template for a new microagent:
+Here's a template for a new micro-agent:
 
 ```markdown
 ---
@@ -149,5 +210,5 @@ Remember to:
 - Optimize for build time and image size
 ```
 
-See the [current public micro-agents](https://github.com/All-Hands-AI/OpenHands/tree/main/microagents/knowledge) for
-more examples.
+Remember that micro-agents are a powerful way to extend OpenHands' capabilities in specific domains. Well-designed
+agents can significantly improve the system's ability to handle specialized tasks.

docs/modules/usage/prompting/microagents-repo.md

@@ -1,51 +1,25 @@
-# Repository Microagents
-
-## Overview
+# Repository Micro-Agents
 
 OpenHands can be customized to work more effectively with specific repositories by providing repository-specific context
 and guidelines. This section explains how to optimize OpenHands for your project.
 
-## Creating a Repository Micro-Agent
+## Repository Configuration
 
 You can customize OpenHands' behavior for your repository by creating a `.openhands/microagents/` directory in your repository's root.
-At minimum it should contain the file
+At minimum, it should contain the file
 `.openhands/microagents/repo.md`, which includes instructions that will
 be given to the agent every time it works with this repository.
 
-### Repository Microagents Best Practices
-
-- **Keep Instructions Updated**: Regularly update your `.openhands/microagents/` directory as your project evolves.
-- **Be Specific**: Include specific paths, patterns, and requirements unique to your project.
-- **Document Dependencies**: List all tools and dependencies required for development.
-- **Include Examples**: Provide examples of good code patterns from your project.
-- **Specify Conventions**: Document naming conventions, file organization, and code style preferences.
-
-### Steps to Create a Repository Microagent
-
-#### 1. Plan the Repository Microagent
-When creating a repository-specific micro-agent, we suggest including the following information:
+We suggest including the following information:
 - **Repository Overview**: A brief description of your project's purpose and architecture.
 - **Directory Structure**: Key directories and their purposes.
 - **Development Guidelines**: Project-specific coding standards and practices.
 - **Testing Requirements**: How to run tests and what types of tests are required.
 - **Setup Instructions**: Steps needed to build and run the project.
 
-#### 2. Create File
-
-Create a file in your repository under `.openhands/microagents/` (Example: `.openhands/microagents/repo.md`)
-
-Update the file with the required frontmatter [according to the required format](./microagents-overview#microagent-format)
-and the required specialized guidelines for your repository.
-
-### Example Repository Microagent
-
+### Example Repository Configuration
+Example `.openhands/microagents/repo.md` file:
 ```
----
-name: repo
-type: repo
-agent: CodeActAgent
----
-
 Repository: MyProject
 Description: A web application for task management
 
@@ -63,6 +37,30 @@ Guidelines:
 - Follow ESLint configuration
 - Write tests for all new features
 - Use TypeScript for new code
-
-If adding a new component in src/components, always add appropriate unit tests in tests/components/.
 ```
+
+### Customizing Prompts
+
+You may also add customized prompts to the `.openhands/microagents/repo.md` file when working with a repository.
+These could:
+
+- **Reference Project Standards**: Mention specific coding standards or patterns used in your project.
+- **Include Context**: Reference relevant documentation or existing implementations.
+- **Specify Testing Requirements**: Include project-specific testing requirements in your prompts.
+
+Example customized prompt:
+```
+Add a new task completion feature to src/components/TaskList.tsx following our existing component patterns.
+Include unit tests in tests/components/ and update the documentation in docs/features/.
+The component should use our shared styling from src/styles/components.
+```
+
+### Best Practices for Repository Customization
+
+- **Keep Instructions Updated**: Regularly update your `.openhands/microagents/` directory as your project evolves.
+- **Be Specific**: Include specific paths, patterns, and requirements unique to your project.
+- **Document Dependencies**: List all tools and dependencies required for development.
+- **Include Examples**: Provide examples of good code patterns from your project.
+- **Specify Conventions**: Document naming conventions, file organization, and code style preferences.
+
+By customizing OpenHands for your repository, you'll get more accurate and consistent results that align with your project's standards and requirements.

docs/modules/usage/runtimes-index.md

@@ -1,24 +0,0 @@
-# Runtime Configuration
-
-A Runtime is an environment where the OpenHands agent can edit files and run
-commands.
-
-By default, OpenHands uses a Docker-based runtime, running on your local computer.
-This means you only have to pay for the LLM you're using, and your code is only ever sent to the LLM.
-
-We also support "remote" runtimes, which are typically managed by third-parties.
-They can make setup a bit simpler and more scalable, especially
-if you're running many OpenHands conversations in parallel (e.g. to do evaluation).
-
-Additionally, we provide a "local" runtime that runs directly on your machine without Docker,
-which can be useful in controlled environments like CI pipelines.
-
-## Available Runtimes
-
-OpenHands supports several different runtime environments:
-
-- [Docker Runtime](./runtimes/docker.md) - The default runtime that uses Docker containers for isolation (recommended for most users)
-- [OpenHands Remote Runtime](./runtimes/remote.md) - Cloud-based runtime for parallel execution (beta)
-- [Modal Runtime](./runtimes/modal.md) - Runtime provided by our partners at Modal
-- [Daytona Runtime](./runtimes/daytona.md) - Runtime provided by Daytona
-- [Local Runtime](./runtimes/local.md) - Direct execution on your local machine without Docker

docs/modules/usage/runtimes.md

@@ -1,8 +1,86 @@
----
-title: Runtime Configuration
-slug: /usage/runtimes
----
+# Runtime Configuration
 
-import { Redirect } from '@docusaurus/router';
+A Runtime is an environment where the OpenHands agent can edit files and run
+commands.
 
-<Redirect to="/modules/usage/runtimes-index" />
+By default, OpenHands uses a Docker-based runtime, running on your local computer.
+This means you only have to pay for the LLM you're using, and your code is only ever sent to the LLM.
+
+We also support "remote" runtimes, which are typically managed by third-parties.
+They can make setup a bit simpler and more scalable, especially
+if you're running many OpenHands conversations in parallel (e.g. to do evaluation).
+
+## Docker Runtime
+This is the default Runtime that's used when you start OpenHands. You might notice
+some flags being passed to `docker run` that make this possible:
+
+```
+docker run # ...
+    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.19-nikolaik \
+    -v /var/run/docker.sock:/var/run/docker.sock \
+    # ...
+```
+
+The `SANDBOX_RUNTIME_CONTAINER_IMAGE` from nikolaik is a pre-built runtime image
+that contains our Runtime server, as well as some basic utilities for Python and NodeJS.
+You can also [build your own runtime image](how-to/custom-sandbox-guide).
+
+### Connecting to Your filesystem
+One useful feature here is the ability to connect to your local filesystem. To mount your filesystem into the runtime:
+1. Set `WORKSPACE_BASE`:
+
+    ```bash
+    export WORKSPACE_BASE=/path/to/your/code
+
+    # Linux and Mac Example
+    # export WORKSPACE_BASE=$HOME/OpenHands
+    # Will set $WORKSPACE_BASE to /home/<username>/OpenHands
+    #
+    # WSL on Windows Example
+    # export WORKSPACE_BASE=/mnt/c/dev/OpenHands
+    # Will set $WORKSPACE_BASE to C:\dev\OpenHands
+    ```
+2. Add the following options to the `docker run` command:
+
+    ```bash
+    docker run # ...
+        -e SANDBOX_USER_ID=$(id -u) \
+        -e WORKSPACE_MOUNT_PATH=$WORKSPACE_BASE \
+        -v $WORKSPACE_BASE:/opt/workspace_base \
+        # ...
+    ```
+
+Be careful! There's nothing stopping the OpenHands agent from deleting or modifying
+any files that are mounted into its workspace.
+
+This setup can cause some issues with file permissions (hence the `SANDBOX_USER_ID` variable)
+but seems to work well on most systems.
+
+## All Hands Runtime
+The All Hands Runtime is currently in beta. You can request access by joining
+the #remote-runtime-limited-beta channel on Slack ([see the README](https://github.com/All-Hands-AI/OpenHands?tab=readme-ov-file#-how-to-join-the-community) for an invite).
+
+To use the All Hands Runtime, set the following environment variables when
+starting OpenHands:
+
+```bash
+docker run # ...
+    -e RUNTIME=remote \
+    -e SANDBOX_REMOTE_RUNTIME_API_URL="https://runtime.app.all-hands.dev" \
+    -e SANDBOX_API_KEY="your-all-hands-api-key" \
+    -e SANDBOX_KEEP_RUNTIME_ALIVE="true" \
+    # ...
+```
+
+## Modal Runtime
+Our partners at [Modal](https://modal.com/) have also provided a runtime for OpenHands.
+
+To use the Modal Runtime, create an account, and then [create an API key.](https://modal.com/settings)
+
+You'll then need to set the following environment variables when starting OpenHands:
+```bash
+docker run # ...
+    -e RUNTIME=modal \
+    -e MODAL_API_TOKEN_ID="your-id" \
+    -e MODAL_API_TOKEN_SECRET="your-secret" \
+```

docs/modules/usage/runtimes/daytona.md

@@ -1,32 +0,0 @@
-# Daytona Runtime
-
-You can use [Daytona](https://www.daytona.io/) as a runtime provider:
-
-## Step 1: Retrieve Your Daytona API Key
-1. Visit the [Daytona Dashboard](https://app.daytona.io/dashboard/keys).
-2. Click **"Create Key"**.
-3. Enter a name for your key and confirm the creation.
-4. Once the key is generated, copy it.
-
-## Step 2: Set Your API Key as an Environment Variable
-Run the following command in your terminal, replacing `<your-api-key>` with the actual key you copied:
-```bash
-export DAYTONA_API_KEY="<your-api-key>"
-```
-
-This step ensures that OpenHands can authenticate with the Daytona platform when it runs.
-
-## Step 3: Run OpenHands Locally Using Docker
-To start the latest version of OpenHands on your machine, execute the following command in your terminal:
-```bash
-bash -i <(curl -sL https://get.daytona.io/openhands)
-```
-
-### What This Command Does:
-- Downloads the latest OpenHands release script.
-- Runs the script in an interactive Bash session.
-- Automatically pulls and runs the OpenHands container using Docker.
-
-Once executed, OpenHands should be running locally and ready for use.
-
-For more details and manual initialization, view the entire [README.md](https://github.com/All-Hands-AI/OpenHands/blob/main/openhands/runtime/impl/daytona/README.md)

docs/modules/usage/runtimes/docker.md

@@ -1,88 +0,0 @@
-# Docker Runtime
-
-This is the default Runtime that's used when you start OpenHands.
-
-## Image
-The `SANDBOX_RUNTIME_CONTAINER_IMAGE` from nikolaik is a pre-built runtime image
-that contains our Runtime server, as well as some basic utilities for Python and NodeJS.
-You can also [build your own runtime image](../how-to/custom-sandbox-guide).
-
-## Connecting to Your filesystem
-One useful feature here is the ability to connect to your local filesystem. To mount your filesystem into the runtime:
-1. Set `WORKSPACE_BASE`:
-
-    ```bash
-    export WORKSPACE_BASE=/path/to/your/code
-
-    # Linux and Mac Example
-    # export WORKSPACE_BASE=$HOME/OpenHands
-    # Will set $WORKSPACE_BASE to /home/<username>/OpenHands
-    #
-    # WSL on Windows Example
-    # export WORKSPACE_BASE=/mnt/c/dev/OpenHands
-    # Will set $WORKSPACE_BASE to C:\dev\OpenHands
-    ```
-2. Add the following options to the `docker run` command:
-
-    ```bash
-    docker run # ...
-        -e SANDBOX_USER_ID=$(id -u) \
-        -e WORKSPACE_MOUNT_PATH=$WORKSPACE_BASE \
-        -v $WORKSPACE_BASE:/opt/workspace_base \
-        # ...
-    ```
-
-Be careful! There's nothing stopping the OpenHands agent from deleting or modifying
-any files that are mounted into its workspace.
-
-This setup can cause some issues with file permissions (hence the `SANDBOX_USER_ID` variable)
-but seems to work well on most systems.
-
-## Hardened Docker Installation
-
-When deploying OpenHands in environments where security is a priority, you should consider implementing a hardened Docker configuration. This section provides recommendations for securing your OpenHands Docker deployment beyond the default configuration.
-
-### Security Considerations
-
-The default Docker configuration in the README is designed for ease of use on a local development machine. If you're running on a public network (e.g. airport WiFi),
-you should implement additional security measures.
-
-### Network Binding Security
-
-By default, OpenHands binds to all network interfaces (`0.0.0.0`), which can expose your instance to all networks the host is connected to. For a more secure setup:
-
-1. **Restrict Network Binding**:
-
-   Use the `runtime_binding_address` configuration to restrict which network interfaces OpenHands listens on:
-
-   ```bash
-   docker run # ...
-       -e SANDBOX_RUNTIME_BINDING_ADDRESS=127.0.0.1 \
-       # ...
-   ```
-
-   This configuration ensures OpenHands only listens on the loopback interface (`127.0.0.1`), making it accessible only from the local machine.
-
-2. **Secure Port Binding**:
-
-   Modify the `-p` flag to bind only to localhost instead of all interfaces:
-
-   ```bash
-   docker run # ... \
-       -p 127.0.0.1:3000:3000 \
-   ```
-
-   This ensures that the OpenHands web interface is only accessible from the local machine, not from other machines on the network.
-
-### Network Isolation
-
-Use Docker's network features to isolate OpenHands:
-
-```bash
-# Create an isolated network
-docker network create openhands-network
-
-# Run OpenHands in the isolated network
-docker run # ... \
-    --network openhands-network \
-```

docs/modules/usage/runtimes/local.md

@@ -1,62 +0,0 @@
-# Local Runtime
-
-The Local Runtime allows the OpenHands agent to execute actions directly on your local machine without using Docker. This runtime is primarily intended for controlled environments like CI pipelines or testing scenarios where Docker is not available.
-
-:::caution
-**Security Warning**: The Local Runtime runs without any sandbox isolation. The agent can directly access and modify files on your machine. Only use this runtime in controlled environments or when you fully understand the security implications.
-:::
-
-## Prerequisites
-
-Before using the Local Runtime, ensure that:
-
-1. You have followed the [Development setup instructions](https://github.com/All-Hands-AI/OpenHands/blob/main/Development.md).
-2. tmux is available on your system.
-
-## Configuration
-
-To use the Local Runtime, besides required configurations like the model, API key, you'll need to set the following options via environment variables or the [config.toml file](https://github.com/All-Hands-AI/OpenHands/blob/main/config.template.toml) when starting OpenHands:
-
-- Via environment variables:
-
-```bash
-# Required
-export RUNTIME=local
-
-# Optional but recommended
-export WORKSPACE_BASE=/path/to/your/workspace
-```
-
-- Via `config.toml`:
-
-```toml
-[core]
-runtime = "local"
-workspace_base = "/path/to/your/workspace"
-```
-
-If `WORKSPACE_BASE` is not set, the runtime will create a temporary directory for the agent to work in.
-
-## Example Usage
-
-Here's an example of how to start OpenHands with the Local Runtime in Headless Mode:
-
-```bash
-# Set the runtime type to local
-export RUNTIME=local
-
-# Optionally set a workspace directory
-export WORKSPACE_BASE=/path/to/your/project
-
-# Start OpenHands
-poetry run python -m openhands.core.main -t "write a bash script that prints hi"
-```
-
-## Use Cases
-
-The Local Runtime is particularly useful for:
-
-- CI/CD pipelines where Docker is not available.
-- Testing and development of OpenHands itself.
-- Environments where container usage is restricted.
-- Scenarios where direct file system access is required.

docs/modules/usage/runtimes/modal.md

@@ -1,13 +0,0 @@
-# Modal Runtime
-
-Our partners at [Modal](https://modal.com/) have provided a runtime for OpenHands.
-
-To use the Modal Runtime, create an account, and then [create an API key.](https://modal.com/settings)
-
-You'll then need to set the following environment variables when starting OpenHands:
-```bash
-docker run # ...
-    -e RUNTIME=modal \
-    -e MODAL_API_TOKEN_ID="your-id" \
-    -e MODAL_API_TOKEN_SECRET="your-secret" \
-```

docs/modules/usage/runtimes/remote.md

@@ -1,6 +0,0 @@
-# OpenHands Remote Runtime
-
-OpenHands Remote Runtime is currently in beta (read [here](https://runtime.all-hands.dev/) for more details), it allows you to launch runtimes in parallel in the cloud.
-Fill out [this form](https://docs.google.com/forms/d/e/1FAIpQLSckVz_JFwg2_mOxNZjCtr7aoBFI2Mwdan3f75J_TrdMS1JV2g/viewform) to apply if you want to try this out!
-
-NOTE: This runtime is specifically designed for agent evaluation purposes only through [OpenHands evaluation harness](https://github.com/All-Hands-AI/OpenHands/tree/main/evaluation). It should not be used to launch production OpenHands applications.

docs/package.json

@@ -22,16 +22,16 @@
     "@mdx-js/react": "^3.1.0",
     "clsx": "^2.0.0",
     "prism-react-renderer": "^2.4.1",
-    "react": "^19.0.0",
-    "react-dom": "^19.0.0",
-    "react-icons": "^5.5.0",
+    "react": "^18.3.1",
+    "react-dom": "^18.3.1",
+    "react-icons": "^5.4.0",
     "react-use": "^17.6.0"
   },
   "devDependencies": {
     "@docusaurus/module-type-aliases": "^3.5.1",
     "@docusaurus/tsconfig": "^3.7.0",
     "@docusaurus/types": "^3.5.1",
-    "typescript": "~5.8.2"
+    "typescript": "~5.7.2"
   },
   "browserslist": {
     "production": [

docs/sidebars.ts

@@ -5,7 +5,7 @@ const sidebars: SidebarsConfig = {
   docsSidebar: [
     {
       type: 'doc',
-      label: 'Running OpenHands',
+      label: 'Installation',
       id: 'usage/installation',
     },
     {
@@ -13,11 +13,6 @@ const sidebars: SidebarsConfig = {
       label: 'Getting Started',
       id: 'usage/getting-started',
     },
-    {
-      type: 'doc',
-      label: 'Key Features',
-      id: 'usage/key-features',
-    },
     {
       type: 'category',
       label: 'Prompting',
@@ -29,36 +24,20 @@ const sidebars: SidebarsConfig = {
         },
         {
           type: 'category',
-          label: 'Microagents',
+          label: 'Micro-Agents',
           items: [
             {
               type: 'doc',
-              label: 'Overview',
-              id: 'usage/prompting/microagents-overview',
+              label: 'Public',
+              id: 'usage/prompting/microagents-public',
             },
             {
               type: 'doc',
               label: 'Repository',
               id: 'usage/prompting/microagents-repo',
             },
-            {
-              type: 'doc',
-              label: 'Public',
-              id: 'usage/prompting/microagents-public',
-            },
           ],
-        },
-      ],
-    },
-    {
-      type: 'category',
-      label: 'Customization',
-      items: [
-        {
-          type: 'doc',
-          label: 'Repository Customization',
-          id: 'usage/customization/repository',
-        },
+        }
       ],
     },
     {
@@ -82,26 +61,9 @@ const sidebars: SidebarsConfig = {
         },
         {
           type: 'doc',
-          label: 'Github Action',
+          label: 'Github Actions',
           id: 'usage/how-to/github-action',
         },
-        {
-          type: 'category',
-          label: 'Cloud',
-          items: [
-            {
-              type: 'doc',
-              label: 'Openhands Cloud',
-              id: 'usage/cloud/openhands-cloud',
-            },
-
-            {
-              type: 'doc',
-              label: 'Cloud GitHub Resolver',
-              id: 'usage/cloud/cloud-github-resolver',
-            },
-          ],
-        },
       ],
     },
     {
@@ -156,40 +118,9 @@ const sidebars: SidebarsConfig = {
           ],
         },
         {
-          type: 'category',
+          type: 'doc',
           label: 'Runtime Configuration',
-          items: [
-            {
-              type: 'doc',
-              label: 'Overview',
-              id: 'usage/runtimes-index',
-            },
-            {
-              type: 'doc',
-              label: 'Docker Runtime',
-              id: 'usage/runtimes/docker',
-            },
-            {
-              type: 'doc',
-              label: 'Remote Runtime',
-              id: 'usage/runtimes/remote',
-            },
-            {
-              type: 'doc',
-              label: 'Modal Runtime',
-              id: 'usage/runtimes/modal',
-            },
-            {
-              type: 'doc',
-              label: 'Daytona Runtime',
-              id: 'usage/runtimes/daytona',
-            },
-            {
-              type: 'doc',
-              label: 'Local Runtime',
-              id: 'usage/runtimes/local',
-            },
-          ],
+          id: 'usage/runtimes',
         },
         {
           type: 'doc',
@@ -201,6 +132,11 @@ const sidebars: SidebarsConfig = {
           label: 'Custom Sandbox',
           id: 'usage/how-to/custom-sandbox-guide',
         },
+        {
+          type: 'doc',
+          label: 'Persist Session Data',
+          id: 'usage/how-to/persist-session-data',
+        },
       ],
     },
     {
@@ -217,11 +153,6 @@ const sidebars: SidebarsConfig = {
       type: 'category',
       label: 'For OpenHands Developers',
       items: [
-        {
-          type: 'doc',
-          label: 'Development Overview',
-          id: 'usage/how-to/development-overview',
-        },
         {
           type: 'category',
           label: 'Architecture',
@@ -254,7 +185,7 @@ const sidebars: SidebarsConfig = {
       type: 'doc',
       label: 'About',
       id: 'usage/about',
-    },
+    }
   ],
 };
 

docs/src/components/CustomFooter.tsx

@@ -8,7 +8,7 @@ function CustomFooter() {
     <footer className="custom-footer">
       <div className="footer-content">
         <div className="footer-icons">
-          <a href="https://join.slack.com/t/openhands-ai/shared_invite/zt-2ngejmfw6-9gW4APWOC9XUp1n~SiQ6iw" target="_blank" rel="noopener noreferrer">
+          <a href="https://join.slack.com/t/openhands-ai/shared_invite/zt-2wkh4pklz-w~h_DVDtEe9H5kyQlcNxVw" target="_blank" rel="noopener noreferrer">
             <FaSlack />
           </a>
           <a href="https://discord.gg/ESHStjSjD4" target="_blank" rel="noopener noreferrer">

docs/src/components/Demo/Demo.tsx

@@ -5,6 +5,9 @@ export function Demo() {
   const videoRef = React.useRef<HTMLVideoElement>(null);
 
   return (
+    <div
+      style={{ paddingBottom: "10px", paddingTop: "10px", textAlign: "center" }}
+    >
       <video
         playsInline
         autoPlay={true}
@@ -17,5 +20,6 @@ export function Demo() {
       >
         <source src="img/teaser.mp4" type="video/mp4"></source>
       </video>
+    </div>
   );
 }