Merge main into fix/sonnet-4-5-bedrock-normalization; resolve conflicts and keep Sonnet 4.5 reasoning_effort suppression (dash and dot variants)\n\nCo-authored-by: openhands <openhands@all-hands.dev>

2025-12-26 05:48:36 +08:00 · 2025-10-21 11:07:07 +00:00 · 2025-10-21 11:07:07 +00:00 · c433da0570
commit c433da0570
parent c3dba9bb95 44578664ed
484 changed files with 32242 additions and 13486 deletions
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@ -1,12 +1,31 @@
- [ ] 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
+## Summary of PR

-**End-user friendly description of the problem this fixes or functionality this introduces.**
+<!-- Summarize what the PR does, explaining any non-trivial design decisions. -->

+## Change Type

---
-**Summarize what the PR does, explaining any non-trivial design decisions.**
+<!-- Choose the types that apply to your PR and remove the rest. -->

+- [ ] Bug fix
+- [ ] New feature
+- [ ] Breaking change
+- [ ] Refactor
+- [ ] Other (dependency update, docs, typo fixes, etc.)

---
-**Link of any specific issues this addresses:**
+## Checklist
+
+- [ ] I have read and reviewed the code and I understand what the code is doing.
+- [ ] I have tested the code to the best of my ability and ensured it works as expected.
+
+## Fixes
+
+<!-- If this resolves an issue, link it here so it will close automatically upon merge. -->
+
+Resolves #(issue)
+
+## Release Notes
+
+<!-- Check the box if this change is worth adding to the release notes. If checked, you must provide an
+end-user friendly description for your change below the checkbox. -->
+
+- [ ] Include this change in the Release Notes.
--- a/.github/workflows/cli-build-binary-and-optionally-release.yml
+++ b/.github/workflows/cli-build-binary-and-optionally-release.yml
@ -0,0 +1,114 @@
+# Workflow that builds and tests the CLI binary executable
+name: CLI - Build binary and optionally release
+
+# Run on pushes to main branch and CLI tags, and on pull requests when CLI files change
+on:
+  push:
+    branches:
+      - main
+    tags:
+      - "*-cli"
+  pull_request:
+    paths:
+      - "openhands-cli/**"
+
+permissions:
+  contents: write       # needed to create releases or upload assets
+
+# Cancel previous runs if a new commit is pushed
+concurrency:
+  group: ${{ github.workflow }}-${{ (github.head_ref && github.ref) || github.run_id }}
+  cancel-in-progress: true
+
+jobs:
+  build-binary:
+    name: Build binary executable
+    strategy:
+      matrix:
+        include:
+          # Build on Ubuntu 22.04 for maximum GLIBC compatibility (GLIBC 2.31)
+          - os: ubuntu-22.04
+            platform: linux
+            artifact_name: openhands-cli-linux
+          # Build on macOS for macOS users
+          - os: macos-15
+            platform: macos
+            artifact_name: openhands-cli-macos
+    runs-on: ${{ matrix.os }}
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: 3.12
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v3
+        with:
+          version: "latest"
+
+      - name: Install dependencies
+        working-directory: openhands-cli
+        run: |
+          uv sync
+
+      - name: Build binary executable
+        working-directory: openhands-cli
+        run: |
+          ./build.sh --install-pyinstaller | tee output.log
+          echo "Full output:"
+          cat output.log
+
+          if grep -q "❌" output.log; then
+            echo "❌ Found failure marker in output"
+            exit 1
+          fi
+
+          echo "✅ Build & test finished without ❌ markers"
+
+      - name: Upload binary artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: ${{ matrix.artifact_name }}
+          path: openhands-cli/dist/openhands*
+          retention-days: 30
+
+  create-github-release:
+    name: Create GitHub Release
+    runs-on: ubuntu-latest
+    needs: build-binary
+    if: startsWith(github.ref, 'refs/tags/')
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Download all artifacts
+        uses: actions/download-artifact@v4
+        with:
+          path: artifacts
+
+      - name: Prepare release assets
+        run: |
+          mkdir -p release-assets
+          # Copy binaries with appropriate names for release
+          if [ -f artifacts/openhands-cli-linux/openhands ]; then
+            cp artifacts/openhands-cli-linux/openhands release-assets/openhands-linux
+          fi
+          if [ -f artifacts/openhands-cli-macos/openhands ]; then
+            cp artifacts/openhands-cli-macos/openhands release-assets/openhands-macos
+          fi
+          ls -la release-assets/
+
+      - name: Create GitHub Release
+        uses: softprops/action-gh-release@v2
+        with:
+          files: release-assets/*
+          draft: true
+          prerelease: false
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
--- a/.github/workflows/cli-build-test.yml
+++ b/.github/workflows/cli-build-test.yml
@ -1,58 +0,0 @@
-# Workflow that builds and tests the CLI binary executable
-name: CLI - Build and Test Binary
-
-# Run on pushes to main branch and all pull requests, but only when CLI files change
-on:
-  push:
-    branches:
-      - main
-    paths:
-      - "openhands-cli/**"
-  pull_request:
-    paths:
-      - "openhands-cli/**"
-
-# Cancel previous runs if a new commit is pushed
-concurrency:
-  group: ${{ github.workflow }}-${{ (github.head_ref && github.ref) || github.run_id }}
-  cancel-in-progress: true
-
-jobs:
-  build-and-test-binary:
-    name: Build and test binary executable
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-
-      - name: Set up Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: 3.12
-
-      - name: Install uv
-        uses: astral-sh/setup-uv@v3
-        with:
-          version: "latest"
-
-      - name: Install dependencies
-        working-directory: openhands-cli
-        run: |
-          uv sync
-
-      - name: Build binary executable
-        working-directory: openhands-cli
-        run: |
-          ./build.sh --install-pyinstaller | tee output.log
-          echo "Full output:"
-          cat output.log
-
-          if grep -q "❌" output.log; then
-            echo "❌ Found failure marker in output"
-            exit 1
-          fi
-
-          echo "✅ Build & test finished without ❌ markers"
--- a/.github/workflows/enterprise-check-migrations.yml
+++ b/.github/workflows/enterprise-check-migrations.yml
@ -0,0 +1,52 @@
+name: Enterprise Check Migrations
+
+on:
+  pull_request:
+    paths:
+      - 'enterprise/migrations/**'
+
+jobs:
+  check-sync:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout PR branch
+        uses: actions/checkout@v4
+        with:
+          ref: ${{ github.event.pull_request.head.sha }}
+          fetch-depth: 0
+
+
+      - name: Fetch base branch
+        run: git fetch origin ${{ github.event.pull_request.base.ref }}
+
+      - name: Check if base branch is ancestor of PR
+        id: check_up_to_date
+        shell: bash
+        run: |
+          BASE="origin/${{ github.event.pull_request.base.ref }}"
+          HEAD="${{ github.event.pull_request.head.sha }}"
+          if git merge-base --is-ancestor "$BASE" "$HEAD"; then
+            echo "We're up to date with base $BASE"
+            exit 0
+          else
+            echo "NOT up to date with base $BASE"
+            exit 1
+          fi
+
+      - name: Find Comment
+        uses: peter-evans/find-comment@v3
+        id: find-comment
+        with:
+          issue-number: ${{ github.event.pull_request.number }}
+          comment-author: 'github-actions[bot]'
+          body-includes: |
+            ⚠️ This PR contains **migrations**
+
+      - name: Comment warning on PR
+        uses: peter-evans/create-or-update-comment@v4
+        with:
+          issue-number: ${{ github.event.pull_request.number }}
+          comment-id: ${{ steps.find-comment.outputs.comment-id }}
+          edit-mode: replace
+          body: |
+            ⚠️ This PR contains **migrations**. Please synchronize before merging to prevent conflicts.
--- a/.github/workflows/ghcr-build.yml
+++ b/.github/workflows/ghcr-build.yml
@ -126,7 +126,7 @@ jobs:
      - name: Install Python dependencies using Poetry
        run: make install-python-dependencies POETRY_GROUP=main INSTALL_PLAYWRIGHT=0
      - 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
+        run: poetry run python3 -m openhands.runtime.utils.runtime_build --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
--- a/.github/workflows/lint.yml
+++ b/.github/workflows/lint.yml
@ -71,7 +71,7 @@ jobs:
        run: pip install pre-commit==4.2.0
      - name: Run pre-commit hooks
        working-directory: ./enterprise
-        run: pre-commit run --all-files --config ./dev_config/python/.pre-commit-config.yaml
+        run: pre-commit run --all-files --show-diff-on-failure --config ./dev_config/python/.pre-commit-config.yaml

  lint-cli-python:
    name: Lint CLI python
--- a/.github/workflows/pypi-release.yml
+++ b/.github/workflows/pypi-release.yml
@ -1,14 +1,17 @@
 # Publishes the OpenHands PyPi package
 name: Publish PyPi Package

-
 on:
  workflow_dispatch:
    inputs:
      reason:
-        description: 'Reason for manual trigger'
+        description: "What are you publishing?"
        required: true
-        default: ''
+        type: choice
+        options:
+          - app server
+          - cli
+        default: app server
  push:
    tags:
      - "*"
@ -16,6 +19,10 @@ on:
 jobs:
  release:
    runs-on: blacksmith-4vcpu-ubuntu-2204
+    # Run when manually dispatched for "app server" OR for tag pushes that don't contain '-cli'
+    if: |
+      (github.event_name == 'workflow_dispatch' && github.event.inputs.reason == 'app server')
+      || (github.event_name == 'push' && startsWith(github.ref, 'refs/tags/') && !contains(github.ref, '-cli'))
    steps:
      - uses: actions/checkout@v4
      - uses: useblacksmith/setup-python@v6
@ -32,3 +39,36 @@ jobs:
        run: ./build.sh
      - name: publish
        run: poetry publish -u __token__ -p ${{ secrets.PYPI_TOKEN }}
+
+  release-cli:
+    name: Publish CLI to PyPI
+    runs-on: ubuntu-latest
+    # Run when manually dispatched for "cli" OR for tag pushes that contain '-cli'
+    if: |
+      (github.event_name == 'workflow_dispatch' && github.event.inputs.reason == 'cli')
+      || (github.event_name == 'push' && startsWith(github.ref, 'refs/tags/') && contains(github.ref, '-cli'))
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: 3.12
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v3
+        with:
+          version: "latest"
+
+      - name: Build CLI package
+        working-directory: openhands-cli
+        run: |
+          # Clean dist directory to avoid conflicts with binary builds
+          rm -rf dist/
+          uv build
+
+      - name: Publish CLI to PyPI
+        working-directory: openhands-cli
+        run: |
+          uv publish --token ${{ secrets.PYPI_TOKEN_OPENHANDS }}
--- a/Development.md
+++ b/Development.md
@ -159,7 +159,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.58-nikolaik`
+Example: `export SANDBOX_RUNTIME_CONTAINER_IMAGE=ghcr.io/all-hands-ai/runtime:0.59-nikolaik`

 ## Develop inside Docker container

--- a/README.md
+++ b/README.md
@ -1,7 +1,7 @@
 <a name="readme-top"></a>

 <div align="center">
-  <img src="./docs/static/img/logo.png" alt="Logo" width="200">
+  <img src="https://raw.githubusercontent.com/All-Hands-AI/docs/main/openhands/static/img/logo.png" alt="Logo" width="200">
  <h1 align="center">OpenHands: Code Less, Make More</h1>
 </div>

@ -38,6 +38,12 @@ call APIs, and yes—even copy code snippets from StackOverflow.

 Learn more at [docs.all-hands.dev](https://docs.all-hands.dev), or [sign up for OpenHands Cloud](https://app.all-hands.dev) to get started.

+
+> [!IMPORTANT]
+> **Upcoming change**: We are renaming our GitHub Org from `All-Hands-AI` to `OpenHands` on October 20th, 2025.
+> Check the [tracking issue](https://github.com/All-Hands-AI/OpenHands/issues/11376) for more information.
+
+
 > [!IMPORTANT]
 > Using OpenHands for work? We'd love to chat! Fill out
 > [this short form](https://docs.google.com/forms/d/e/1FAIpQLSet3VbGaz8z32gW9Wm-Grl4jpt5WgMXPgJ4EDPVmCETCBpJtQ/viewform)
@ -76,17 +82,17 @@ You'll find OpenHands running at [http://localhost:3000](http://localhost:3000)
 You can also run OpenHands directly with Docker:

 ```bash
-docker pull docker.all-hands.dev/all-hands-ai/runtime:0.58-nikolaik
+docker pull docker.all-hands.dev/all-hands-ai/runtime:0.59-nikolaik

 docker run -it --rm --pull=always \
-    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.58-nikolaik \
+    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.59-nikolaik \
    -e LOG_ALL_EVENTS=true \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -v ~/.openhands:/.openhands \
    -p 3000:3000 \
    --add-host host.docker.internal:host-gateway \
    --name openhands-app \
-    docker.all-hands.dev/all-hands-ai/openhands:0.58
+    docker.all-hands.dev/all-hands-ai/openhands:0.59
 ```

 </details>
--- a/containers/dev/compose.yml
+++ b/containers/dev/compose.yml
@ -12,7 +12,7 @@ services:
      - SANDBOX_API_HOSTNAME=host.docker.internal
      - DOCKER_HOST_ADDR=host.docker.internal
      #
-      - SANDBOX_RUNTIME_CONTAINER_IMAGE=${SANDBOX_RUNTIME_CONTAINER_IMAGE:-ghcr.io/all-hands-ai/runtime:0.58-nikolaik}
+      - SANDBOX_RUNTIME_CONTAINER_IMAGE=${SANDBOX_RUNTIME_CONTAINER_IMAGE:-ghcr.io/all-hands-ai/runtime:0.59-nikolaik}
      - SANDBOX_USER_ID=${SANDBOX_USER_ID:-1234}
      - WORKSPACE_MOUNT_PATH=${WORKSPACE_BASE:-$PWD/workspace}
    ports:
--- a/containers/runtime/README.md
+++ b/containers/runtime/README.md
@ -6,7 +6,7 @@ that depends on the `base_image` **AND** a [Python source distribution](https://
 The following command will generate a `Dockerfile` file for `nikolaik/python-nodejs:python3.12-nodejs22` (the default base image), an updated `config.sh` and the runtime source distribution files/folders into `containers/runtime`:

 ```bash
-poetry run python3 openhands/runtime/utils/runtime_build.py \
+poetry run python3 -m openhands.runtime.utils.runtime_build \
    --base_image nikolaik/python-nodejs:python3.12-nodejs22 \
    --build_folder containers/runtime
 ```
--- a/docker-compose.yml
+++ b/docker-compose.yml
@ -7,7 +7,7 @@ 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.58-nikolaik}
+      - SANDBOX_RUNTIME_CONTAINER_IMAGE=${SANDBOX_RUNTIME_CONTAINER_IMAGE:-docker.all-hands.dev/all-hands-ai/runtime:0.59-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 for this user
      - WORKSPACE_MOUNT_PATH=${WORKSPACE_BASE:-$PWD/workspace}
    ports:
--- a/docs/DOC_STYLE_GUIDE.md
+++ b/docs/DOC_STYLE_GUIDE.md
@ -1,67 +0,0 @@
-# Documentation Style Guide
-
-## General Writing Principles
-
- **Clarity & Conciseness**: Always prioritize clarity and brevity. Avoid unnecessary jargon or overly complex explanations.
-Keep sentences short and to the point.
- **Gradual Complexity**: Start with the simplest, most basic setup, and then gradually introduce more advanced
-concepts and configurations.
-
-## Formatting Guidelines
-
-### Headers
-
-Use **Title Case** for the first and second level headers.
-
-Example:
-  - **Basic Usage**
-  - **Advanced Configuration Options**
-
-### Lists
-
-When listing items or options, use bullet points to enhance readability.
-
-Example:
-  - Option A
-  - Option B
-  - Option C
-
-### Procedures
-
-For instructions or processes that need to be followed in a specific order, use numbered steps.
-
-Example:
-  1. Step one: Do this.
-    - First this sub step.
-    - Then this sub step.
-  2. Step two: Complete this action.
-  3. Step three: Verify the result.
-
-### Code Blocks
-
-* Use code blocks for multi-line inputs, outputs, commands and code samples.
-
-Example:
-```bash
-docker run -it \
-    -e THIS=this \
-    -e THAT=that
-    ...
-```
-
-### Use of Note and Warning
-
-When adding a note or warning, use the built-in note and warning syntax.
-
-Example:
-<Note>
-This section is for advanced users only.
-</Note>
-
-### Referring to UI Elements
-
-When referencing UI elements, use ``.
-
-Example:
-1. Toggle the `Advanced` option
-2. Enter your model in the `Custom Model` textbox.
--- a/docs/README.md
+++ b/docs/README.md
@ -1,36 +0,0 @@
-# OpenHands Documentation
-
-This directory contains the documentation for OpenHands. The documentation is automatically synchronized with the [All-Hands-AI/docs](https://github.com/All-Hands-AI/docs) repository, which hosts the unified documentation site using Mintlify.
-
-## Documentation Structure
-
-The documentation files in this directory are automatically included in the main documentation site via Git submodules. When you make changes to documentation in this repository, they will be automatically synchronized to the docs repository.
-
-## How It Works
-
-1. **Automatic Sync**: When documentation changes are pushed to the `main` branch, a GitHub Action automatically notifies the docs repository
-2. **Submodule Update**: The docs repository updates its submodule reference to include your latest changes  
-3. **Site Rebuild**: Mintlify automatically rebuilds and deploys the documentation site
-
-## Making Documentation Changes
-
-Simply edit the documentation files in this directory as usual. The synchronization happens automatically when changes are merged to the main branch.
-
-## Local Development
-
-For local documentation development in this repository only:
-
-```bash
-npm install -g mint
-# or
-yarn global add mint
-
-# Preview local changes
-mint dev
-```
-
-For the complete unified documentation site, work with the [All-Hands-AI/docs](https://github.com/All-Hands-AI/docs) repository.
-
-## Configuration
-
-The Mintlify configuration (`docs.json`) has been moved to the root of the [All-Hands-AI/docs](https://github.com/All-Hands-AI/docs) repository to enable unified documentation across multiple repositories.
--- a/docs/README_JA.md
+++ b/docs/README_JA.md
@ -1,17 +0,0 @@
-# セットアップ
-
-```
-npm install -g mint
-```
-
-または
-
-```
-yarn global add mint
-```
-
-# プレビュー
-
-```
-mint dev
-```
--- a/docs/docs.json
+++ b/docs/docs.json
@ -1,233 +0,0 @@
-{
-  "$schema": "https://mintlify.com/docs.json",
-  "theme": "mint",
-  "name": "All Hands Docs",
-  "colors": {
-    "primary": "#99873c"
-  },
-  "background": {
-    "color": {
-      "light": "#f7f3ee"
-    }
-  },
-  "appearance": {
-    "default": "light",
-    "strict": true
-  },
-  "favicon": "/logo-square.png",
-  "navigation": {
-    "tabs": [
-      {
-        "tab": "Docs",
-        "pages": [
-          "index",
-          "usage/installation",
-          "usage/getting-started",
-          "usage/key-features",
-          "usage/faqs",
-          {
-            "group": "OpenHands Cloud",
-            "pages": [
-              "usage/cloud/openhands-cloud",
-              "usage/cloud/pro-subscription",
-              {
-                "group": "Integrations",
-                "pages": [
-                  "usage/cloud/bitbucket-installation",
-                  "usage/cloud/github-installation",
-                  "usage/cloud/gitlab-installation",
-                  "usage/cloud/slack-installation",
-                  {
-                    "group": "Project Management Tools",
-                    "pages": [
-                      "usage/cloud/project-management/overview",
-                      "usage/cloud/project-management/jira-integration",
-                      "usage/cloud/project-management/jira-dc-integration",
-                      "usage/cloud/project-management/linear-integration"
-                    ]
-                  }
-                ]
-              },
-              "usage/cloud/cloud-ui",
-              "usage/cloud/cloud-api"
-            ]
-          },
-          {
-            "group": "Run OpenHands on Your Own",
-            "pages": [
-              "usage/local-setup",
-              "usage/how-to/gui-mode",
-              "usage/how-to/cli-mode",
-              "usage/how-to/headless-mode",
-              "usage/how-to/github-action",
-              {
-                "group": "Advanced Configuration",
-                "pages": [
-                {
-                  "group": "LLM Configuration",
-                  "pages": [
-                    "usage/llms/llms",
-                    {
-                      "group": "Providers",
-                      "pages": [
-                        "usage/llms/openhands-llms",
-                        "usage/llms/azure-llms",
-                        "usage/llms/google-llms",
-                        "usage/llms/groq",
-                        "usage/llms/local-llms",
-                        "usage/llms/litellm-proxy",
-                        "usage/llms/moonshot",
-                        "usage/llms/openai-llms",
-                        "usage/llms/openrouter"
-                      ]
-                    }
-                  ]
-                },
-                {
-                  "group": "Runtime Configuration",
-                  "pages": [
-                    "usage/runtimes/overview",
-                    {
-                      "group": "Providers",
-                      "pages": [
-                        "usage/runtimes/docker",
-                        "usage/runtimes/remote",
-                        "usage/runtimes/local",
-                        {
-                          "group": "Third-Party Providers",
-                          "pages": [
-                            "usage/runtimes/modal",
-                            "usage/runtimes/daytona",
-                            "usage/runtimes/runloop",
-                            "usage/runtimes/e2b"
-                          ]
-                        }
-                      ]
-                    }
-                  ]
-                },
-                "usage/configuration-options",
-                "usage/how-to/custom-sandbox-guide",
-                "usage/search-engine-setup"
-                ]
-              }
-            ]
-          },
-          {
-            "group": "Customizations & Settings",
-            "pages": [
-              {
-                "group": "OpenHands Settings",
-                "pages": [
-                  "usage/settings/secrets-settings",
-                  "usage/settings/mcp-settings"
-                ]
-              },
-              "usage/prompting/repository",
-              {
-                "group": "Microagents",
-                "pages": [
-                  "usage/prompting/microagents-overview",
-                  "usage/prompting/microagents-repo",
-                  "usage/prompting/microagents-keyword",
-                  "usage/prompting/microagents-org",
-                  "usage/prompting/microagents-public"
-                ]
-              }
-            ]
-          },
-          {
-            "group": "Tips and Tricks",
-            "pages": [
-              "usage/prompting/prompting-best-practices"
-            ]
-          },
-          {
-            "group": "Troubleshooting & Feedback",
-            "pages": [
-              "usage/troubleshooting/troubleshooting",
-              "usage/feedback"
-            ]
-          },
-          {
-            "group": "OpenHands Developers",
-            "pages": [
-              "usage/how-to/development-overview",
-              {
-                "group": "Architecture",
-                "pages": [
-                  "usage/architecture/backend",
-                  "usage/architecture/runtime"
-                ]
-              },
-              "usage/how-to/debugging",
-              "usage/how-to/evaluation-harness",
-              "usage/how-to/websocket-connection"
-            ]
-          }
-        ]
-      },
-      {
-        "tab": "Success Stories",
-        "pages": [
-          "success-stories/index"
-        ]
-      },
-      {
-          "tab": "API Reference",
-          "openapi": "/openapi.json"
-      }
-    ],
-    "global": {
-      "anchors": [
-        {
-          "anchor": "Company",
-          "href": "https://www.all-hands.dev/",
-          "icon": "house"
-        },
-        {
-          "anchor": "Blog",
-          "href": "https://www.all-hands.dev/blog",
-          "icon": "newspaper"
-        },
-        {
-          "anchor": "OpenHands Cloud",
-          "href": "https://app.all-hands.dev",
-          "icon": "cloud"
-        }
-      ]
-    }
-  },
-  "logo": {
-    "light": "/logo/light.svg",
-    "dark": "/logo/dark.svg"
-  },
-  "navbar": {
-    "links": [
-    ],
-    "primary": {
-      "type": "github",
-      "href": "https://github.com/All-Hands-AI/OpenHands"
-    }
-  },
-  "footer": {
-    "socials": {
-      "slack": "https://all-hands.dev/joinslack",
-      "github": "https://github.com/All-Hands-AI/OpenHands"
-    }
-  },
-  "contextual": {
-    "options": [
-      "copy",
-      "view",
-      "chatgpt",
-      "claude"
-    ]
-  },
-  "redirects": [
-    {
-      "source": "/modules/:slug*",
-      "destination": "/:slug*"
-    }
-  ]
-}
--- a/docs/favicon.svg
+++ b/docs/favicon.svg
@ -1,19 +0,0 @@
-<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
-<path d="M9.06145 23.1079C5.26816 22.3769 -3.39077 20.6274 1.4173 5.06384C9.6344 6.09939 16.9728 14.0644 9.06145 23.1079Z" fill="url(#paint0_linear_17557_2021)"/>
-<path d="M8.91928 23.0939C5.27642 21.2223 0.78371 4.20891 17.0071 0C20.7569 7.19341 19.6212 16.5452 8.91928 23.0939Z" fill="url(#paint1_linear_17557_2021)"/>
-<path d="M8.91388 23.0788C8.73534 19.8817 10.1585 9.08525 23.5699 13.1107C23.1812 20.1229 18.984 26.4182 8.91388 23.0788Z" fill="url(#paint2_linear_17557_2021)"/>
-<defs>
-<linearGradient id="paint0_linear_17557_2021" x1="3.77557" y1="5.91571" x2="5.23185" y2="21.5589" gradientUnits="userSpaceOnUse">
-<stop stop-color="#18E299"/>
-<stop offset="1" stop-color="#15803D"/>
-</linearGradient>
-<linearGradient id="paint1_linear_17557_2021" x1="12.1711" y1="-0.718425" x2="10.1897" y2="22.9832" gradientUnits="userSpaceOnUse">
-<stop stop-color="#16A34A"/>
-<stop offset="1" stop-color="#4ADE80"/>
-</linearGradient>
-<linearGradient id="paint2_linear_17557_2021" x1="23.1327" y1="15.353" x2="9.33841" y2="18.5196" gradientUnits="userSpaceOnUse">
-<stop stop-color="#4ADE80"/>
-<stop offset="1" stop-color="#0D9373"/>
-</linearGradient>
-</defs>
-</svg>
--- a/docs/index.mdx
+++ b/docs/index.mdx
@ -1,17 +0,0 @@
---
-title: Introduction
-description: OpenHands - Code Less, Make More
-icon: book-open
-mode: wide
---
-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.
-
-<iframe
-  className="w-full aspect-video"
-  src="https://www.youtube.com/embed/oB4JR98KRAA"
-  title="YouTube video player"
-  frameborder="0"
-  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
-  allowfullscreen
-></iframe>
--- a/docs/logo-square.png
+++ b/docs/logo-square.png
--- a/docs/logo/dark.svg
+++ b/docs/logo/dark.svg
@ -1,29 +0,0 @@
-<svg width="1305" height="196" viewBox="0 0 1305 196" fill="none" xmlns="http://www.w3.org/2000/svg">
-<g clip-path="url(#clip0_14027_2415)">
-<g clip-path="url(#clip1_14027_2415)">
-<path d="M282.419 58.7848C273.03 53.1628 266.757 61.779 267.526 73.4779L267.448 73.5663C267.474 61.3495 265.779 47.8566 260.145 36.9411C258.15 33.0751 254.107 26.7204 246.113 29.7146C242.605 31.0285 239.423 34.9828 241.066 45.1909C241.066 45.1909 242.892 55.9043 242.552 69.3719V69.5614C240.27 32.4182 231.663 21.0857 219.352 21.8185C215.414 22.5007 210.028 24.1557 211.841 35.5766C211.841 35.5766 213.81 47.4902 214.449 56.9782L214.488 57.4583H214.449C208.659 36.979 200.86 36.701 195.213 37.4969C190.088 38.2171 184.493 43.3969 187.323 53.605C196.204 85.6315 194.47 124.202 193.805 129.723C191.992 125.946 191.431 122.952 188.914 118.808C178.794 102.169 173.982 100.944 168.074 100.691C162.206 100.438 155.868 103.963 156.285 110.672C156.716 117.38 160.224 118.492 165.205 127.841C169.092 135.118 170.2 144.656 178.025 161.99C184.506 176.342 201.447 192.084 232.302 190.214C257.302 189.405 294.639 180.89 288.144 124.973C286.527 115.258 287.74 107.122 288.588 98.7833C289.905 85.8463 291.835 64.4068 282.432 58.7722L282.419 58.7848Z" fill="#FFE165"/>
-<path d="M126.317 101.083C120.409 101.449 115.636 102.75 105.829 119.566C103.391 123.748 102.895 126.754 101.148 130.557C100.378 125.049 97.9134 86.516 106.181 54.3378C108.816 44.0918 103.13 39.0131 97.9916 38.3814C92.3318 37.6865 84.5201 38.1034 79.1211 58.7849H79.0559L79.1341 58.1911C79.5906 48.6905 81.3381 36.7516 81.3381 36.7516C82.9161 25.2928 77.517 23.7389 73.5655 23.1198C61.2808 22.6145 52.9083 33.9975 51.2912 70.8122H51.2652C50.7044 57.4836 52.3084 46.8713 52.3084 46.8713C53.756 36.6253 50.4957 32.7341 46.9616 31.4833C38.9152 28.6281 34.9898 35.0587 33.0727 38.9625C27.6476 49.9792 26.2 63.4973 26.4609 75.7141L26.3826 75.6257C26.9173 63.9142 20.488 55.4117 11.2027 61.1979C1.9174 66.9968 4.25176 88.3984 5.8167 101.31C6.83391 109.636 8.19019 117.747 6.75567 127.487C1.33054 183.505 38.8239 191.351 63.8368 191.717C94.7183 193.044 111.359 176.986 117.566 162.521C125.052 145.061 125.991 135.497 129.734 128.157C134.533 118.719 138.028 117.544 138.328 110.836C138.628 104.127 132.225 100.716 126.356 101.07L126.317 101.083Z" fill="#FFE165"/>
-<path d="M138.679 101.171C135.549 98.2021 130.842 96.6228 126.056 96.9008C118.387 97.3682 112.949 100.084 104.59 113.35C104.368 98.1768 105.242 75.3981 110.38 55.361C112.31 47.8313 110.367 42.9168 108.385 40.1247C106.076 36.8652 102.49 34.7175 98.5256 34.2374C94.9132 33.7952 90.1923 33.7699 85.5888 37.4337C85.5888 37.3832 85.6018 37.32 85.6018 37.32C87.0885 26.5561 83.2544 20.3908 74.2169 19.0011L73.7213 18.9505C68.1527 18.7105 63.3797 20.4792 59.5325 24.1935C57.472 26.177 55.6854 28.7417 54.1335 31.9128C52.399 29.4492 50.169 28.1984 48.4084 27.5668C37.6495 23.7387 31.7027 31.938 29.1205 37.1684C26.1211 43.2579 24.2562 50.0801 23.2129 57.0413C22.9912 56.9023 22.7825 56.7634 22.5608 56.637C20.1873 55.3105 15.2447 53.6934 8.82849 57.6983C-2.04784 64.4952 -0.665478 84.027 1.49935 101.815C1.61673 102.763 1.7341 103.698 1.85147 104.645C2.77739 111.935 3.65115 118.82 2.45136 126.919L2.42528 127.121C0.247403 149.596 4.61619 166.892 15.4143 178.553C25.795 189.771 42.0574 195.608 63.6144 195.924C65.1924 195.987 66.7312 196.013 68.231 196C105.059 195.671 118.27 171.73 121.517 164.15C125.716 154.346 127.894 147.032 129.629 141.144C130.972 136.596 132.041 133.008 133.554 130.026C135.276 126.641 136.788 124.442 138.119 122.497C140.388 119.187 142.344 116.331 142.579 111.025C142.748 107.185 141.392 103.774 138.64 101.171H138.679ZM65.6488 30.1314C67.7224 28.1353 70.1089 27.2509 73.1345 27.3141C75.7557 27.731 78.1292 28.3501 77.0468 36.183C76.9686 36.6757 75.2732 48.4377 74.8168 58.0141C74.8168 58.0773 74.8168 58.1404 74.8168 58.2036C72.4302 67.5526 70.4349 81.0202 69.3656 100.704C64.7359 100.981 60.1194 101.462 55.6332 102.093C54.1856 62.158 57.5372 37.9391 65.6358 30.1314H65.6488ZM36.9452 40.7817C40.1925 34.2121 42.9181 34.5406 45.4481 35.4376C48.9561 36.6883 48.4084 43.4727 48.0041 46.29C47.9389 46.7448 46.374 57.3192 46.9217 70.7742C46.5174 80.2116 46.5696 91.0893 47.0521 103.534C42.7616 104.355 38.6927 105.302 34.976 106.326C33.2155 100.59 25.4299 64.1541 36.9452 40.7943V40.7817ZM130.946 117.86C129.537 119.907 127.79 122.459 125.821 126.325C123.956 129.976 122.808 133.892 121.335 138.832C119.652 144.505 117.553 151.567 113.549 160.929C110.706 167.549 98.7603 189.051 63.8752 187.535C44.4309 187.257 30.6855 182.482 21.8566 172.943C12.7539 163.114 9.11539 147.979 11.0324 127.98C12.3626 118.833 11.3846 111.088 10.4326 103.609C10.3152 102.674 10.1978 101.752 10.0804 100.817C9.03715 92.1884 6.24634 69.2581 13.5103 64.7226C15.4664 63.4972 17.0705 63.2192 18.2572 63.8762C20.2786 65.0006 22.313 69.0939 22.0261 75.436C22.0131 75.7772 22.0522 76.1056 22.1174 76.4341C22.4826 91.2156 25.2082 104.077 26.7601 108.903C24.2171 109.825 21.974 110.785 20.0961 111.745C17.9834 112.832 17.1879 115.359 18.3094 117.405C19.0919 118.833 20.6047 119.642 22.1696 119.629C22.8347 119.629 23.5128 119.465 24.1519 119.136C34.7022 113.716 59.7281 108.208 81.7807 108.802C84.1803 108.84 86.1495 107.046 86.2147 104.734C86.28 102.422 84.402 100.501 82.0155 100.438C80.6983 100.4 79.3681 100.4 78.0379 100.4C80.2419 60.7051 86.306 47.7555 91.0269 43.9275C92.9831 42.3483 94.848 42.2219 97.4301 42.5378C98.1474 42.6262 99.9471 43.0305 101.238 44.8497C102.634 46.8332 102.894 49.7643 101.982 53.327C94.0003 84.4186 95.8 120.981 96.7129 129.85C96.5564 130.153 96.4129 130.456 96.2434 130.772C94.3785 134.17 90.9096 137.708 86.7755 137.468C84.4151 137.354 82.3415 139.098 82.1981 141.397C82.0546 143.709 83.8673 145.692 86.2539 145.831C93.2439 146.236 99.8297 142.079 103.872 134.714C104.303 133.93 104.668 133.185 104.994 132.465C105.02 132.414 105.046 132.351 105.072 132.301C105.829 130.658 106.376 129.155 106.859 127.803C107.615 125.706 108.267 123.886 109.571 121.638C118.831 105.744 122.587 105.517 126.564 105.277C128.898 105.138 131.22 105.858 132.589 107.172C133.567 108.094 133.998 109.244 133.932 110.684C133.802 113.653 132.954 114.891 130.907 117.873L130.946 117.86Z" fill="black"/>
-<path d="M292.383 124.316C291.04 116.243 291.783 109.345 292.566 102.043C292.67 101.095 292.774 100.16 292.866 99.2129C294.691 81.3993 295.709 61.8296 284.689 55.2348C278.194 51.3436 273.278 53.0492 270.93 54.4136C270.709 54.54 270.5 54.6916 270.278 54.8305C269.091 47.8946 267.109 41.1103 263.992 35.0713C261.319 29.8915 255.229 21.7933 244.535 25.8108C242.787 26.4678 240.597 27.7564 238.901 30.2579C237.284 27.1121 235.445 24.5853 233.346 22.6397C229.433 19.0012 224.621 17.3083 219.066 17.6494L218.57 17.6999C209.559 19.2539 205.842 25.4823 207.537 36.2463C207.537 36.2463 207.537 36.2968 207.55 36.3347C202.882 32.7467 198.161 32.8604 194.561 33.3658C190.61 33.9217 187.063 36.1326 184.82 39.43C182.902 42.2599 181.038 47.1997 183.111 54.6916C188.641 74.6403 189.945 97.4063 190.01 112.579C181.403 99.4656 175.912 96.8504 168.244 96.5219C163.471 96.3198 158.763 98.0001 155.699 101.02C152.999 103.673 151.708 107.109 151.956 110.937C152.295 116.231 154.303 119.061 156.638 122.32C158.007 124.24 159.559 126.413 161.345 129.761C162.923 132.718 164.058 136.28 165.493 140.803C167.344 146.653 169.653 153.93 174.048 163.658C177.438 171.175 191.105 194.888 227.829 194.547C229.316 194.535 230.855 194.484 232.42 194.383C254.094 193.688 270.239 187.548 280.411 176.152C290.975 164.302 295.017 146.931 292.422 124.493L292.396 124.291L292.383 124.316ZM245.317 44.5593C244.861 41.7041 244.17 34.9324 247.665 33.6311C250.169 32.6836 252.907 32.3172 256.272 38.8236C268.231 61.9812 261.149 98.5559 259.493 104.317C255.75 103.357 251.668 102.485 247.365 101.74C247.6 89.2954 247.443 78.4051 246.869 68.9803C247.156 55.5254 245.396 44.9762 245.317 44.5593ZM219.822 26.0003C222.861 25.874 225.26 26.7204 227.36 28.6913C235.602 36.36 239.423 60.5031 238.732 100.464C234.232 99.9078 229.616 99.5161 224.973 99.314C223.539 79.6432 221.283 66.2262 218.714 56.9151C218.714 56.8519 218.714 56.7888 218.714 56.7256C218.074 47.1492 216.144 35.4251 216.066 34.9703C214.827 27.1247 217.188 26.4678 219.809 26.0003H219.822ZM283.841 125.554C286.136 145.516 282.785 160.714 273.878 170.707C265.231 180.397 251.577 185.426 232.015 186.057C197.326 188.18 184.937 166.905 181.977 160.335C177.777 151.037 175.547 144.025 173.761 138.378C172.196 133.45 170.97 129.572 169.04 125.946C167.005 122.118 165.206 119.604 163.758 117.582C161.658 114.639 160.785 113.413 160.589 110.444C160.498 109.004 160.915 107.842 161.867 106.907C163.223 105.568 165.519 104.797 167.866 104.911C171.844 105.088 175.599 105.239 185.172 120.968C186.528 123.192 187.206 124.998 188.002 127.083C188.523 128.435 189.097 129.938 189.893 131.568C189.919 131.618 189.932 131.669 189.958 131.707C190.31 132.427 190.688 133.16 191.131 133.943C195.318 141.233 201.982 145.276 208.959 144.745C211.332 144.568 213.119 142.547 212.936 140.247C212.754 137.948 210.68 136.242 208.294 136.394C204.16 136.697 200.625 133.223 198.695 129.862C198.513 129.547 198.369 129.256 198.213 128.953C198.956 120.084 200.065 83.4839 191.484 52.5438C190.492 48.9937 190.701 46.0627 192.057 44.0539C193.322 42.2094 195.109 41.7672 195.826 41.6662C198.395 41.2998 200.273 41.4009 202.256 42.9422C207.055 46.6944 213.367 59.5303 216.314 99.175C214.984 99.1876 213.654 99.2255 212.349 99.2887C209.963 99.3898 208.124 101.348 208.228 103.66C208.333 105.972 210.315 107.715 212.741 107.652C234.767 106.667 259.911 111.72 270.552 116.963C271.191 117.279 271.869 117.418 272.547 117.418C274.112 117.406 275.612 116.572 276.368 115.119C277.451 113.06 276.603 110.533 274.464 109.484C272.573 108.549 270.304 107.64 267.748 106.755C269.209 101.904 271.7 88.9922 271.778 74.2107C271.843 73.8822 271.869 73.5537 271.843 73.2126C271.426 66.8831 273.395 62.7519 275.39 61.5896C276.564 60.9074 278.168 61.16 280.15 62.3476C287.506 66.7568 285.158 89.725 284.271 98.3791C284.18 99.314 284.076 100.236 283.971 101.171C283.163 108.676 282.328 116.42 283.841 125.554Z" fill="black"/>
-<path d="M162.923 44.774C162.232 44.774 161.527 44.6477 160.862 44.3445C158.424 43.258 157.354 40.4659 158.476 38.1034C162.101 30.4347 167.409 23.3598 173.812 17.6494C175.781 15.8933 178.859 16.007 180.672 17.9273C182.485 19.835 182.367 22.8166 180.385 24.5727C174.921 29.4493 170.395 35.4882 167.292 42.0325C166.483 43.7381 164.749 44.7614 162.923 44.774Z" fill="black"/>
-<path d="M146.57 42.0578C144.053 42.083 141.901 40.2132 141.692 37.737C140.766 26.6572 140.727 15.4258 141.601 4.34602C141.809 1.7561 144.144 -0.176866 146.804 0.0126405C149.478 0.214781 151.473 2.46359 151.277 5.05351C150.443 15.6406 150.482 26.3793 151.369 36.9664C151.59 39.5563 149.595 41.8304 146.922 42.0325C146.804 42.0325 146.687 42.0451 146.57 42.0451V42.0578Z" fill="black"/>
-<path d="M129.851 44.9762C127.673 45.0015 125.665 43.5739 125.104 41.4388C123.043 33.6058 119.144 26.1645 113.836 19.9361C112.128 17.9273 112.428 14.971 114.488 13.316C116.562 11.661 119.614 11.9516 121.322 13.9477C127.53 21.25 132.094 29.9547 134.494 39.1141C135.159 41.6283 133.581 44.1929 130.985 44.8372C130.594 44.9383 130.216 44.9762 129.825 44.9888L129.851 44.9762Z" fill="black"/>
-</g>
-</g>
-<path d="M379.045 147.144L419.52 55.0319C423.451 46.2048 424.882 39.0196 425.244 34.35C425.349 32.9943 426.419 31.9097 427.775 31.7892L440.789 30.5691C441.979 30.4637 443.109 31.1114 443.606 32.211L492.788 141.571C500.244 158.005 502.94 165.566 513.153 168.715C514.313 169.076 515.127 170.161 515.127 171.381V173.655C515.127 175.207 513.876 176.457 512.325 176.457H455.822C454.271 176.457 453.021 175.207 453.021 173.655V171.321C453.021 170.01 453.955 168.88 455.235 168.594C466.954 166.003 466.728 160.068 462.556 150.413L459.528 143.438C456.741 136.931 451.62 135.997 445.805 135.997H407.665C401.384 135.997 396.97 137.157 394.409 143.212L391.849 149.027C387.224 159.827 391.999 166.033 405.195 168.639C406.505 168.895 407.439 170.055 407.439 171.381V173.685C407.439 175.237 406.189 176.487 404.637 176.487H358.589C357.037 176.487 355.787 175.237 355.787 173.685V171.245C355.787 169.98 356.631 168.88 357.851 168.549C369.344 165.476 373.984 158.622 379.045 147.174V147.144ZM407.665 125.98H445.579C448.14 125.98 450.46 123.886 448.833 120.166L428.603 75.051C426.75 71.0894 425.816 71.0894 424.19 75.051L404.185 120.874C402.785 124.127 405.345 125.995 407.68 125.995L407.665 125.98Z" fill="#fff" stroke="#fff" stroke-width="0.393644" stroke-miterlimit="10"/>
-<path d="M527.675 156.227V50.1663C527.675 40.5107 524.075 37.3023 515.685 37.4378C514.103 37.468 512.777 36.2328 512.777 34.6361V32.708C512.777 31.3523 513.741 30.2074 515.067 29.9514L545.344 24.3328C552.093 23.1729 555.572 26.2006 555.572 32.4669V156.212C555.572 162.825 558.329 166.184 563.179 165.883C564.836 165.777 566.267 166.997 566.267 168.669V168.745C566.267 169.227 566.162 169.709 565.921 170.115C562.682 175.689 555.316 177.843 548.598 177.843C536.502 177.843 527.66 171.094 527.66 156.212L527.675 156.227Z" fill="#fff" stroke="#fff" stroke-width="0.393644" stroke-miterlimit="10"/>
-<path d="M581.748 156.227V50.1663C581.748 40.5107 578.148 37.3023 569.758 37.4378C568.176 37.468 566.851 36.2328 566.851 34.6361V32.708C566.851 31.3523 567.815 30.2074 569.14 29.9514L599.417 24.3328C606.166 23.1729 609.645 26.2006 609.645 32.4669V156.212C609.645 162.825 612.402 166.184 617.252 165.883C618.909 165.777 620.34 166.997 620.34 168.669V168.745C620.34 169.227 620.235 169.709 619.994 170.115C616.755 175.689 609.389 177.843 602.671 177.843C590.575 177.843 581.733 171.094 581.733 156.212L581.748 156.227Z" fill="#fff" stroke="#fff" stroke-width="0.393644" stroke-miterlimit="10"/>
-<path d="M688.158 155.052V53.4201C688.158 45.2558 683.383 41.4599 674.405 39.818C673.079 39.577 672.115 38.4171 672.115 37.0765V34.817C672.115 33.2655 673.365 32.0152 674.917 32.0152H733.046C734.598 32.0152 735.848 33.2655 735.848 34.817V37.0765C735.848 38.4171 734.884 39.577 733.558 39.818C724.566 41.4448 719.806 45.2408 719.806 53.4201V92.9613C719.806 98.3087 723.993 100.644 729.808 100.644H770.283C776.097 100.644 780.285 98.3238 780.285 92.9613V53.4201C780.285 45.2558 775.51 41.4599 766.532 39.818C765.206 39.577 764.242 38.4171 764.242 37.0765V34.817C764.242 33.2655 765.493 32.0152 767.044 32.0152H825.173C826.725 32.0152 827.975 33.2655 827.975 34.817V37.0765C827.975 38.4171 827.011 39.577 825.686 39.818C816.708 41.4448 811.933 45.2408 811.933 53.4201V155.067C811.933 163.232 816.708 167.027 825.686 168.669C827.011 168.91 827.975 170.07 827.975 171.411V173.67C827.975 175.222 826.725 176.472 825.173 176.472H767.044C765.493 176.472 764.242 175.222 764.242 173.67V171.411C764.242 170.07 765.206 168.91 766.532 168.669C775.525 167.043 780.285 163.247 780.285 155.067V117.62C780.285 112.272 776.097 109.938 770.524 109.938H729.582C723.993 109.938 719.821 112.257 719.821 117.62V155.067C719.821 163.232 724.596 167.027 733.573 168.669C734.899 168.91 735.863 170.07 735.863 171.411V173.67C735.863 175.222 734.613 176.472 733.061 176.472H674.932C673.381 176.472 672.13 175.222 672.13 173.67V171.411C672.13 170.07 673.094 168.91 674.42 168.669C683.398 167.043 688.173 163.247 688.173 155.067L688.158 155.052Z" fill="#fff" stroke="#fff" stroke-width="0.393644" stroke-miterlimit="10"/>
-<path d="M834.929 152.265C834.929 133.421 850.745 122.033 896.101 115.511C902.608 114.577 904.476 112.95 904.476 106.909V103.189C904.476 86.4384 899.128 77.8373 885.873 77.8373C859.361 77.8373 879.591 108.777 855.4 108.777C846.091 108.777 841.677 102.963 841.677 95.5216C841.677 77.6114 867.029 69.4772 892.621 69.4772C920.066 69.4772 932.388 79.4792 932.388 111.805V156.227C932.388 162.855 934.346 166.379 938.941 165.973C940.553 165.837 941.923 167.148 941.923 168.759C941.923 169.226 941.818 169.708 941.577 170.115C938.414 175.688 931.891 177.843 924.947 177.843C911.917 177.843 905.877 170.16 904.943 161.8C904.717 159.013 902.849 158.546 900.755 161.107C894.248 169.241 882.152 177.858 865.402 177.858C849.585 177.858 834.929 170.416 834.929 152.28V152.265ZM879.817 162.267C894.007 162.267 904.476 151.331 904.476 136.675V130.634C904.476 125.287 902.623 122.952 895.167 123.66C869.348 125.98 863.534 137.608 863.534 146.692C863.534 155.067 868.414 162.282 879.817 162.282V162.267Z" fill="#fff" stroke="#fff" stroke-width="0.393644" stroke-miterlimit="10"/>
-<path d="M1038.21 156.227V114.125C1038.21 98.0829 1030.3 85.746 1015.89 85.746C1001.47 85.746 992.856 98.0678 992.856 114.125V154.359C992.856 164.211 996.2 167.751 1005.07 168.971C1006.46 169.167 1007.51 170.341 1007.51 171.742V173.655C1007.51 175.207 1006.26 176.457 1004.71 176.457H952.863C951.311 176.457 950.061 175.207 950.061 173.655V171.757C950.061 170.357 951.115 169.182 952.501 168.986C961.584 167.766 964.944 164.226 964.944 154.359V95.7481C964.944 86.0925 961.343 82.884 952.953 83.0196C951.372 83.0497 950.046 81.8145 950.046 80.2178V78.2897C950.046 76.934 951.01 75.7892 952.336 75.5331L982.613 69.9145C989.361 68.7546 992.841 71.7824 992.841 77.1298C992.841 85.505 996.561 87.5988 999.589 84.1041C1004.47 78.2897 1013.31 68.9806 1031.69 68.9806C1048.91 68.9806 1066.11 77.3558 1066.11 108.748V156.197C1066.11 162.81 1068.87 166.169 1073.72 165.868C1075.37 165.762 1076.8 166.982 1076.8 168.654V168.73C1076.8 169.212 1076.7 169.694 1076.46 170.1C1073.22 175.674 1065.85 177.828 1059.13 177.828C1047.04 177.828 1038.2 171.08 1038.2 156.197L1038.21 156.227Z" fill="#fff" stroke="#fff" stroke-width="0.393644" stroke-miterlimit="10"/>
-<path d="M1082.63 125.061C1082.63 88.7735 1107.52 69.4775 1133.11 69.4775C1157.06 69.4775 1165.21 86.6948 1165.21 67.6096V50.1663C1165.21 40.5107 1161.61 37.3023 1153.22 37.4378C1151.64 37.468 1150.31 36.2328 1150.31 34.6361V32.708C1150.31 31.3523 1151.27 30.2074 1152.6 29.9514L1182.88 24.3328C1189.63 23.1729 1193.1 26.2006 1193.1 32.4669V156.212C1193.1 162.825 1195.86 166.184 1200.71 165.883C1202.37 165.777 1203.8 166.997 1203.8 168.669V168.745C1203.8 169.227 1203.69 169.709 1203.45 170.115C1200.21 175.689 1192.86 177.843 1186.36 177.843C1178.67 177.843 1170.77 174.815 1168.22 167.841C1166.82 164.12 1164.73 162.493 1162.18 162.493C1156.59 162.493 1148.46 177.843 1127.29 177.843C1104.04 177.843 1082.63 158.532 1082.63 125.046V125.061ZM1142.64 161.574C1152.64 161.574 1165.21 155.534 1165.21 135.289V117.62C1165.21 89.2405 1148.92 78.0786 1135.89 78.0786C1120.77 78.0786 1111.94 93.4281 1111.94 114.592C1111.94 139.718 1124.27 161.574 1142.64 161.574Z" fill="#fff" stroke="#fff" stroke-width="0.393644" stroke-miterlimit="10"/>
-<path d="M1219.29 167.826C1218.9 167.539 1218.6 167.163 1218.39 166.726C1212.86 154.781 1212.35 141.103 1221.02 141.103C1224.28 141.103 1226.37 142.73 1227.53 146.225C1233.12 162.975 1242.88 169.483 1256.6 169.483C1272.19 169.483 1276.61 161.574 1276.61 154.133C1276.61 143.905 1267.07 140.636 1252.41 136.223C1233.57 130.408 1215.66 121.34 1215.66 101.095C1215.66 80.8501 1234.5 69.4623 1258.45 69.4623C1272.06 69.4623 1284.77 73.213 1292.72 78.7865C1293.13 79.0727 1293.46 79.4643 1293.67 79.9162C1299.19 91.8463 1299.68 105.268 1291.02 105.268C1287.77 105.268 1285.67 103.641 1284.51 100.146C1278.93 83.3958 1268.92 77.3554 1257.07 77.3554C1245.91 77.3554 1240.79 82.9439 1240.79 91.3041C1240.79 101.773 1249.63 106.895 1260.79 110.374C1277.54 115.496 1302.65 121.777 1302.65 145.035C1302.65 166.666 1280.33 177.828 1254.98 177.828C1240 177.828 1227.23 173.625 1219.28 167.795L1219.29 167.826Z" fill="#fff" stroke="#fff" stroke-width="0.393644" stroke-miterlimit="10"/>
-<defs>
-<clipPath id="clip0_14027_2415">
-<rect width="294" height="196" fill="white"/>
-</clipPath>
-<clipPath id="clip1_14027_2415">
-<rect width="294" height="196" fill="white"/>
-</clipPath>
-</defs>
-</svg>
--- a/docs/logo/light.svg
+++ b/docs/logo/light.svg
@ -1,29 +0,0 @@
-<svg width="1305" height="196" viewBox="0 0 1305 196" fill="none" xmlns="http://www.w3.org/2000/svg">
-<g clip-path="url(#clip0_14027_2415)">
-<g clip-path="url(#clip1_14027_2415)">
-<path d="M282.419 58.7848C273.03 53.1628 266.757 61.779 267.526 73.4779L267.448 73.5663C267.474 61.3495 265.779 47.8566 260.145 36.9411C258.15 33.0751 254.107 26.7204 246.113 29.7146C242.605 31.0285 239.423 34.9828 241.066 45.1909C241.066 45.1909 242.892 55.9043 242.552 69.3719V69.5614C240.27 32.4182 231.663 21.0857 219.352 21.8185C215.414 22.5007 210.028 24.1557 211.841 35.5766C211.841 35.5766 213.81 47.4902 214.449 56.9782L214.488 57.4583H214.449C208.659 36.979 200.86 36.701 195.213 37.4969C190.088 38.2171 184.493 43.3969 187.323 53.605C196.204 85.6315 194.47 124.202 193.805 129.723C191.992 125.946 191.431 122.952 188.914 118.808C178.794 102.169 173.982 100.944 168.074 100.691C162.206 100.438 155.868 103.963 156.285 110.672C156.716 117.38 160.224 118.492 165.205 127.841C169.092 135.118 170.2 144.656 178.025 161.99C184.506 176.342 201.447 192.084 232.302 190.214C257.302 189.405 294.639 180.89 288.144 124.973C286.527 115.258 287.74 107.122 288.588 98.7833C289.905 85.8463 291.835 64.4068 282.432 58.7722L282.419 58.7848Z" fill="#FFE165"/>
-<path d="M126.317 101.083C120.409 101.449 115.636 102.75 105.829 119.566C103.391 123.748 102.895 126.754 101.148 130.557C100.378 125.049 97.9134 86.516 106.181 54.3378C108.816 44.0918 103.13 39.0131 97.9916 38.3814C92.3318 37.6865 84.5201 38.1034 79.1211 58.7849H79.0559L79.1341 58.1911C79.5906 48.6905 81.3381 36.7516 81.3381 36.7516C82.9161 25.2928 77.517 23.7389 73.5655 23.1198C61.2808 22.6145 52.9083 33.9975 51.2912 70.8122H51.2652C50.7044 57.4836 52.3084 46.8713 52.3084 46.8713C53.756 36.6253 50.4957 32.7341 46.9616 31.4833C38.9152 28.6281 34.9898 35.0587 33.0727 38.9625C27.6476 49.9792 26.2 63.4973 26.4609 75.7141L26.3826 75.6257C26.9173 63.9142 20.488 55.4117 11.2027 61.1979C1.9174 66.9968 4.25176 88.3984 5.8167 101.31C6.83391 109.636 8.19019 117.747 6.75567 127.487C1.33054 183.505 38.8239 191.351 63.8368 191.717C94.7183 193.044 111.359 176.986 117.566 162.521C125.052 145.061 125.991 135.497 129.734 128.157C134.533 118.719 138.028 117.544 138.328 110.836C138.628 104.127 132.225 100.716 126.356 101.07L126.317 101.083Z" fill="#FFE165"/>
-<path d="M138.679 101.171C135.549 98.2021 130.842 96.6228 126.056 96.9008C118.387 97.3682 112.949 100.084 104.59 113.35C104.368 98.1768 105.242 75.3981 110.38 55.361C112.31 47.8313 110.367 42.9168 108.385 40.1247C106.076 36.8652 102.49 34.7175 98.5256 34.2374C94.9132 33.7952 90.1923 33.7699 85.5888 37.4337C85.5888 37.3832 85.6018 37.32 85.6018 37.32C87.0885 26.5561 83.2544 20.3908 74.2169 19.0011L73.7213 18.9505C68.1527 18.7105 63.3797 20.4792 59.5325 24.1935C57.472 26.177 55.6854 28.7417 54.1335 31.9128C52.399 29.4492 50.169 28.1984 48.4084 27.5668C37.6495 23.7387 31.7027 31.938 29.1205 37.1684C26.1211 43.2579 24.2562 50.0801 23.2129 57.0413C22.9912 56.9023 22.7825 56.7634 22.5608 56.637C20.1873 55.3105 15.2447 53.6934 8.82849 57.6983C-2.04784 64.4952 -0.665478 84.027 1.49935 101.815C1.61673 102.763 1.7341 103.698 1.85147 104.645C2.77739 111.935 3.65115 118.82 2.45136 126.919L2.42528 127.121C0.247403 149.596 4.61619 166.892 15.4143 178.553C25.795 189.771 42.0574 195.608 63.6144 195.924C65.1924 195.987 66.7312 196.013 68.231 196C105.059 195.671 118.27 171.73 121.517 164.15C125.716 154.346 127.894 147.032 129.629 141.144C130.972 136.596 132.041 133.008 133.554 130.026C135.276 126.641 136.788 124.442 138.119 122.497C140.388 119.187 142.344 116.331 142.579 111.025C142.748 107.185 141.392 103.774 138.64 101.171H138.679ZM65.6488 30.1314C67.7224 28.1353 70.1089 27.2509 73.1345 27.3141C75.7557 27.731 78.1292 28.3501 77.0468 36.183C76.9686 36.6757 75.2732 48.4377 74.8168 58.0141C74.8168 58.0773 74.8168 58.1404 74.8168 58.2036C72.4302 67.5526 70.4349 81.0202 69.3656 100.704C64.7359 100.981 60.1194 101.462 55.6332 102.093C54.1856 62.158 57.5372 37.9391 65.6358 30.1314H65.6488ZM36.9452 40.7817C40.1925 34.2121 42.9181 34.5406 45.4481 35.4376C48.9561 36.6883 48.4084 43.4727 48.0041 46.29C47.9389 46.7448 46.374 57.3192 46.9217 70.7742C46.5174 80.2116 46.5696 91.0893 47.0521 103.534C42.7616 104.355 38.6927 105.302 34.976 106.326C33.2155 100.59 25.4299 64.1541 36.9452 40.7943V40.7817ZM130.946 117.86C129.537 119.907 127.79 122.459 125.821 126.325C123.956 129.976 122.808 133.892 121.335 138.832C119.652 144.505 117.553 151.567 113.549 160.929C110.706 167.549 98.7603 189.051 63.8752 187.535C44.4309 187.257 30.6855 182.482 21.8566 172.943C12.7539 163.114 9.11539 147.979 11.0324 127.98C12.3626 118.833 11.3846 111.088 10.4326 103.609C10.3152 102.674 10.1978 101.752 10.0804 100.817C9.03715 92.1884 6.24634 69.2581 13.5103 64.7226C15.4664 63.4972 17.0705 63.2192 18.2572 63.8762C20.2786 65.0006 22.313 69.0939 22.0261 75.436C22.0131 75.7772 22.0522 76.1056 22.1174 76.4341C22.4826 91.2156 25.2082 104.077 26.7601 108.903C24.2171 109.825 21.974 110.785 20.0961 111.745C17.9834 112.832 17.1879 115.359 18.3094 117.405C19.0919 118.833 20.6047 119.642 22.1696 119.629C22.8347 119.629 23.5128 119.465 24.1519 119.136C34.7022 113.716 59.7281 108.208 81.7807 108.802C84.1803 108.84 86.1495 107.046 86.2147 104.734C86.28 102.422 84.402 100.501 82.0155 100.438C80.6983 100.4 79.3681 100.4 78.0379 100.4C80.2419 60.7051 86.306 47.7555 91.0269 43.9275C92.9831 42.3483 94.848 42.2219 97.4301 42.5378C98.1474 42.6262 99.9471 43.0305 101.238 44.8497C102.634 46.8332 102.894 49.7643 101.982 53.327C94.0003 84.4186 95.8 120.981 96.7129 129.85C96.5564 130.153 96.4129 130.456 96.2434 130.772C94.3785 134.17 90.9096 137.708 86.7755 137.468C84.4151 137.354 82.3415 139.098 82.1981 141.397C82.0546 143.709 83.8673 145.692 86.2539 145.831C93.2439 146.236 99.8297 142.079 103.872 134.714C104.303 133.93 104.668 133.185 104.994 132.465C105.02 132.414 105.046 132.351 105.072 132.301C105.829 130.658 106.376 129.155 106.859 127.803C107.615 125.706 108.267 123.886 109.571 121.638C118.831 105.744 122.587 105.517 126.564 105.277C128.898 105.138 131.22 105.858 132.589 107.172C133.567 108.094 133.998 109.244 133.932 110.684C133.802 113.653 132.954 114.891 130.907 117.873L130.946 117.86Z" fill="black"/>
-<path d="M292.383 124.316C291.04 116.243 291.783 109.345 292.566 102.043C292.67 101.095 292.774 100.16 292.866 99.2129C294.691 81.3993 295.709 61.8296 284.689 55.2348C278.194 51.3436 273.278 53.0492 270.93 54.4136C270.709 54.54 270.5 54.6916 270.278 54.8305C269.091 47.8946 267.109 41.1103 263.992 35.0713C261.319 29.8915 255.229 21.7933 244.535 25.8108C242.787 26.4678 240.597 27.7564 238.901 30.2579C237.284 27.1121 235.445 24.5853 233.346 22.6397C229.433 19.0012 224.621 17.3083 219.066 17.6494L218.57 17.6999C209.559 19.2539 205.842 25.4823 207.537 36.2463C207.537 36.2463 207.537 36.2968 207.55 36.3347C202.882 32.7467 198.161 32.8604 194.561 33.3658C190.61 33.9217 187.063 36.1326 184.82 39.43C182.902 42.2599 181.038 47.1997 183.111 54.6916C188.641 74.6403 189.945 97.4063 190.01 112.579C181.403 99.4656 175.912 96.8504 168.244 96.5219C163.471 96.3198 158.763 98.0001 155.699 101.02C152.999 103.673 151.708 107.109 151.956 110.937C152.295 116.231 154.303 119.061 156.638 122.32C158.007 124.24 159.559 126.413 161.345 129.761C162.923 132.718 164.058 136.28 165.493 140.803C167.344 146.653 169.653 153.93 174.048 163.658C177.438 171.175 191.105 194.888 227.829 194.547C229.316 194.535 230.855 194.484 232.42 194.383C254.094 193.688 270.239 187.548 280.411 176.152C290.975 164.302 295.017 146.931 292.422 124.493L292.396 124.291L292.383 124.316ZM245.317 44.5593C244.861 41.7041 244.17 34.9324 247.665 33.6311C250.169 32.6836 252.907 32.3172 256.272 38.8236C268.231 61.9812 261.149 98.5559 259.493 104.317C255.75 103.357 251.668 102.485 247.365 101.74C247.6 89.2954 247.443 78.4051 246.869 68.9803C247.156 55.5254 245.396 44.9762 245.317 44.5593ZM219.822 26.0003C222.861 25.874 225.26 26.7204 227.36 28.6913C235.602 36.36 239.423 60.5031 238.732 100.464C234.232 99.9078 229.616 99.5161 224.973 99.314C223.539 79.6432 221.283 66.2262 218.714 56.9151C218.714 56.8519 218.714 56.7888 218.714 56.7256C218.074 47.1492 216.144 35.4251 216.066 34.9703C214.827 27.1247 217.188 26.4678 219.809 26.0003H219.822ZM283.841 125.554C286.136 145.516 282.785 160.714 273.878 170.707C265.231 180.397 251.577 185.426 232.015 186.057C197.326 188.18 184.937 166.905 181.977 160.335C177.777 151.037 175.547 144.025 173.761 138.378C172.196 133.45 170.97 129.572 169.04 125.946C167.005 122.118 165.206 119.604 163.758 117.582C161.658 114.639 160.785 113.413 160.589 110.444C160.498 109.004 160.915 107.842 161.867 106.907C163.223 105.568 165.519 104.797 167.866 104.911C171.844 105.088 175.599 105.239 185.172 120.968C186.528 123.192 187.206 124.998 188.002 127.083C188.523 128.435 189.097 129.938 189.893 131.568C189.919 131.618 189.932 131.669 189.958 131.707C190.31 132.427 190.688 133.16 191.131 133.943C195.318 141.233 201.982 145.276 208.959 144.745C211.332 144.568 213.119 142.547 212.936 140.247C212.754 137.948 210.68 136.242 208.294 136.394C204.16 136.697 200.625 133.223 198.695 129.862C198.513 129.547 198.369 129.256 198.213 128.953C198.956 120.084 200.065 83.4839 191.484 52.5438C190.492 48.9937 190.701 46.0627 192.057 44.0539C193.322 42.2094 195.109 41.7672 195.826 41.6662C198.395 41.2998 200.273 41.4009 202.256 42.9422C207.055 46.6944 213.367 59.5303 216.314 99.175C214.984 99.1876 213.654 99.2255 212.349 99.2887C209.963 99.3898 208.124 101.348 208.228 103.66C208.333 105.972 210.315 107.715 212.741 107.652C234.767 106.667 259.911 111.72 270.552 116.963C271.191 117.279 271.869 117.418 272.547 117.418C274.112 117.406 275.612 116.572 276.368 115.119C277.451 113.06 276.603 110.533 274.464 109.484C272.573 108.549 270.304 107.64 267.748 106.755C269.209 101.904 271.7 88.9922 271.778 74.2107C271.843 73.8822 271.869 73.5537 271.843 73.2126C271.426 66.8831 273.395 62.7519 275.39 61.5896C276.564 60.9074 278.168 61.16 280.15 62.3476C287.506 66.7568 285.158 89.725 284.271 98.3791C284.18 99.314 284.076 100.236 283.971 101.171C283.163 108.676 282.328 116.42 283.841 125.554Z" fill="black"/>
-<path d="M162.923 44.774C162.232 44.774 161.527 44.6477 160.862 44.3445C158.424 43.258 157.354 40.4659 158.476 38.1034C162.101 30.4347 167.409 23.3598 173.812 17.6494C175.781 15.8933 178.859 16.007 180.672 17.9273C182.485 19.835 182.367 22.8166 180.385 24.5727C174.921 29.4493 170.395 35.4882 167.292 42.0325C166.483 43.7381 164.749 44.7614 162.923 44.774Z" fill="black"/>
-<path d="M146.57 42.0578C144.053 42.083 141.901 40.2132 141.692 37.737C140.766 26.6572 140.727 15.4258 141.601 4.34602C141.809 1.7561 144.144 -0.176866 146.804 0.0126405C149.478 0.214781 151.473 2.46359 151.277 5.05351C150.443 15.6406 150.482 26.3793 151.369 36.9664C151.59 39.5563 149.595 41.8304 146.922 42.0325C146.804 42.0325 146.687 42.0451 146.57 42.0451V42.0578Z" fill="black"/>
-<path d="M129.851 44.9762C127.673 45.0015 125.665 43.5739 125.104 41.4388C123.043 33.6058 119.144 26.1645 113.836 19.9361C112.128 17.9273 112.428 14.971 114.488 13.316C116.562 11.661 119.614 11.9516 121.322 13.9477C127.53 21.25 132.094 29.9547 134.494 39.1141C135.159 41.6283 133.581 44.1929 130.985 44.8372C130.594 44.9383 130.216 44.9762 129.825 44.9888L129.851 44.9762Z" fill="black"/>
-</g>
-</g>
-<path d="M379.045 147.144L419.52 55.0319C423.451 46.2048 424.882 39.0196 425.244 34.35C425.349 32.9943 426.419 31.9097 427.775 31.7892L440.789 30.5691C441.979 30.4637 443.109 31.1114 443.606 32.211L492.788 141.571C500.244 158.005 502.94 165.566 513.153 168.715C514.313 169.076 515.127 170.161 515.127 171.381V173.655C515.127 175.207 513.876 176.457 512.325 176.457H455.822C454.271 176.457 453.021 175.207 453.021 173.655V171.321C453.021 170.01 453.955 168.88 455.235 168.594C466.954 166.003 466.728 160.068 462.556 150.413L459.528 143.438C456.741 136.931 451.62 135.997 445.805 135.997H407.665C401.384 135.997 396.97 137.157 394.409 143.212L391.849 149.027C387.224 159.827 391.999 166.033 405.195 168.639C406.505 168.895 407.439 170.055 407.439 171.381V173.685C407.439 175.237 406.189 176.487 404.637 176.487H358.589C357.037 176.487 355.787 175.237 355.787 173.685V171.245C355.787 169.98 356.631 168.88 357.851 168.549C369.344 165.476 373.984 158.622 379.045 147.174V147.144ZM407.665 125.98H445.579C448.14 125.98 450.46 123.886 448.833 120.166L428.603 75.051C426.75 71.0894 425.816 71.0894 424.19 75.051L404.185 120.874C402.785 124.127 405.345 125.995 407.68 125.995L407.665 125.98Z" fill="black" stroke="black" stroke-width="0.393644" stroke-miterlimit="10"/>
-<path d="M527.675 156.227V50.1663C527.675 40.5107 524.075 37.3023 515.685 37.4378C514.103 37.468 512.777 36.2328 512.777 34.6361V32.708C512.777 31.3523 513.741 30.2074 515.067 29.9514L545.344 24.3328C552.093 23.1729 555.572 26.2006 555.572 32.4669V156.212C555.572 162.825 558.329 166.184 563.179 165.883C564.836 165.777 566.267 166.997 566.267 168.669V168.745C566.267 169.227 566.162 169.709 565.921 170.115C562.682 175.689 555.316 177.843 548.598 177.843C536.502 177.843 527.66 171.094 527.66 156.212L527.675 156.227Z" fill="black" stroke="black" stroke-width="0.393644" stroke-miterlimit="10"/>
-<path d="M581.748 156.227V50.1663C581.748 40.5107 578.148 37.3023 569.758 37.4378C568.176 37.468 566.851 36.2328 566.851 34.6361V32.708C566.851 31.3523 567.815 30.2074 569.14 29.9514L599.417 24.3328C606.166 23.1729 609.645 26.2006 609.645 32.4669V156.212C609.645 162.825 612.402 166.184 617.252 165.883C618.909 165.777 620.34 166.997 620.34 168.669V168.745C620.34 169.227 620.235 169.709 619.994 170.115C616.755 175.689 609.389 177.843 602.671 177.843C590.575 177.843 581.733 171.094 581.733 156.212L581.748 156.227Z" fill="black" stroke="black" stroke-width="0.393644" stroke-miterlimit="10"/>
-<path d="M688.158 155.052V53.4201C688.158 45.2558 683.383 41.4599 674.405 39.818C673.079 39.577 672.115 38.4171 672.115 37.0765V34.817C672.115 33.2655 673.365 32.0152 674.917 32.0152H733.046C734.598 32.0152 735.848 33.2655 735.848 34.817V37.0765C735.848 38.4171 734.884 39.577 733.558 39.818C724.566 41.4448 719.806 45.2408 719.806 53.4201V92.9613C719.806 98.3087 723.993 100.644 729.808 100.644H770.283C776.097 100.644 780.285 98.3238 780.285 92.9613V53.4201C780.285 45.2558 775.51 41.4599 766.532 39.818C765.206 39.577 764.242 38.4171 764.242 37.0765V34.817C764.242 33.2655 765.493 32.0152 767.044 32.0152H825.173C826.725 32.0152 827.975 33.2655 827.975 34.817V37.0765C827.975 38.4171 827.011 39.577 825.686 39.818C816.708 41.4448 811.933 45.2408 811.933 53.4201V155.067C811.933 163.232 816.708 167.027 825.686 168.669C827.011 168.91 827.975 170.07 827.975 171.411V173.67C827.975 175.222 826.725 176.472 825.173 176.472H767.044C765.493 176.472 764.242 175.222 764.242 173.67V171.411C764.242 170.07 765.206 168.91 766.532 168.669C775.525 167.043 780.285 163.247 780.285 155.067V117.62C780.285 112.272 776.097 109.938 770.524 109.938H729.582C723.993 109.938 719.821 112.257 719.821 117.62V155.067C719.821 163.232 724.596 167.027 733.573 168.669C734.899 168.91 735.863 170.07 735.863 171.411V173.67C735.863 175.222 734.613 176.472 733.061 176.472H674.932C673.381 176.472 672.13 175.222 672.13 173.67V171.411C672.13 170.07 673.094 168.91 674.42 168.669C683.398 167.043 688.173 163.247 688.173 155.067L688.158 155.052Z" fill="black" stroke="black" stroke-width="0.393644" stroke-miterlimit="10"/>
-<path d="M834.929 152.265C834.929 133.421 850.745 122.033 896.101 115.511C902.608 114.577 904.476 112.95 904.476 106.909V103.189C904.476 86.4384 899.128 77.8373 885.873 77.8373C859.361 77.8373 879.591 108.777 855.4 108.777C846.091 108.777 841.677 102.963 841.677 95.5216C841.677 77.6114 867.029 69.4772 892.621 69.4772C920.066 69.4772 932.388 79.4792 932.388 111.805V156.227C932.388 162.855 934.346 166.379 938.941 165.973C940.553 165.837 941.923 167.148 941.923 168.759C941.923 169.226 941.818 169.708 941.577 170.115C938.414 175.688 931.891 177.843 924.947 177.843C911.917 177.843 905.877 170.16 904.943 161.8C904.717 159.013 902.849 158.546 900.755 161.107C894.248 169.241 882.152 177.858 865.402 177.858C849.585 177.858 834.929 170.416 834.929 152.28V152.265ZM879.817 162.267C894.007 162.267 904.476 151.331 904.476 136.675V130.634C904.476 125.287 902.623 122.952 895.167 123.66C869.348 125.98 863.534 137.608 863.534 146.692C863.534 155.067 868.414 162.282 879.817 162.282V162.267Z" fill="black" stroke="black" stroke-width="0.393644" stroke-miterlimit="10"/>
-<path d="M1038.21 156.227V114.125C1038.21 98.0829 1030.3 85.746 1015.89 85.746C1001.47 85.746 992.856 98.0678 992.856 114.125V154.359C992.856 164.211 996.2 167.751 1005.07 168.971C1006.46 169.167 1007.51 170.341 1007.51 171.742V173.655C1007.51 175.207 1006.26 176.457 1004.71 176.457H952.863C951.311 176.457 950.061 175.207 950.061 173.655V171.757C950.061 170.357 951.115 169.182 952.501 168.986C961.584 167.766 964.944 164.226 964.944 154.359V95.7481C964.944 86.0925 961.343 82.884 952.953 83.0196C951.372 83.0497 950.046 81.8145 950.046 80.2178V78.2897C950.046 76.934 951.01 75.7892 952.336 75.5331L982.613 69.9145C989.361 68.7546 992.841 71.7824 992.841 77.1298C992.841 85.505 996.561 87.5988 999.589 84.1041C1004.47 78.2897 1013.31 68.9806 1031.69 68.9806C1048.91 68.9806 1066.11 77.3558 1066.11 108.748V156.197C1066.11 162.81 1068.87 166.169 1073.72 165.868C1075.37 165.762 1076.8 166.982 1076.8 168.654V168.73C1076.8 169.212 1076.7 169.694 1076.46 170.1C1073.22 175.674 1065.85 177.828 1059.13 177.828C1047.04 177.828 1038.2 171.08 1038.2 156.197L1038.21 156.227Z" fill="black" stroke="black" stroke-width="0.393644" stroke-miterlimit="10"/>
-<path d="M1082.63 125.061C1082.63 88.7735 1107.52 69.4775 1133.11 69.4775C1157.06 69.4775 1165.21 86.6948 1165.21 67.6096V50.1663C1165.21 40.5107 1161.61 37.3023 1153.22 37.4378C1151.64 37.468 1150.31 36.2328 1150.31 34.6361V32.708C1150.31 31.3523 1151.27 30.2074 1152.6 29.9514L1182.88 24.3328C1189.63 23.1729 1193.1 26.2006 1193.1 32.4669V156.212C1193.1 162.825 1195.86 166.184 1200.71 165.883C1202.37 165.777 1203.8 166.997 1203.8 168.669V168.745C1203.8 169.227 1203.69 169.709 1203.45 170.115C1200.21 175.689 1192.86 177.843 1186.36 177.843C1178.67 177.843 1170.77 174.815 1168.22 167.841C1166.82 164.12 1164.73 162.493 1162.18 162.493C1156.59 162.493 1148.46 177.843 1127.29 177.843C1104.04 177.843 1082.63 158.532 1082.63 125.046V125.061ZM1142.64 161.574C1152.64 161.574 1165.21 155.534 1165.21 135.289V117.62C1165.21 89.2405 1148.92 78.0786 1135.89 78.0786C1120.77 78.0786 1111.94 93.4281 1111.94 114.592C1111.94 139.718 1124.27 161.574 1142.64 161.574Z" fill="black" stroke="black" stroke-width="0.393644" stroke-miterlimit="10"/>
-<path d="M1219.29 167.826C1218.9 167.539 1218.6 167.163 1218.39 166.726C1212.86 154.781 1212.35 141.103 1221.02 141.103C1224.28 141.103 1226.37 142.73 1227.53 146.225C1233.12 162.975 1242.88 169.483 1256.6 169.483C1272.19 169.483 1276.61 161.574 1276.61 154.133C1276.61 143.905 1267.07 140.636 1252.41 136.223C1233.57 130.408 1215.66 121.34 1215.66 101.095C1215.66 80.8501 1234.5 69.4623 1258.45 69.4623C1272.06 69.4623 1284.77 73.213 1292.72 78.7865C1293.13 79.0727 1293.46 79.4643 1293.67 79.9162C1299.19 91.8463 1299.68 105.268 1291.02 105.268C1287.77 105.268 1285.67 103.641 1284.51 100.146C1278.93 83.3958 1268.92 77.3554 1257.07 77.3554C1245.91 77.3554 1240.79 82.9439 1240.79 91.3041C1240.79 101.773 1249.63 106.895 1260.79 110.374C1277.54 115.496 1302.65 121.777 1302.65 145.035C1302.65 166.666 1280.33 177.828 1254.98 177.828C1240 177.828 1227.23 173.625 1219.28 167.795L1219.29 167.826Z" fill="black" stroke="black" stroke-width="0.393644" stroke-miterlimit="10"/>
-<defs>
-<clipPath id="clip0_14027_2415">
-<rect width="294" height="196" fill="white"/>
-</clipPath>
-<clipPath id="clip1_14027_2415">
-<rect width="294" height="196" fill="white"/>
-</clipPath>
-</defs>
-</svg>
--- a/docs/openapi.json
+++ b/docs/openapi.json
--- a/docs/reo-init.js
+++ b/docs/reo-init.js
@ -1,14 +0,0 @@
-// Reo.dev tracking initialization
-(function() {
-  var e, t, n;
-  e = "6bac7145b4ee6ec";
-  t = function() {
-    Reo.init({clientID: "6bac7145b4ee6ec"});
-  };
-  n = document.createElement("script");
-  n.src = "https://static.reo.dev/" + e + "/reo.js";
-  n.defer = true;
-  n.onload = t;
-  document.head.appendChild(n);
-})();
-
--- a/docs/static/img/backend_architecture.png
+++ b/docs/static/img/backend_architecture.png
--- a/docs/static/img/backend_architecture.puml
+++ b/docs/static/img/backend_architecture.puml
@ -1,201 +0,0 @@
-@startuml openhands
-!pragma useIntermediatePackages false
-
-class openhands.action.agent.AgentEchoAction {
-  content: str
-  runnable: bool
-  action: str
-}
-class openhands.action.agent.AgentFinishAction {
-  runnable: bool
-  action: str
-}
-class openhands.observation.AgentMessageObservation {
-  role: str
-  observation: str
-}
-class openhands.action.agent.AgentSummarizeAction {
-  summary: str
-  action: str
-}
-class openhands.action.agent.AgentThinkAction {
-  thought: str
-  runnable: bool
-  action: str
-}
-class openhands.action.base.ExecutableAction {
-}
-class openhands.action.base.NotExecutableAction {
-}
-class openhands.observation.Observation {
-  content: str
-}
-class openhands.action.base.Action {
-}
-class openhands.action.base.NullAction {
-  action: str
-}
-class openhands.action.bash.CmdRunAction {
-  command: str
-  action: str
-}
-class openhands.action.browse.BrowseURLAction {
-  url: str
-  action: str
-}
-class openhands.observation.BrowserOutputObservation {
-  url: str
-  status_code: int
-  error: bool
-  observation: str
-}
-class openhands.action.fileop.FileReadAction {
-  path: str
-  action: str
-}
-class openhands.observation.FileReadObservation {
-  path: str
-  observation: str
-}
-class openhands.action.fileop.FileWriteAction {
-  path: str
-  contents: str
-  action: str
-}
-class openhands.observation.FileWriteObservation {
-  path: str
-  observation: str
-}
-class openhands.action.tasks.AddTaskAction {
-  parent: str
-  goal: str
-  subtasks: list
-  action: str
-}
-class openhands.action.tasks.ModifyTaskAction {
-  id: str
-  state: str
-  action: str
-}
-abstract class openhands.agent.Agent {
-  _registry: Dict[str, Type[Agent]] {static}
-  llm: LLM
-  _complete: None
-}
-class openhands.llm.llm.LLM {
-  model: None
-  api_key: None
-  base_url: None
-  _debug_dir: None
-  _debug_idx: None
-  _debug_id: None
-  _completion: None
-}
-class openhands.controller.agent_controller.AgentController {
-  agent: Agent
-  max_iterations: int
-  workdir: str
-  command_manager: CommandManager
-  state: State
-  plan: Plan
-  callbacks: List[Callable]
-}
-class openhands.observation.AgentErrorObservation {
-  observation: str
-}
-class openhands.controller.command_manager.CommandManager {
-  directory: None
-  shell: None
-}
-class openhands.observation.NullObservation {
-  observation: str
-}
-class openhands.plan.Plan {
-  main_goal: str {static}
-  task: Task {static}
-  main_goal: str
-  task: None
-}
-class openhands.state.State {
-  plan: Plan
-  iteration: int
-  history: List[Tuple[Action, Observation]]
-  updated_info: List[Tuple[Action, Observation]]
-}
-class openhands.observation.CmdOutputObservation {
-  command: str
-  exit_code: int
-  observation: str
-}
-class openhands.sandbox.sandbox.DockerInteractive {
-  instance_id: None
-  instance_id: None
-  workspace_dir: None
-  workspace_dir: None
-  workspace_dir: None
-  timeout: int
-  base_container_image: None
-  container_name: None
-}
-class openhands.observation.UserMessageObservation {
-  role: str
-  observation: str
-}
-class openhands.plan.Task {
-  id: str {static}
-  goal: str {static}
-  parent: Task | None {static}
-  subtasks: List[Task] {static}
-  id: None
-  id: None
-  parent: None
-  goal: str
-  subtasks: None
-}
-
-class openhands.server.session.Session {
-  websocket: None
-  controller: Optional[AgentController]
-  agent: Optional[Agent]
-  agent_task: None
-}
-
-openhands.action.base.ExecutableAction <|-- openhands.action.agent.AgentEchoAction
-openhands.action.base.NotExecutableAction <|-- openhands.action.agent.AgentFinishAction
-openhands.observation.Observation <|-- openhands.observation.AgentMessageObservation
-openhands.action.base.NotExecutableAction <|-- openhands.action.agent.AgentSummarizeAction
-openhands.action.base.NotExecutableAction <|-- openhands.action.agent.AgentThinkAction
-openhands.action.base.Action <|-- openhands.action.base.ExecutableAction
-openhands.action.base.Action <|-- openhands.action.base.NotExecutableAction
-openhands.action.base.NotExecutableAction <|-- openhands.action.base.NullAction
-openhands.action.base.ExecutableAction <|-- openhands.action.bash.CmdRunAction
-openhands.action.base.ExecutableAction <|-- openhands.action.browse.BrowseURLAction
-openhands.observation.Observation <|-- openhands.observation.BrowserOutputObservation
-openhands.action.base.ExecutableAction <|-- openhands.action.fileop.FileReadAction
-openhands.observation.Observation <|-- openhands.observation.FileReadObservation
-openhands.action.base.ExecutableAction <|-- openhands.action.fileop.FileWriteAction
-openhands.observation.Observation <|-- openhands.observation.FileWriteObservation
-openhands.action.base.NotExecutableAction <|-- openhands.action.tasks.AddTaskAction
-openhands.action.base.NotExecutableAction <|-- openhands.action.tasks.ModifyTaskAction
-openhands.agent.Agent *-- openhands.agent.Agent
-openhands.agent.Agent *-- openhands.llm.llm.LLM
-openhands.controller.agent_controller.AgentController *-- openhands.agent.Agent
-openhands.observation.Observation <|-- openhands.observation.AgentErrorObservation
-openhands.observation.Observation <|-- openhands.observation.NullObservation
-openhands.plan.Plan *-- openhands.plan.Task
-openhands.state.State *-- openhands.plan.Plan
-openhands.state.State *-- openhands.observation.CmdOutputObservation
-openhands.state.State *-- openhands.action.base.Action
-openhands.state.State *-- openhands.observation.Observation
-openhands.observation.Observation <|-- openhands.observation.CmdOutputObservation
-openhands.observation.Observation <|-- openhands.observation.UserMessageObservation
-openhands.plan.Task *-- openhands.plan.Task
-openhands.server.session.Session *-- openhands.controller.agent_controller.AgentController
-openhands.server.session.Session *-- openhands.agent.Agent
-openhands.controller.agent_controller.AgentController -> openhands.state.State
-openhands.controller.agent_controller.AgentController -> openhands.plan.Plan
-openhands.controller.agent_controller.AgentController -> openhands.controller.command_manager.CommandManager
-openhands.controller.command_manager.CommandManager -> openhands.sandbox.sandbox.DockerInteractive
-
-footer Based on f3fda42; Generated by //py2puml//
-@enduml
--- a/docs/static/img/backend_architecture.svg
+++ b/docs/static/img/backend_architecture.svg
--- a/docs/static/img/connect-repo.png
+++ b/docs/static/img/connect-repo.png
--- a/docs/static/img/jira-admin-configure.png
+++ b/docs/static/img/jira-admin-configure.png
--- a/docs/static/img/jira-admin-edit.png
+++ b/docs/static/img/jira-admin-edit.png
--- a/docs/static/img/jira-dc-admin-configure.png
+++ b/docs/static/img/jira-dc-admin-configure.png
--- a/docs/static/img/jira-dc-admin-edit.png
+++ b/docs/static/img/jira-dc-admin-edit.png
--- a/docs/static/img/jira-dc-user-link.png
+++ b/docs/static/img/jira-dc-user-link.png
--- a/docs/static/img/jira-dc-user-unlink.png
+++ b/docs/static/img/jira-dc-user-unlink.png
--- a/docs/static/img/jira-user-link.png
+++ b/docs/static/img/jira-user-link.png
--- a/docs/static/img/jira-user-unlink.png
+++ b/docs/static/img/jira-user-unlink.png
--- a/docs/static/img/linear-admin-configure.png
+++ b/docs/static/img/linear-admin-configure.png
--- a/docs/static/img/linear-admin-edit.png
+++ b/docs/static/img/linear-admin-edit.png
--- a/docs/static/img/linear-user-link.png
+++ b/docs/static/img/linear-user-link.png
--- a/docs/static/img/linear-user-unlink.png
+++ b/docs/static/img/linear-user-unlink.png
--- a/docs/static/img/logo-square.png
+++ b/docs/static/img/logo-square.png
--- a/docs/static/img/logo.png
+++ b/docs/static/img/logo.png
--- a/docs/static/img/oh-features.png
+++ b/docs/static/img/oh-features.png
--- a/docs/static/img/openhands-llm-api-key.png
+++ b/docs/static/img/openhands-llm-api-key.png
--- a/docs/static/img/openhands-provider-cli.png
+++ b/docs/static/img/openhands-provider-cli.png
--- a/docs/static/img/results.png
+++ b/docs/static/img/results.png
--- a/docs/static/img/slack-create-conversation.png
+++ b/docs/static/img/slack-create-conversation.png
--- a/docs/static/img/slack-pro-tip.png
+++ b/docs/static/img/slack-pro-tip.png
--- a/docs/static/img/slack-results-and-follow-up.png
+++ b/docs/static/img/slack-results-and-follow-up.png
--- a/docs/static/img/system_architecture.png
+++ b/docs/static/img/system_architecture.png
--- a/docs/static/img/system_architecture.puml
+++ b/docs/static/img/system_architecture.puml
@ -1,67 +0,0 @@
-@startuml "System Architecture"
-
-
-node frontend as frontend{
-
-    component App
-
-    package components{
-
-        component Terminal
-
-        component ChatInterface
-
-        component BannerSettings
-
-    }
-
-    package services{
-        component chatService
-
-        component settingsService
-
-        chatService -[hidden]u-> settingsService
-    }
-
-    package socket
-
-    App -> Terminal
-    App -> ChatInterface
-    App -> BannerSettings
-    ChatInterface -> chatService
-    BannerSettings -> settingsService
-    Terminal -> socket
-    chatService -d-> socket
-    settingsService -d-> socket
-    services -[hidden]d-> socket
-
-    Terminal -[hidden]u-> ChatInterface
-    ChatInterface -[hidden]u-> BannerSettings
-
-
-
-    interface "HTTP (:3001)" as HTTP
-    HTTP - App
-
-}
-
-node backend{
-    package server as serverpackage{
-        component Server
-
-        'defined in server/server.py, port is defined at startup with uvicorn
-        interface "Client WS\n(:3000/ws)" as client_socket
-        client_socket - Server
-
-
-    }
-    node AgentController{
-
-    }
-    Server -d-> AgentController
-}
-
-
-socket -d-> client_socket: connects to \n VITE_TERMINAL_WS_URL
-
-@enduml
--- a/docs/static/img/system_architecture.svg
+++ b/docs/static/img/system_architecture.svg
--- a/docs/static/img/system_architecture_overview.png
+++ b/docs/static/img/system_architecture_overview.png
--- a/docs/static/img/teaser.mp4
+++ b/docs/static/img/teaser.mp4
--- a/docs/success-stories/index.mdx
+++ b/docs/success-stories/index.mdx
@ -1,217 +0,0 @@
---
-title: "Success Stories"
-description: "Real-world examples of what you can achieve with OpenHands"
---
-
-Discover how developers and teams are using OpenHands to automate their software development workflows. From quick fixes to complex projects, see what's possible with AI-powered development assistance.
-
-Check out the [#success-stories](https://www.linen.dev/s/openhands/c/success-stories) channel on our Slack for more!
-
-<Update label="2025-06-13 OpenHands helps frontline support" description="@Joe Pelletier">
-
-## One of the cool things about OpenHands, and especially the Slack Integration, is the ability to empower folks who are on the ‘front lines’ with customers.
-
-For example, often times Support and Customer Success teams will field bug reports, doc questions, and other ‘nits’ from customers. They tend to have few options to deal with this, other than file a feedback ticket with product teams and hope it gets prioritized in an upcoming sprint.
-
-Instead, with tools like OpenHands and the Slack integration, they can request OpenHands to make fixes proactively and then have someone on the engineering team (like a lead engineer, a merge engineer, or even technical product manager) review the PR and approve it — thus reducing the cycle time for ‘quick wins’ from weeks to just a few hours.
-
-Here's how we do that with the OpenHands project:
-
-<iframe
-  width="560"
-  height="560"
-  src="https://www.linen.dev/s/openhands/t/29118545/seems-mcp-config-from-config-toml-is-being-overwritten-hence#629f8e2b-cde8-427e-920c-390557a06cc9"
-  frameborder="0"
-  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
-  allowfullscreen
-></iframe>
-
-[Original Slack thread](https://www.linen.dev/s/openhands/t/29124350/one-of-the-cool-things-about-openhands-and-especially-the-sl#25029f37-7b0d-4535-9187-83b3e06a4011)
-
-</Update>
-
-
-<Update label="2025-06-13 Ask OpenHands to show me some love" description="@Graham Neubig">
-
-## Asked openhands to “show me some love” and...
-
-Asked openhands to “show me some love” and it coded up this app for me, actually kinda genuinely feel loved
-
-<video
-  controls
-  autoplay
-  className="w-full aspect-video"
-  src="/success-stories/stories/2025-06-13-show-love/v1.mp4"
-></video>
-
-[Original Slack thread](https://www.linen.dev/s/openhands/t/29100731/asked-openhands-to-show-me-some-love-and-it-coded-up-this-ap#1e08af6b-b7d5-4167-8a53-17e6806555e0)
-
-</Update>
-
-<Update label="2025-06-11 OpenHands does 100% of my infra IAM research for me" description="@Xingyao Wang">
-
-## Now, OpenHands does 100% of my infra IAM research for me
-
-Got an IAM error on GCP? Send a screenshot to OH... and it just works!!!
-Can't imagine going back to the early days without OH: I'd spend an entire afternoon figuring how to get IAM right
-
-[Original Slack thread](https://www.linen.dev/s/openhands/t/29100732/now-openhands-does-100-of-my-infra-iam-research-for-me-sweat#20482a73-4e2e-4edd-b6d1-c9e8442fccd1)
-
-![](/success-stories/stories/2025-06-11-infra-iam/s1.png)
-![](/success-stories/stories/2025-06-11-infra-iam/s2.png)
-
-</Update>
-
-<Update label="2025-06-08 OpenHands builds an interactive map for me" description="@Rodrigo Argenton Freire (ODLab)">
-
-## Very simple example, but baby steps....
-
-I am a professor of architecture and urban design. We built, me and some students, an interactive map prototype to help visitors and new students to find important places in the campus. Considering that we lack a lot of knowledge in programming, that was really nice to build and a smooth process.
-We first created the main components with all-hands and then adjusted some details locally. Definitely, saved us a lot of time and money.
-That's a prototype but we will have all the info by tuesday.
-https://buriti-emau.github.io/Mapa-UFU/
-
-[Original Slack thread](https://www.linen.dev/s/openhands/t/29100736/very-simple-example-but-baby-steps-i-am-a-professor-of-archi#8f2e3f3f-44e6-44ea-b9a8-d53487470179)
-
-![](/success-stories/stories/2025-06-08-map/s1.png)
-
-</Update>
-
-
-<Update label="2025-06-06 Web Search Saves the Day" description="@Ian Walker">
-
-## Tavily adapter helps solve persistent debugging issue
-
-Big congratulations to the new [Tavily adapter](https://www.all-hands.dev/blog/building-a-provably-versatile-agent)... OpenHands and I have been beavering away at a Lightstreamer client library for most of this week but were getting a persistent (and unhelpful) "unexpected error" from the server.
-
-Coming back to the problem today, after trying several unsuccessful fixes prompted by me, OH decided all by itself to search the web, and found the cause of the problem (of course it was simply CRLF line endings...). I was on the verge of giving up - good thing OH has more stamina than me!
-
-This demonstrates how OpenHands' web search capabilities can help solve debugging issues that would otherwise require extensive manual research.
-
-<iframe
-  width="560"
-  height="560"
-  src="https://www.linen.dev/s/openhands/t/29100737/big-congratulations-to-the-new-tavily-adapter-openhands-and-#87b027e5-188b-425e-8aa9-719dcb4929f4"
-  title="YouTube video player"
-  frameborder="0"
-  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
-  allowfullscreen
-></iframe>
-
-
-[Original Slack thread](https://www.linen.dev/s/openhands/t/29100737/big-congratulations-to-the-new-tavily-adapter-openhands-and-#76f1fb26-6ef7-4709-b9ea-fb99105e47e4)
-
-</Update>
-
-<Update label="2025-06-05 OpenHands updates my personal website for a new paper" description="@Xingyao Wang">
-
-## I asked OpenHands to update my personal website for the "OpenHands Versa" paper.
-
-It is an extremely trivial task: You just need to browse to arxiv, copy the author names, format them for BibTeX, and then modify the papers.bib file. But now I'm getting way too lazy to even open my IDE and actually do this one-file change!
-
-[Original Tweet/X thread](https://x.com/xingyaow_/status/1930796287919542410)
-
-[Original Slack thread](https://www.linen.dev/s/openhands/t/29100738/i-asked-openhands-to-update-my-personal-website-for-the-open#f0324022-b12b-4d34-b12b-bdbc43823f69)
-
-</Update>
-
-<Update label="2025-06-02 OpenHands makes an animated gif of swe-bench verified scores over time" description="@Graham Neubig">
-
-## I asked OpenHands to make an animated gif of swe-bench verified scores over time.
-
-It took a bit of prompting but ended up looking pretty nice I think
-
-<video width="560" height="315" autoPlay loop muted src="/success-stories/stories/2025-06-02-swebench-score/s1.mp4"></video>
-
-[Original Slack thread](https://www.linen.dev/s/openhands/t/29100744/i-asked-openhands-to-make-an-animated-gif-of-swe-bench-verif#fb3b82c9-6222-4311-b97b-b2ac1cfe6dff)
-
-</Update>
-
-<Update label="2025-05-30 AWS Troubleshooting" description="@Graham Neubig">
-
-## Quick AWS security group fix
-
-I really don't like trying to fix issues with AWS, especially security groups and other finicky things like this. But I started up an instance and wasn't able to ssh in. So I asked OpenHands:
-
-> Currently, the following ssh command is timing out:
->
-> $ ssh -i gneubig.pem ubuntu@XXX.us-east-2.compute.amazonaws.com
-> ssh: connect to host XXX.us-east-2.compute.amazonaws.com port 22: Operation timed out
->
-> Use the provided AWS credentials to take a look at i-XXX and examine why
-
-And 2 minutes later I was able to SSH in!
-
-This shows how OpenHands can quickly diagnose and fix AWS infrastructure issues that would normally require manual investigation.
-
-[Original Slack thread](https://www.linen.dev/s/openhands/t/29100747/i-really-don-t-like-trying-to-fix-issues-with-aws-especially#d92a66d2-3bc1-4467-9d09-dc983004d083)
-
-</Update>
-
-
-<Update label="2025-05-04 Chrome Extension Development" description="@Xingyao Wang">
-
-## OpenHands builds Chrome extension for GitHub integration
-
-I asked OpenHands to write a Chrome extension based on our [OpenHands Cloud API](https://docs.all-hands.dev/modules/usage/cloud/cloud-api). Once installed, you can now easily launch an OpenHands cloud session from your GitHub webpage/PR!
-
-This demonstrates OpenHands' ability to create browser extensions and integrate with external APIs, enabling seamless workflows between GitHub and OpenHands Cloud.
-
-![Chrome extension](/success-stories/stories/2025-05-04-chrome-extension/s1.png)
-![Chrome extension](/success-stories/stories/2025-05-04-chrome-extension/s2.png)
-
-[GitHub Repository](https://github.com/xingyaoww/openhands-chrome-extension)
-
-[Original Slack thread](https://www.linen.dev/s/openhands/t/29100755/i-asked-openhands-to-write-a-chrome-extension-based-on-our-h#88f14b7f-f8ff-40a6-83c2-bd64e95924c5)
-
-</Update>
-
-
-<Update label="2025-04-11 Visual UI Testing" description="@Xingyao Wang">
-
-## OpenHands tests UI automatically with visual browsing
-
-Thanks to visual browsing -- OpenHands can actually test some simple UI by serving the website, clicking the button in the browser and looking at screenshots now!
-
-Prompt is just:
-```
-I want to create a Hello World app in Javascript that:
-* Displays Hello World in the middle.
-* Has a button that when clicked, changes the greeting with a bouncing animation to fun versions of Hello.
-* Has a counter for how many times the button has been clicked.
-* Has another button that changes the app's background color.
-```
-
-Eager-to-work Sonnet 3.7 will test stuff for you without you asking!
-
-This showcases OpenHands' visual browsing capabilities, enabling it to create, serve, and automatically test web applications through actual browser interactions and screenshot analysis.
-
-![Visual UI testing](/success-stories/stories/2025-04-11-visual-ui/s1.png)
-
-[Original Slack thread](https://www.linen.dev/s/openhands/t/29100764/thanks-to-u07k0p3bdb9-s-visual-browsing-openhands-can-actual#21beb9bc-1a04-4272-87e9-4d3e3b9925e7)
-
-</Update>
-
-<Update label="2025-03-07 Proactive Error Handling" description="@Graham Neubig">
-
-## OpenHands fixes crashes before you notice them
-
-Interesting story, I asked OpenHands to start an app on port 12000, it showed up on the app pane. I started using the app, and then it crashed... But because it crashed in OpenHands, OpenHands immediately saw the error message and started fixing the problem without me having to do anything. It was already fixing the problem before I even realized what was going wrong.
-
-This demonstrates OpenHands' proactive monitoring capabilities - it doesn't just execute commands, but actively watches for errors and begins remediation automatically, often faster than human reaction time.
-
-</Update>
-
-<Update label="2024-12-03 Creative Design Acceleration" description="@Rohit Malhotra">
-
-## Pair programming for interactive design projects
-
-Used OpenHands as a pair programmer to do heavy lifting for a creative/interactive design project in p5js.
-
-I usually take around 2 days for high fidelity interactions (planning strategy + writing code + circling back with designer), did this in around 5hrs instead with the designer watching curiously the entire time.
-
-This showcases how OpenHands can accelerate creative and interactive design workflows, reducing development time by 75% while maintaining high quality output.
-
-[Original Tweet](https://x.com/rohit_malh5/status/1863995531657425225)
-
-</Update>
--- a/docs/success-stories/stories/2025-04-11-visual-ui/s1.png
+++ b/docs/success-stories/stories/2025-04-11-visual-ui/s1.png
--- a/docs/success-stories/stories/2025-05-04-chrome-extension/s1.png
+++ b/docs/success-stories/stories/2025-05-04-chrome-extension/s1.png
--- a/docs/success-stories/stories/2025-05-04-chrome-extension/s2.png
+++ b/docs/success-stories/stories/2025-05-04-chrome-extension/s2.png
--- a/docs/success-stories/stories/2025-06-02-swebench-score/s1.mp4
+++ b/docs/success-stories/stories/2025-06-02-swebench-score/s1.mp4
--- a/docs/success-stories/stories/2025-06-08-map/s1.png
+++ b/docs/success-stories/stories/2025-06-08-map/s1.png
--- a/docs/success-stories/stories/2025-06-11-infra-iam/s1.png
+++ b/docs/success-stories/stories/2025-06-11-infra-iam/s1.png
--- a/docs/success-stories/stories/2025-06-11-infra-iam/s2.png
+++ b/docs/success-stories/stories/2025-06-11-infra-iam/s2.png
--- a/docs/success-stories/stories/2025-06-13-show-love/v1.mp4
+++ b/docs/success-stories/stories/2025-06-13-show-love/v1.mp4
--- a/docs/usage/about.mdx
+++ b/docs/usage/about.mdx
@ -1,30 +0,0 @@
---
-title: About OpenHands
---
-
-## Research Strategy
-
-Achieving full replication of production-grade applications with LLMs is a complex endeavor. Our strategy involves:
-
- **Core Technical Research:** Focusing on foundational research to understand and improve the technical aspects of code generation and handling.
- **Task Planning:** Developing capabilities for bug detection, codebase management, and optimization.
- **Evaluation:** Establishing comprehensive evaluation metrics to better understand and improve our agents.
-
-## Default Agent
-
-Our default Agent is currently the [CodeActAgent](./agents), which is capable of generating code and handling files.
-
-## Built With
-
-OpenHands is built using a combination of powerful frameworks and libraries, providing a robust foundation for its
-development. Here are the key technologies used in the project:
-
-![FastAPI](https://img.shields.io/badge/FastAPI-black?style=for-the-badge) ![uvicorn](https://img.shields.io/badge/uvicorn-black?style=for-the-badge) ![LiteLLM](https://img.shields.io/badge/LiteLLM-black?style=for-the-badge) ![Docker](https://img.shields.io/badge/Docker-black?style=for-the-badge) ![Ruff](https://img.shields.io/badge/Ruff-black?style=for-the-badge) ![MyPy](https://img.shields.io/badge/MyPy-black?style=for-the-badge) ![LlamaIndex](https://img.shields.io/badge/LlamaIndex-black?style=for-the-badge) ![React](https://img.shields.io/badge/React-black?style=for-the-badge)
-
-Please note that the selection of these technologies is in progress, and additional technologies may be added or
-existing ones may be removed as the project evolves. We strive to adopt the most suitable and efficient tools to
-enhance the capabilities of OpenHands.
-
-## License
-
-Distributed under MIT [License](https://github.com/All-Hands-AI/OpenHands/blob/main/LICENSE).
--- a/docs/usage/agents.mdx
+++ b/docs/usage/agents.mdx
@ -1,26 +0,0 @@
---
-title: Main Agent and Capabilities
---
-
-## CodeActAgent
-
-### Description
-
-This agent implements the CodeAct idea ([paper](https://arxiv.org/abs/2402.01030), [tweet](https://twitter.com/xingyaow_/status/1754556835703751087)) that consolidates LLM agents’ **act**ions into a
-unified **code** action space for both _simplicity_ and _performance_.
-
-The conceptual idea is illustrated below. At each turn, the agent can:
-
-1. **Converse**: Communicate with humans in natural language to ask for clarification, confirmation, etc.
-2. **CodeAct**: Choose to perform the task by executing code
-
- Execute any valid Linux `bash` command
- Execute any valid `Python` code with [an interactive Python interpreter](https://ipython.org/). This is simulated through `bash` command, see plugin system below for more details.
-
-![image](https://github.com/All-Hands-AI/OpenHands/assets/38853559/92b622e3-72ad-4a61-8f41-8c040b6d5fb3)
-
-### Demo
-
-https://github.com/All-Hands-AI/OpenHands/assets/38853559/f592a192-e86c-4f48-ad31-d69282d5f6ac
-
-_Example of CodeActAgent with `gpt-4-turbo-2024-04-09` performing a data science task (linear regression)_.
--- a/docs/usage/architecture/backend.mdx
+++ b/docs/usage/architecture/backend.mdx
@ -1,103 +0,0 @@
---
-title: Backend Architecture
---
-
-
-This is a high-level overview of the system architecture. The system is divided into two main components: the frontend and the backend. The frontend is responsible for handling user interactions and displaying the results. The backend is responsible for handling the business logic and executing the agents.
-
-# System overview
-
-```mermaid
-flowchart LR
-  U["User"] --> FE["Frontend (SPA)"]
-  FE -- "HTTP/WS" --> BE["OpenHands Backend"]
-  BE --> ES["EventStream"]
-  BE --> ST["Storage"]
-  BE --> RT["Runtime Interface"]
-  BE --> LLM["LLM Providers"]
-
-  subgraph Runtime
-    direction TB
-    RT --> DRT["Docker Runtime"]
-    RT --> LRT["Local Runtime"]
-    RT --> RRT["Remote Runtime"]
-    DRT --> AES["Action Execution Server"]
-    LRT --> AES
-    RRT --> AES
-    AES --> Bash["Bash Session"]
-    AES --> Jupyter["Jupyter Plugin"]
-    AES --> Browser["BrowserEnv"]
-  end
-```
-
-This Overview is simplified to show the main components and their interactions. For a more detailed view of the backend architecture, see the Backend Architecture section below.
-
-# Backend Architecture
-
-
-```mermaid
-classDiagram
-  class Agent {
-    <<abstract>>
-    +sandbox_plugins: list[PluginRequirement]
-  }
-  class CodeActAgent {
-    +tools
-  }
-  Agent <|-- CodeActAgent
-
-  class EventStream
-  class Observation
-  class Action
-  Action --> Observation
-  Agent --> EventStream
-
-  class Runtime {
-    +connect()
-    +send_action_for_execution()
-  }
-  class ActionExecutionClient {
-    +_send_action_server_request()
-  }
-  class DockerRuntime
-  class LocalRuntime
-  class RemoteRuntime
-  Runtime <|-- ActionExecutionClient
-  ActionExecutionClient <|-- DockerRuntime
-  ActionExecutionClient <|-- LocalRuntime
-  ActionExecutionClient <|-- RemoteRuntime
-
-  class ActionExecutionServer {
-    +/execute_action
-    +/alive
-  }
-  class BashSession
-  class JupyterPlugin
-  class BrowserEnv
-  ActionExecutionServer --> BashSession
-  ActionExecutionServer --> JupyterPlugin
-  ActionExecutionServer --> BrowserEnv
-
-  Agent --> Runtime
-  Runtime ..> ActionExecutionServer : REST
-```
-
-<details>
-  <summary>Updating this Diagram</summary>
-  <div>
-    We maintain architecture diagrams inline with Mermaid in this MDX.
-
-    Guidance:
-    - Edit the Mermaid blocks directly (flowchart/classDiagram).
-    - Quote labels and edge text for GitHub preview compatibility.
-    - Keep relationships concise and reflect stable abstractions (agents, runtime client/server, plugins).
-    - Verify accuracy against code:
-      - openhands/runtime/impl/action_execution/action_execution_client.py
-      - openhands/runtime/impl/docker/docker_runtime.py
-      - openhands/runtime/impl/local/local_runtime.py
-      - openhands/runtime/action_execution_server.py
-      - openhands/runtime/plugins/*
-    - Build docs locally or view on GitHub to confirm diagrams render.
-
-  </div>
-</details>
--- a/docs/usage/architecture/runtime.mdx
+++ b/docs/usage/architecture/runtime.mdx
@ -1,170 +0,0 @@
---
-title: Runtime Architecture
---
-
-The OpenHands Docker 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?
-
-OpenHands needs to execute arbitrary code in a secure, isolated environment for several reasons:
-
-1. Security: Executing untrusted code can pose significant risks to the host system. A sandboxed environment prevents malicious code from accessing or modifying the host system's resources
-2. Consistency: A sandboxed environment ensures that code execution is consistent across different machines and setups, eliminating "it works on my machine" issues
-3. Resource Control: Sandboxing allows for better control over resource allocation and usage, preventing runaway processes from affecting the host system
-4. Isolation: Different projects or users can work in isolated environments without interfering with each other or the host system
-5. Reproducibility: Sandboxed environments make it easier to reproduce bugs and issues, as the execution environment is consistent and controllable
-
-## How does the Runtime work?
-
-The OpenHands Runtime system uses a client-server architecture implemented with Docker containers. Here's an overview of how it works:
-
-```mermaid
-graph TD
-    A[User-provided Custom Docker Image] --> B[OpenHands Backend]
-    B -->|Builds| C[OH Runtime Image]
-    C -->|Launches| D[Action Executor]
-    D -->|Initializes| E[Browser]
-    D -->|Initializes| F[Bash Shell]
-    D -->|Initializes| G[Plugins]
-    G -->|Initializes| L[Jupyter Server]
-
-    B -->|Spawn| H[Agent]
-    B -->|Spawn| I[EventStream]
-    I <--->|Execute Action to
-    Get Observation
-    via REST API
-    | D
-
-    H -->|Generate Action| I
-    I -->|Obtain Observation| H
-
-    subgraph "Docker Container"
-    D
-    E
-    F
-    G
-    L
-    end
-```
-
-1. User Input: The user provides a custom base Docker image
-2. Image Building: OpenHands builds a new Docker image (the "OH runtime image") based on the user-provided image. This new image includes OpenHands-specific code, primarily the "runtime client"
-3. Container Launch: When OpenHands starts, it launches a Docker container using the OH runtime image
-4. Action Execution Server Initialization: The action execution server initializes an `ActionExecutor` inside the container, setting up necessary components like a bash shell and loading any specified plugins
-5. Communication: The OpenHands backend (client: `openhands/runtime/impl/action_execution/action_execution_client.py`; runtimes: `openhands/runtime/impl/docker/docker_runtime.py`, `openhands/runtime/impl/local/local_runtime.py`) communicates with the action execution server over RESTful API, sending actions and receiving observations
-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:
-
- 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.
-
-Check out the [relevant code](https://github.com/All-Hands-AI/OpenHands/blob/main/openhands/runtime/utils/runtime_build.py) if you are interested in more details.
-
-### Image Tagging System
-
-OpenHands uses a three-tag system for its runtime images to balance reproducibility with flexibility.
-The tags are:
-
- **Versioned Tag**: `oh_v{openhands_version}_{base_image}` (e.g.: `oh_v0.9.9_nikolaik_s_python-nodejs_t_python3.12-nodejs22`)
- **Lock Tag**: `oh_v{openhands_version}_{16_digit_lock_hash}` (e.g.: `oh_v0.9.9_1234567890abcdef`)
- **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.
-
-This effectively gives a hash for the dependencies of Openhands independent of the source code.
-
-#### Versioned Tag - Most Generic
-
-This tag is a concatenation of openhands version and the base image name (transformed to fit in tag standard).
-
-#### Build Process
-
-When generating an image...
-
- **No re-build**: OpenHands first checks whether an image with the same **most specific source tag** exists. If there is such an image,
-  no build is performed - the existing image is used.
- **Fastest re-build**: OpenHands next checks whether an image with the **generic lock tag** exists. If there is such an image,
-  OpenHands builds a new image based upon it, bypassing all installation steps (like `poetry install` and
-  `apt-get`) except a final operation to copy the current source code. The new image is tagged with a
-  **source** tag only.
- **Ok-ish re-build**: If neither a **source** nor **lock** tag exists, an image will be built based upon the **versioned** tag image.
-  In versioned tag image, most dependencies should already been installed hence saving time.
- **Slowest re-build**: If all of the three tags don't exists, a brand new image is built based upon the base
-  image (Which is a slower operation). This new image is tagged with all the **source**, **lock**, and **versioned** tags.
-
-This tagging approach allows OpenHands to efficiently manage both development and production environments.
-
-1. Identical source code and Dockerfile always produce the same image (via hash-based tags)
-2. The system can quickly rebuild images when minor changes occur (by leveraging recent compatible images)
-3. The **lock** tag (e.g., `runtime:oh_v0.9.3_1234567890abcdef`) always points to the latest build for a particular base image, dependency, and OpenHands version combination
-
-## Volume mounts: named volumes and overlay
-
-OpenHands supports both bind mounts and Docker named volumes in SandboxConfig.volumes:
-
- Bind mount: "/abs/host/path:/container/path[:mode]"
- Named volume: "volume:`<name>`:/container/path[:mode]" or any non-absolute host spec treated as a named volume
-
-Overlay mode (copy-on-write layer) is supported for bind mounts by appending ":overlay" to the mode (e.g., ":ro,overlay").
-To enable overlay COW, set SANDBOX_VOLUME_OVERLAYS to a writable host directory; per-container upper/work dirs are created under it. If SANDBOX_VOLUME_OVERLAYS is unset, overlay mounts are skipped.
-
-Implementation references:
- openhands/runtime/impl/docker/docker_runtime.py (named volumes in _build_docker_run_args; overlay mounts in _process_overlay_mounts)
- openhands/core/config/sandbox_config.py (volumes field)
-
-
-## Runtime Plugin System
-
-The OpenHands Runtime supports a plugin system that allows for extending functionality and customizing the runtime environment. Plugins are initialized when the action execution server starts up inside the runtime.
-
-## Ports and URLs
-
- Host port allocation uses file-locked ranges for stability and concurrency:
-  - Main runtime port: find_available_port_with_lock on configured range
-  - VSCode port: SandboxConfig.sandbox.vscode_port if provided, else find_available_port_with_lock in VSCODE_PORT_RANGE
-  - App ports: two additional ranges for plugin/web apps
- DOCKER_HOST_ADDR (if set) adjusts how URLs are formed for LocalRuntime/Docker environments.
- VSCode URL is exposed with a connection token from the action execution server endpoint /vscode/connection_token and rendered as:
-  - Docker/Local: http://localhost:{port}/?tkn={token}&folder={workspace_mount_path_in_sandbox}
-  - RemoteRuntime: scheme://vscode-{host}/?tkn={token}&folder={workspace_mount_path_in_sandbox}
-
-References:
- openhands/runtime/impl/docker/docker_runtime.py (port ranges, locking, DOCKER_HOST_ADDR, vscode_url)
- openhands/runtime/impl/local/local_runtime.py (vscode_url factory)
- openhands/runtime/impl/remote/remote_runtime.py (vscode_url mapping)
- openhands/runtime/action_execution_server.py (/vscode/connection_token)
-
-
-Examples:
- Jupyter: openhands/runtime/plugins/jupyter/__init__.py (JupyterPlugin, Kernel Gateway)
- VS Code: openhands/runtime/plugins/vscode/* (VSCodePlugin, exposes tokenized URL)
- Agent Skills: openhands/runtime/plugins/agent_skills/*
-
-Key aspects of the plugin system:
-
-1. Plugin Definition: Plugins are defined as Python classes that inherit from a base `Plugin` class
-2. Plugin Registration: Available plugins are registered in `openhands/runtime/plugins/__init__.py` via `ALL_PLUGINS`
-3. Plugin Specification: Plugins are associated with `Agent.sandbox_plugins: list[PluginRequirement]`. Users can specify which plugins to load when initializing the runtime
-4. Initialization: Plugins are initialized asynchronously when the runtime starts and are accessible to actions
-5. Usage: Plugins extend capabilities (e.g., Jupyter for IPython cells); the server exposes any web endpoints (ports) via host port mapping
--- a/docs/usage/cloud/bitbucket-installation.mdx
+++ b/docs/usage/cloud/bitbucket-installation.mdx
@ -1,49 +0,0 @@
---
-title: Bitbucket Integration
-description: This guide walks you through the process of installing OpenHands Cloud for your Bitbucket repositories. Once
-  set up, it will allow OpenHands to work with your Bitbucket repository.
---
-
-## Prerequisites
-
- Signed in to [OpenHands Cloud](https://app.all-hands.dev) with [a Bitbucket account](/usage/cloud/openhands-cloud).
-
-## Adding Bitbucket Repository Access
-
-Upon signing into OpenHands Cloud with a Bitbucket account, OpenHands will have access to your repositories.
-
-## Working With Bitbucket Repos in Openhands Cloud
-
-After signing in with a Bitbucket account, use the `Open Repository` section to select the appropriate repository and
-branch you'd like OpenHands to work on. Then click on `Launch` to start the conversation!
-
-![Connect Repo](/static/img/connect-repo.png)
-
-## IP Whitelisting
-
-If your Bitbucket Cloud instance has IP restrictions, you'll need to whitelist the following IP addresses to allow
-OpenHands to access your repositories:
-
-### Core App IP
-```
-34.68.58.200
-```
-
-### Runtime IPs
-```
-34.10.175.217
-34.136.162.246
-34.45.0.142
-34.28.69.126
-35.224.240.213
-34.70.174.52
-34.42.4.87
-35.222.133.153
-34.29.175.97
-34.60.55.59
-```
-
-## Next Steps
-
- [Learn about the Cloud UI](/usage/cloud/cloud-ui).
- [Use the Cloud API](/usage/cloud/cloud-api) to programmatically interact with OpenHands.
--- a/docs/usage/cloud/cloud-api.mdx
+++ b/docs/usage/cloud/cloud-api.mdx
@ -1,122 +0,0 @@
---
-title: Cloud API
-description: OpenHands Cloud provides a REST API that allows you to programmatically interact with OpenHands.
-  This guide explains how to obtain an API key and use the API to start conversations and retrieve their status.
---
-
-For the available API endpoints, refer to the
-[OpenHands API Reference](https://docs.all-hands.dev/api-reference).
-
-## Obtaining an API Key
-
-To use the OpenHands Cloud API, you'll need to generate an API key:
-
-1. Log in to your [OpenHands Cloud](https://app.all-hands.dev) account.
-2. Navigate to the [Settings > API Keys](https://app.all-hands.dev/settings/api-keys) page.
-3. Click `Create API Key`.
-4. Give your key a descriptive name (Example: "Development" or "Production") and select `Create`.
-5. Copy the generated API key and store it securely. It will only be shown once.
-
-## API Usage Example
-
-### Starting a New Conversation
-
-To start a new conversation with OpenHands to perform a task,
-[you'll need to make a POST request to the conversation endpoint](/api-reference/new-conversation).
-
-<Tabs>
-  <Tab title="cURL">
-    ```bash
-    curl -X POST "https://app.all-hands.dev/api/conversations" \
-      -H "Authorization: Bearer YOUR_API_KEY" \
-      -H "Content-Type: application/json" \
-      -d '{
-        "initial_user_msg": "Check whether there is any incorrect information in the README.md file and send a PR to fix it if so.",
-        "repository": "yourusername/your-repo"
-      }'
-    ```
-  </Tab>
-  <Tab title="Python (with requests)">
-    ```python
-    import requests
-
-    api_key = "YOUR_API_KEY"
-    url = "https://app.all-hands.dev/api/conversations"
-
-    headers = {
-        "Authorization": f"Bearer {api_key}",
-        "Content-Type": "application/json"
-    }
-
-    data = {
-        "initial_user_msg": "Check whether there is any incorrect information in the README.md file and send a PR to fix it if so.",
-        "repository": "yourusername/your-repo"
-    }
-
-    response = requests.post(url, headers=headers, json=data)
-    conversation = response.json()
-
-    print(f"Conversation Link: https://app.all-hands.dev/conversations/{conversation['conversation_id']}")
-    print(f"Status: {conversation['status']}")
-    ```
-    </Tab>
-    <Tab title="TypeScript/JavaScript (with fetch)">
-        ```typescript
-    const apiKey = "YOUR_API_KEY";
-    const url = "https://app.all-hands.dev/api/conversations";
-
-    const headers = {
-      "Authorization": `Bearer ${apiKey}`,
-      "Content-Type": "application/json"
-    };
-
-    const data = {
-      initial_user_msg: "Check whether there is any incorrect information in the README.md file and send a PR to fix it if so.",
-      repository: "yourusername/your-repo"
-    };
-
-    async function startConversation() {
-      try {
-        const response = await fetch(url, {
-          method: "POST",
-          headers: headers,
-          body: JSON.stringify(data)
-        });
-
-        const conversation = await response.json();
-
-        console.log(`Conversation Link: https://app.all-hands.dev/conversations/${conversation.id}`);
-        console.log(`Status: ${conversation.status}`);
-
-        return conversation;
-      } catch (error) {
-        console.error("Error starting conversation:", error);
-      }
-    }
-
-    startConversation();
-    ```
-  </Tab>
-</Tabs>
-
-#### Response
-
-The API will return a JSON object with details about the created conversation:
-
-```json
-{
-  "status": "ok",
-  "conversation_id": "abc1234",
-}
-```
-
-You may receive an `AuthenticationError` if:
-
- You provided an invalid API key.
- You provided the wrong repository name.
- You don't have access to the repository.
-
-## Rate Limits
-
-If you have too many conversations running at once, older conversations will be paused to limit the number of concurrent conversations.
-If you're running into issues and need a higher limit for your use case, please contact us at [contact@all-hands.dev](mailto:contact@all-hands.dev).
--- a/docs/usage/cloud/cloud-ui.mdx
+++ b/docs/usage/cloud/cloud-ui.mdx
@ -1,54 +0,0 @@
---
-title: Cloud UI
-description: The Cloud UI provides a web interface for interacting with OpenHands. This page provides references on
- how to use the OpenHands Cloud UI.
---
-
-## Landing Page
-
-The landing page is where you can:
-
- [Select a GitHub repo](/usage/cloud/github-installation#working-with-github-repos-in-openhands-cloud),
-  [a GitLab repo](/usage/cloud/gitlab-installation#working-with-gitlab-repos-in-openhands-cloud) or
-  [a Bitbucket repo](/usage/cloud/bitbucket-installation#working-with-bitbucket-repos-in-openhands-cloud) to start working on.
- Launch an empty conversation using `New Conversation`.
- See `Suggested Tasks` for repositories that OpenHands has access to.
- See your `Recent Conversations`.
-
-## Settings
-
-Settings are divided across tabs, with each tab focusing on a specific area of configuration.
-
- `User`
-  - Change your email address.
- `Integrations`
-  - [Configure GitHub repository access](/usage/cloud/github-installation#modifying-repository-access) for OpenHands.
-  - [Install the OpenHands Slack app](/usage/cloud/slack-installation).
- `Application`
-  - Set your preferred language, notifications and other preferences.
-  - Toggle task suggestions on GitHub.
-  - Toggle Solvability Analysis.
-  - Set a maximum budget per conversation.
-  - Configure the username and email that OpenHands uses for commits.
- `LLM` (Available for [Pro subscription users](/usage/cloud/pro-subscription))
-  - Choose to use another LLM or use different models from the OpenHands provider.
- `Billing`
-  - Add credits for using the OpenHands provider.
-  - Cancel your `Pro subscription`.
- `Secrets`
-  - [Manage secrets](/usage/settings/secrets-settings).
- `API Keys`
-  - [Create API keys to work with OpenHands programmatically](/usage/cloud/cloud-api).
- `MCP`
-  - [Setup an MCP server](/usage/settings/mcp-settings)
-
-## Key Features
-
-For an overview of the key features available inside a conversation, please refer to the [Key Features](/usage/key-features)
-section of the documentation.
-
-## Next Steps
-
- [Install GitHub Integration](/usage/cloud/github-installation) to use OpenHands with your GitHub repositories.
- [Install GitLab Integration](/usage/cloud/gitlab-installation) to use OpenHands with your GitLab repositories.
- [Use the Cloud API](/usage/cloud/cloud-api) to programmatically interact with OpenHands.
--- a/docs/usage/cloud/github-installation.mdx
+++ b/docs/usage/cloud/github-installation.mdx
@ -1,79 +0,0 @@
---
-title: GitHub Integration
-description: This guide walks you through the process of installing OpenHands Cloud for your GitHub repositories. Once
-  set up, it will allow OpenHands to work with your GitHub repository through the Cloud UI or straight from GitHub!
---
-
-## Prerequisites
-
- Signed in to [OpenHands Cloud](https://app.all-hands.dev) with [a GitHub account](/usage/cloud/openhands-cloud).
-
-## Adding GitHub Repository Access
-
-You can grant OpenHands access to specific GitHub repositories:
-
-1. Click on `+ Add GitHub Repos` in the repository selection dropdown.
-2. Select your organization and choose the specific repositories to grant OpenHands access to.
-<Accordion title="OpenHands permissions">
-  - OpenHands requests short-lived tokens (8-hour expiration) with these permissions:
-     - Actions: Read and write
-     - 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:
-     - Permission granted for the repository
-     - User's GitHub permissions (owner/collaborator)
-</Accordion>
-
-3. Click `Install & Authorize`.
-
-## Modifying Repository Access
-
-You can modify GitHub repository access at any time by:
- Selecting `+ Add GitHub Repos` in the repository selection dropdown or
- Visiting the `Settings > Integrations` page and selecting `Configure GitHub Repositories`
-
-## Working With GitHub Repos in Openhands Cloud
-
-Once you've granted GitHub repository access, you can start working with your GitHub repository. Use the
-`Open Repository` section to select the appropriate repository and branch you'd like OpenHands to work on. Then click
-on `Launch` to start the conversation!
-
-![Connect Repo](/static/img/connect-repo.png)
-
-## Working on GitHub Issues and Pull Requests Using Openhands
-
-To allow OpenHands to work directly from GitHub directly, you must
-[give OpenHands access to your repository](/usage/cloud/github-installation#modifying-repository-access). Once access is
-given, you can use OpenHands by labeling the issue or by tagging `@openhands`.
-
-### Working with Issues
-
-On your repository, label an issue with `openhands` or add a message starting 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 PR.
-
-### Working with Pull Requests
-
-To get OpenHands to work on pull requests, mention `@openhands` in the comments to:
- Ask questions
- Request updates
- Get code explanations
-
-<Note>
-The `@openhands` mention functionality in pull requests only works if the pull request is both
-*to* and *from* a repository that you have added through the interface. This is because OpenHands needs appropriate
-permissions to access both repositories.
-</Note>
-
-
-## Next Steps
-
- [Learn about the Cloud UI](/usage/cloud/cloud-ui).
- [Use the Cloud API](/usage/cloud/cloud-api) to programmatically interact with OpenHands.
--- a/docs/usage/cloud/gitlab-installation.mdx
+++ b/docs/usage/cloud/gitlab-installation.mdx
@ -1,60 +0,0 @@
---
-title: GitLab Integration
-description: This guide walks you through the process of installing OpenHands Cloud for your GitLab repositories. Once
-  set up, it will allow OpenHands to work with your GitLab repository through the Cloud UI or straight from GitLab!.
---
-
-## Prerequisites
-
- Signed in to [OpenHands Cloud](https://app.all-hands.dev) with [a GitLab account](/usage/cloud/openhands-cloud).
-
-## Adding GitLab Repository Access
-
-Upon signing into OpenHands Cloud with a GitLab account, OpenHands will have access to your repositories.
-
-## Working With GitLab Repos in Openhands Cloud
-
-After signing in with a Gitlab account, use the `Open Repository` section to select the appropriate repository and
-branch you'd like OpenHands to work on. Then click on `Launch` to start the conversation!
-
-![Connect Repo](/static/img/connect-repo.png)
-
-## Using Tokens with Reduced Scopes
-
-OpenHands requests an API-scoped token during OAuth authentication. By default, this token is provided to the agent.
-To restrict the agent's permissions, [you can define a custom secret](/usage/settings/secrets-settings) `GITLAB_TOKEN`,
-which will override the default token assigned to the agent. While the high-permission API token is still requested
-and used for other components of the application (e.g. opening merge requests), the agent will not have access to it.
-
-## Working on GitLab Issues and Merge Requests Using Openhands
-
-<Note>
-This feature works for personal projects and is available for group projects with a
-[Premium or Ultimate tier subscription](https://docs.gitlab.com/user/project/integrations/webhooks/#group-webhooks).
-
-A webhook is automatically installed within a few minutes after the owner/maintainer of the project or group logs into
-OpenHands Cloud. If you decide to delete the webhook, then re-installing will require the support of All Hands AI but
-we are planning to improve this in a future release.
-</Note>
-
-Giving GitLab repository access to OpenHands also allows you to work on GitLab issues and merge requests directly.
-
-### Working with Issues
-
-On your repository, label an issue with `openhands` or add a message starting 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 merge 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 PR.
-
-### Working with Merge Requests
-
-To get OpenHands to work on merge requests, mention `@openhands` in the comments to:
- Ask questions
- Request updates
- Get code explanations
-
-## Next Steps
-
- [Learn about the Cloud UI](/usage/cloud/cloud-ui).
- [Use the Cloud API](/usage/cloud/cloud-api) to programmatically interact with OpenHands.
--- a/docs/usage/cloud/openhands-cloud.mdx
+++ b/docs/usage/cloud/openhands-cloud.mdx
@ -1,27 +0,0 @@
---
-title: Getting Started
-description: Getting started with OpenHands Cloud.
---
-
-## Accessing OpenHands Cloud
-
-OpenHands Cloud is the hosted cloud version of All Hands AI's OpenHands. To get started with OpenHands Cloud,
-visit [app.all-hands.dev](https://app.all-hands.dev).
-
-You'll be prompted to connect with your GitHub, GitLab or Bitbucket account:
-
-1. Click `Log in with GitHub`, `Log in with GitLab` or `Log in with Bitbucket`.
-2. Review the permissions requested by OpenHands and authorize the application.
-   - OpenHands will require certain permissions from your account. To read more about these permissions,
-     you can click the `Learn more` link on the authorization page.
-3. Review and accept the `terms of service` and select `Continue`.
-
-## Next Steps
-
-Once you've connected your account, you can:
-
- [Install GitHub Integration](/usage/cloud/github-installation) to use OpenHands with your GitHub repositories.
- [Install GitLab Integration](/usage/cloud/gitlab-installation) to use OpenHands with your GitLab repositories.
- [Install Bitbucket Integration](/usage/cloud/bitbucket-installation) to use OpenHands with your Bitbucket repositories.
- [Learn about the Cloud UI](/usage/cloud/cloud-ui).
- [Use the Cloud API](/usage/cloud/cloud-api) to programmatically interact with OpenHands.
--- a/docs/usage/cloud/pro-subscription.mdx
+++ b/docs/usage/cloud/pro-subscription.mdx
@ -1,50 +0,0 @@
---
-title: "Pro Subscription"
-description: "Learn about OpenHands Cloud Pro Subscription features and pricing."
---
-
-## Overview
-
-The OpenHands Pro Subscription unlocks additional features and better pricing when you run OpenHands conversations in
-OpenHands Cloud.
-
-## Base Features
-
-All users start on the Pay-as-you-go plan and have access to these base features when they sign up:
-
-* **Run multiple OpenHands conversations on OpenHands Cloud runtimes.**
-* **API keys to the OpenHands LLM provider for use in OpenHands CLI or when running OpenHands on your own.**
-* **$20 in initial OpenHands Cloud credits to get started.**
-* **Support for GitHub, GitLab, Bitbucket, Slack, and more.**
-
-## What you get with a Pro Subscription
-
-The $20/month Pro subscription covers the cost of runtime compute in OpenHands Cloud, plus enables the following
-features:
-
-* **Bring Your Own LLM Keys:** Bring your own API keys from OpenAI, Anthropic, Mistral, and other providers.
-* **Model Choice:** Unlocks access to OpenHands LLM provider models for use within OpenHands Cloud.
-* **No Markup Pricing on LLM usage:** When you use the OpenHands LLM provider in OpenHands Cloud, you pay for
-LLM usage at-cost (zero markup) based on API prices.
-
-## Plan Comparison
-
-Here are the key differences between Pay-as-you-go and Pro subscriptions:
-
-### When running OpenHands conversations in OpenHands Cloud
-|  | Pay-as-you-go | Pro Subscription |
-| :---- | ----- | ----- |
-| Monthly price | None \- no commitment | $20/month |
-| Can I bring my own LLM key? | No | ✅ Yes |
-| Do I pay for LLM usage? | ✅ Yes | ✅ Yes |
-| Can I select from different LLMs without bringing my own LLM key? | No \- defaults to Claude Sonnet 4 | ✅ Yes \- via OpenHands LLM provider <br/><br/>[*See models and pricing*](https://docs.all-hands.dev/usage/llms/openhands-llms#pricing) |
-| How much am I charged for LLM usage? | **Marked up pricing** \- 2x Claude Sonnet 4 API prices. *This markup helps cover the cost of runtime compute.* | **No markup** \- 1x API prices. *The $20 monthly subscription covers the cost of runtime compute.* |
-
-
-### When using the OpenHands LLM Provider outside of OpenHands Cloud
-The following applies to **both** the Pay-as-you-go and Pro subscription:
-|  | Pay-as-you-go or Pro Subscription |
-| :---- | :---- |
-| Do I have access to multiple models via the OpenHands LLM provider? | ✅ Yes <br/><br/> [*See models and pricing*](https://docs.all-hands.dev/usage/llms/openhands-llms#pricing) |
-| Can I generate and refresh OpenHands LLM API keys? | ✅ Yes |
-| How much am I charged for LLM usage when I use the OpenHands LLM provider in other AI coding tools?  | **No markup** \- pay 1x API prices <br/> [*See models and pricing*](https://docs.all-hands.dev/usage/llms/openhands-llms#pricing) <br/><br/> *Usage is deducted from your OpenHands Cloud credit balance.*  <br/><br/> *The OpenHands LLM provider is available to all OpenHands Cloud users, and LLM usage is billed at-cost (zero markup). Use these models with OpenHands CLI, running OpenHands on your own, or even other AI coding agents\! [Learn more.](https://www.all-hands.dev/blog/access-state-of-the-art-llm-models-at-cost-via-openhands-gui-and-cli)* |
--- a/docs/usage/cloud/project-management/jira-dc-integration.mdx
+++ b/docs/usage/cloud/project-management/jira-dc-integration.mdx
@ -1,126 +0,0 @@
---
-title: Jira Data Center Integration (Coming soon...)
-description: Complete guide for setting up Jira Data Center integration with OpenHands Cloud, including service account creation, personal access token generation, webhook configuration, and workspace integration setup.
---
-
-# Jira Data Center Integration
-
-## Platform Configuration
-
-### Step 1: Create Service Account
-
-1. **Access User Management**
-   - Log in to Jira Data Center as administrator
-   - Go to **Administration** > **User Management**
-
-2. **Create User**
-   - Click **Create User**
-   - Username: `openhands-agent`
-   - Full Name: `OpenHands Agent`
-   - Email: `openhands@yourcompany.com` (replace with your preferred service account email)
-   - Password: Set a secure password
-   - Click **Create**
-
-3. **Assign Permissions**
-   - Add user to appropriate groups
-   - Ensure access to relevant projects
-   - Grant necessary project permissions
-
-### Step 2: Generate API Token
-
-1. **Personal Access Tokens**
-   - Log in as the service account
-   - Go to **Profile** > **Personal Access Tokens**
-   - Click **Create token**
-   - Name: `OpenHands Cloud Integration`
-   - Expiry: Set appropriate expiration (recommend 1 year)
-   - Click **Create**
-   - **Important**: Copy and store the token securely
-
-### Step 3: Configure Webhook
-
-1. **Create Webhook**
-   - Go to **Administration** > **System** > **WebHooks**
-   - Click **Create a WebHook**
-   - **Name**: `OpenHands Cloud Integration`
-   - **URL**: `https://app.all-hands.dev/integration/jira-dc/events`
-   - Set a suitable webhook secret
-   - **Issue related events**: Select the following:
-     - Issue updated
-     - Comment created
-   - **JQL Filter**: Leave empty (or customize as needed)
-   - Click **Create**
-   - **Important**: Copy and store the webhook secret securely (you'll need this for workspace integration)
-
---
-
-## Workspace Integration
-
-### Step 1: Log in to OpenHands Cloud
-
-1. **Navigate and Authenticate**
-   - Go to [OpenHands Cloud](https://app.all-hands.dev/)
-   - Sign in with your Git provider (GitHub, GitLab, or BitBucket)
-   - **Important:** Make sure you're signing in with the same Git provider account that contains the repositories you want the OpenHands agent to work on.
-
-### Step 2: Configure Jira Data Center Integration
-
-1. **Access Integration Settings**
-   - Navigate to **Settings** > **Integrations**
-   - Locate **Jira Data Center** section
-
-2. **Configure Workspace**
-   - Click **Configure** button
-   - Enter your workspace name and click **Connect**
-      - If no integration exists, you'll be prompted to enter additional credentials required for the workspace integration:
-         - **Webhook Secret**: The webhook secret from Step 3 above
-         - **Service Account Email**: The service account email from Step 1 above
-         - **Service Account API Key**: The personal access token from Step 2 above
-         - Ensure **Active** toggle is enabled
-
-<Note>
-Workspace name is the host name of your Jira Data Center instance.
-
-Eg: http://jira.all-hands.dev/projects/OH/issues/OH-77
-
-Here the workspace name is **jira.all-hands.dev**.
-</Note>
-
-3. **Complete OAuth Flow**
-   - You'll be redirected to Jira Data Center to complete OAuth verification
-   - Grant the necessary permissions to verify your workspace access. If you have access to multiple workspaces, select the correct one that you initially provided
-   - If successful, you will be redirected back to the **Integrations** settings in the OpenHands Cloud UI
-
-### Managing Your Integration
-
-**Edit Configuration:**
- Click the **Edit** button next to your configured platform
- Update any necessary credentials or settings
- Click **Update** to apply changes
- You will need to repeat the OAuth flow as before
- **Important:** Only the original user who created the integration can see the edit view
-
-**Unlink Workspace:**
- In the edit view, click **Unlink** next to the workspace name
- This will deactivate your workspace link
- **Important:** If the original user who configured the integration chooses to unlink their integration, any users currently linked to that integration will also be unlinked, and the workspace integration will be deactivated. The integration can only be reactivated by the original user.
-
-### Screenshots
-
-<AccordionGroup>
-<Accordion title="Workspace link flow">
-![workspace-link.png](/static/img/jira-dc-user-link.png)
-</Accordion>
-
-<Accordion title="Workspace Configure flow">
-![workspace-link.png](/static/img/jira-dc-admin-configure.png)
-</Accordion>
-
-<Accordion title="Edit view as a user">
-![workspace-link.png](/static/img/jira-dc-user-unlink.png)
-</Accordion>
-
-<Accordion title="Edit view as the workspace creator">
-![workspace-link.png](/static/img/jira-dc-admin-edit.png)
-</Accordion>
-</AccordionGroup>
--- a/docs/usage/cloud/project-management/jira-integration.mdx
+++ b/docs/usage/cloud/project-management/jira-integration.mdx
@ -1,130 +0,0 @@
---
-title: Jira Cloud Integration (Coming soon...)
-description: Complete guide for setting up Jira Cloud integration with OpenHands Cloud, including service account creation, API token generation, webhook configuration, and workspace integration setup.
---
-
-# Jira Cloud Integration
-
-## Platform Configuration
-
-### Step 1: Create Service Account
-
-1. **Navigate to User Management**
-   - Go to [Atlassian Admin](https://admin.atlassian.com/)
-   - Select your organization
-   - Go to **Directory** > **Users**
-
-2. **Create OpenHands Service Account**
-   - Click **Service accounts**
-   - Click **Create a service account**
-   - Name: `OpenHands Agent`
-   - Click **Next**
-   - Select **User** role for Jira app
-   - Click **Create**
-
-### Step 2: Generate API Token
-
-1. **Access Service Account Configuration**
-   - Locate the created service account from above step and click on it
-   - Click **Create API token**
-   - Set the expiry to 365 days (maximum allowed value)
-   - Click **Next**
-   - In **Select token scopes** screen, filter by following values
-      - App: Jira
-      - Scope type: Classic
-      - Scope actions: Write, Read
-   - Select `read:jira-work` and `write:jira-work` scopes
-   - Click **Next**
-   - Review and create API token
-   - **Important**: Copy and securely store the token immediately
-
-### Step 3: Configure Webhook
-
-1. **Navigate to Webhook Settings**
-   - Go to **Jira Settings** > **System** > **WebHooks**
-   - Click **Create a WebHook**
-
-2. **Configure Webhook**
-   - **Name**: `OpenHands Cloud Integration`
-   - **Status**: Enabled
-   - **URL**: `https://app.all-hands.dev/integration/jira/events`
-   - **Issue related events**: Select the following:
-     - Issue updated
-     - Comment created
-   - **JQL Filter**: Leave empty (or customize as needed)
-   - Click **Create**
-   - **Important**: Copy and store the webhook secret securely (you'll need this for workspace integration)
-
---
-
-## Workspace Integration
-
-### Step 1: Log in to OpenHands Cloud
-
-1. **Navigate and Authenticate**
-   - Go to [OpenHands Cloud](https://app.all-hands.dev/)
-   - Sign in with your Git provider (GitHub, GitLab, or BitBucket)
-   - **Important:** Make sure you're signing in with the same Git provider account that contains the repositories you want the OpenHands agent to work on.
-
-### Step 2: Configure Jira Integration
-
-1. **Access Integration Settings**
-   - Navigate to **Settings** > **Integrations**
-   - Locate **Jira Cloud** section
-
-2. **Configure Workspace**
-   - Click **Configure** button
-   - Enter your workspace name and click **Connect**
-   - **Important:** Make sure you enter the full workspace name, eg: **yourcompany.atlassian.net**
-      - If no integration exists, you'll be prompted to enter additional credentials required for the workspace integration:
-         - **Webhook Secret**: The webhook secret from Step 3 above
-         - **Service Account Email**: The service account email from Step 1 above
-         - **Service Account API Key**: The API token from Step 2 above
-         - Ensure **Active** toggle is enabled
-
-<Note>
-Workspace name is the host name when accessing a resource in Jira Cloud.
-
-Eg: https://all-hands.atlassian.net/browse/OH-55
-
-Here the workspace name is **all-hands**.
-</Note>
-
-3. **Complete OAuth Flow**
-   - You'll be redirected to Jira Cloud to complete OAuth verification
-   - Grant the necessary permissions to verify your workspace access.
-   - If successful, you will be redirected back to the **Integrations** settings in the OpenHands Cloud UI
-
-### Managing Your Integration
-
-**Edit Configuration:**
- Click the **Edit** button next to your configured platform
- Update any necessary credentials or settings
- Click **Update** to apply changes
- You will need to repeat the OAuth flow as before
- **Important:** Only the original user who created the integration can see the edit view
-
-**Unlink Workspace:**
- In the edit view, click **Unlink** next to the workspace name
- This will deactivate your workspace link
- **Important:** If the original user who configured the integration chooses to unlink their integration, any users currently linked to that workspace integration will also be unlinked, and the workspace integration will be deactivated. The integration can only be reactivated by the original user.
-
-### Screenshots
-
-<AccordionGroup>
-<Accordion title="Workspace link flow">
-![workspace-link.png](/static/img/jira-user-link.png)
-</Accordion>
-
-<Accordion title="Workspace Configure flow">
-![workspace-link.png](/static/img/jira-admin-configure.png)
-</Accordion>
-
-<Accordion title="Edit view as a user">
-![workspace-link.png](/static/img/jira-user-unlink.png)
-</Accordion>
-
-<Accordion title="Edit view as the workspace creator">
-![workspace-link.png](/static/img/jira-admin-edit.png)
-</Accordion>
-</AccordionGroup>
--- a/docs/usage/cloud/project-management/linear-integration.mdx
+++ b/docs/usage/cloud/project-management/linear-integration.mdx
@ -1,130 +0,0 @@
---
-title: Linear Integration (Coming soon...)
-description: Complete guide for setting up Linear integration with OpenHands Cloud, including service account creation, API key generation, webhook configuration, and workspace integration setup.
---
-
-# Linear Integration
-
-## Platform Configuration
-
-### Step 1: Create Service Account
-
-1. **Access Team Settings**
-   - Log in to Linear as a team admin
-   - Go to **Settings** > **Members**
-
-2. **Invite Service Account**
-   - Click **Invite members**
-   - Email: `openhands@yourcompany.com` (replace with your preferred service account email)
-   - Role: **Member** (with appropriate team access)
-   - Send invitation
-
-3. **Complete Setup**
-   - Accept invitation from the service account email
-   - Complete profile setup
-   - Ensure access to relevant teams/workspaces
-
-### Step 2: Generate API Key
-
-1. **Access API Settings**
-   - Log in as the service account
-   - Go to **Settings** > **Security & access**
-
-2. **Create Personal API Key**
-   - Click **Create new key**
-   - Name: `OpenHands Cloud Integration`
-   - Scopes: Select the following:
-     - `Read` - Read access to issues and comments
-     - `Create comments` - Ability to create or update comments
-   - Select the teams you want to provide access to, or allow access for all teams you have permissions for
-   - Click **Create**
-   - **Important**: Copy and store the API key securely
-
-### Step 3: Configure Webhook
-
-1. **Access Webhook Settings**
-   - Go to **Settings** > **API** > **Webhooks**
-   - Click **New webhook**
-
-2. **Configure Webhook**
-   - **Label**: `OpenHands Cloud Integration`
-   - **URL**: `https://app.all-hands.dev/integration/linear/events`
-   - **Resource types**: Select:
-     - `Comment` - For comment events
-     - `Issue` - For issue updates (label changes)
-   - Select the teams you want to provide access to, or allow access for all public teams
-   - Click **Create webhook**
-   - **Important**: Copy and store the webhook secret securely (you'll need this for workspace integration)
-
---
-
-## Workspace Integration
-
-### Step 1: Log in to OpenHands Cloud
-
-1. **Navigate and Authenticate**
-   - Go to [OpenHands Cloud](https://app.all-hands.dev/)
-   - Sign in with your Git provider (GitHub, GitLab, or BitBucket)
-   - **Important:** Make sure you're signing in with the same Git provider account that contains the repositories you want the OpenHands agent to work on.
-
-### Step 2: Configure Linear Integration
-
-1. **Access Integration Settings**
-   - Navigate to **Settings** > **Integrations**
-   - Locate **Linear** section
-
-2. **Configure Workspace**
-   - Click **Configure** button
-   - Enter your workspace name and click **Connect**
-      - If no integration exists, you'll be prompted to enter additional credentials required for the workspace integration:
-         - **Webhook Secret**: The webhook secret from Step 3 above
-         - **Service Account Email**: The service account email from Step 1 above
-         - **Service Account API Key**: The API key from Step 2 above
-         - Ensure **Active** toggle is enabled
-
-<Note>
-Workspace name is the identifier after the host name when accessing a resource in Linear.
-
-Eg: https://linear.app/allhands/issue/OH-37
-
-Here the workspace name is **allhands**.
-</Note>
-
-3. **Complete OAuth Flow**
-   - You'll be redirected to Linear to complete OAuth verification
-   - Grant the necessary permissions to verify your workspace access. If you have access to multiple workspaces, select the correct one that you initially provided
-   - If successful, you will be redirected back to the **Integrations** settings in the OpenHands Cloud UI
-
-### Managing Your Integration
-
-**Edit Configuration:**
- Click the **Edit** button next to your configured platform
- Update any necessary credentials or settings
- Click **Update** to apply changes
- You will need to repeat the OAuth flow as before
- **Important:** Only the original user who created the integration can see the edit view
-
-**Unlink Workspace:**
- In the edit view, click **Unlink** next to the workspace name
- This will deactivate your workspace link
- **Important:** If the original user who configured the integration chooses to unlink their integration, any users currently linked to that integration will also be unlinked, and the workspace integration will be deactivated. The integration can only be reactivated by the original user.
-
-### Screenshots
-
-<AccordionGroup>
-<Accordion title="Workspace link flow">
-![workspace-link.png](/static/img/linear-user-link.png)
-</Accordion>
-
-<Accordion title="Workspace Configure flow">
-![workspace-link.png](/static/img/linear-admin-configure.png)
-</Accordion>
-
-<Accordion title="Edit view as a user">
-![workspace-link.png](/static/img/linear-admin-edit.png)
-</Accordion>
-
-<Accordion title="Edit view as the workspace creator">
-![workspace-link.png](/static/img/workspace-admin-edit.png)
-</Accordion>
-</AccordionGroup>
--- a/docs/usage/cloud/project-management/overview.mdx
+++ b/docs/usage/cloud/project-management/overview.mdx
@ -1,80 +0,0 @@
---
-title: Project Management Tool Integrations (Coming soon...)
-description: Overview of OpenHands Cloud integrations with project management platforms including Jira Cloud, Jira Data Center, and Linear. Learn about setup requirements, usage methods, and troubleshooting.
---
-
-# Project Management Tool Integrations
-
-## Overview
-
-OpenHands Cloud integrates with project management platforms (Jira Cloud, Jira Data Center, and Linear) to enable AI-powered task delegation. Users can invoke the OpenHands agent by:
- Adding `@openhands` in ticket comments
- Adding the `openhands` label to tickets
-
-## Prerequisites
-
-Integration requires two levels of setup:
-1. **Platform Configuration** - Administrative setup of service accounts and webhooks on your project management platform (see individual platform documentation below)
-2. **Workspace Integration** - Self-service configuration through the OpenHands Cloud UI to link your OpenHands account to the target workspace
-
-### Platform-Specific Setup Guides:
- [Jira Cloud Integration (Coming soon...)](./jira-integration.md)
- [Jira Data Center Integration (Coming soon...)](./jira-dc-integration.md)
- [Linear Integration (Coming soon...)](./linear-integration.md)
-
-## Usage
-
-Once both the platform configuration and workspace integration are completed, users can trigger the OpenHands agent within their project management platforms using two methods:
-
-### Method 1: Comment Mention
-Add a comment to any issue with `@openhands` followed by your task description:
-```
-@openhands Please implement the user authentication feature described in this ticket
-```
-
-### Method 2: Label-based Delegation
-Add the label `openhands` to any issue. The OpenHands agent will automatically process the issue based on its description and requirements.
-
-### Git Repository Detection
-
-The OpenHands agent needs to identify which Git repository to work with when processing your issues. Here's how to ensure proper repository detection:
-
-#### Specifying the Target Repository
-
-**Required:** Include the target Git repository in your issue description or comment to ensure the agent works with the correct codebase.
-
-**Supported Repository Formats:**
- Full HTTPS URL: `https://github.com/owner/repository.git`
- GitHub URL without .git: `https://github.com/owner/repository`
- Owner/repository format: `owner/repository`
-
-#### Platform-Specific Behavior
-
-**Linear Integration:** When GitHub integration is enabled for your Linear workspace with issue sync activated, the target repository is automatically detected from the linked GitHub issue. Manual specification is not required in this configuration.
-
-**Jira Integrations:** Always include the repository information in your issue description or `@openhands` comment to ensure proper repository detection.
-
-## Troubleshooting
-
-### Platform Configuration Issues
- **Webhook not triggering**: Verify the webhook URL is correct and the proper event types are selected (Comment, Issue updated)
- **API authentication failing**: Check API key/token validity and ensure required scopes are granted. If your current API token is expired, make sure to update it in the respective integration settings
- **Permission errors**: Ensure the service account has access to relevant projects/teams and appropriate permissions
-
-### Workspace Integration Issues
- **Workspace linking requests credentials**: If there are no active workspace integrations for the workspace you specified, you need to configure it first. Contact your platform administrator that you want to integrate with (eg: Jira, Linear)
- **Integration not found**: Verify the workspace name matches exactly and that platform configuration was completed first
- **OAuth flow fails**: Make sure that you're authorizing with the correct account with proper workspace access
-
-### General Issues
- **Agent not responding**: Check webhook logs in your platform settings and verify service account status
- **Authentication errors**: Verify Git provider permissions and OpenHands Cloud access
- **Agent fails to identify git repo**: Ensure you're signing in with the same Git provider account that contains the repositories you want OpenHands to work on
- **Partial functionality**: Ensure both platform configuration and workspace integration are properly completed
-
-### Getting Help
-For additional support, contact OpenHands Cloud support with:
- Your integration platform (Linear, Jira Cloud, or Jira Data Center)
- Workspace name
- Error logs from webhook/integration attempts
- Screenshots of configuration settings (without sensitive credentials)
--- a/docs/usage/cloud/slack-installation.mdx
+++ b/docs/usage/cloud/slack-installation.mdx
@ -1,89 +0,0 @@
---
-title: Slack Integration (Beta)
-description: This guide walks you through installing the OpenHands Slack app.
---
-
-<iframe
-  className="w-full aspect-video"
-  src="https://www.youtube.com/embed/hbloGmfZsJ4"
-  title="OpenHands Slack Integration Tutorial"
-  frameBorder="0"
-  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
-  allowFullScreen>
-</iframe>
-
-<Info>
-OpenHands utilizes a large language model (LLM), which may generate responses that are inaccurate or incomplete.
-While we strive for accuracy, OpenHands' outputs are not guaranteed to be correct, and we encourage users to
-validate critical information independently.
-</Info>
-
-## Prerequisites
-
- Access to OpenHands Cloud.
-
-## Installation Steps
-
-<AccordionGroup>
-<Accordion title="Install Slack App (only for Slack admins/owners)">
-
-  **This step is for Slack admins/owners**
-
-  1. Make sure you have permissions to install Apps to your workspace.
-  2. Click the button below to install OpenHands Slack App <a target="_blank" href="https://slack.com/oauth/v2/authorize?client_id=7477886716822.8729519890534&scope=app_mentions:read,channels:history,chat:write,groups:history,im:history,mpim:history,users:read&user_scope="><img alt="Add to Slack" height="40" width="139" src="https://platform.slack-edge.com/img/add_to_slack.png" srcSet="https://platform.slack-edge.com/img/add_to_slack.png 1x, https://platform.slack-edge.com/img/add_to_slack@2x.png 2x" /></a>
-  3. In the top right corner, select the workspace to install the OpenHands Slack app.
-  4. Review permissions and click allow.
-
-</Accordion>
-
-<Accordion title="Authorize Slack App (for all Slack workspace members)">
-
-  **Make sure your Slack workspace admin/owner has installed OpenHands Slack App first.**
-
-  Every user in the Slack workspace (including admins/owners) must link their OpenHands Cloud account to the OpenHands Slack App. To do this:
-  1. Visit the [Settings > Integrations](https://app.all-hands.dev/settings/integrations) page in OpenHands Cloud.
-  2. Click `Install OpenHands Slack App`.
-  3. In the top right corner, select the workspace to install the OpenHands Slack app.
-  4. Review permissions and click allow.
-
-  Depending on the workspace settings, you may need approval from your Slack admin to authorize the Slack App.
-
-</Accordion>
-
-</AccordionGroup>
-
-
-## Working With the Slack App
-
-To start a new conversation, you can mention `@openhands` in a new message or a thread inside any Slack channel.
-
-Once a conversation is started, all thread messages underneath it will be follow-up messages to OpenHands.
-
-To send follow-up messages for the same conversation, mention `@openhands` in a thread reply to the original message.
-You must be the user who started the conversation.
-
-## Example conversation
-
-### Start a new conversation, and select repo
-
-Conversation is started by mentioning `@openhands`.
-
-![slack-create-conversation.png](/static/img/slack-create-conversation.png)
-
-### See agent response and send follow up messages
-
-Initial request is followed up by mentioning `@openhands` in a thread reply.
-
-![slack-results-and-follow-up.png](/static/img/slack-results-and-follow-up.png)
-
-## Pro tip
-
-You can mention a repo name when starting a new conversation in the following formats
-
-1. "My-Repo" repo (e.g `@openhands in the openhands repo ...`)
-2. "All-Hands-AI/OpenHands" (e.g `@openhands in All-Hands-AI/OpenHands ...`)
-
-The repo match is case insensitive. If a repo name match is made, it will kick off the conversation.
-If the repo name partially matches against multiple repos, you'll be asked to select a repo from the filtered list.
-
-![slack-pro-tip.png](/static/img/slack-pro-tip.png)
--- a/docs/usage/configuration-options.mdx
+++ b/docs/usage/configuration-options.mdx
@ -1,437 +0,0 @@
---
-title: Configuration Options
-description: This page outlines all available configuration options for OpenHands, allowing you to customize its
-  behavior and integrate it with other services.
---
-
-<Note>
-   In GUI Mode, any settings applied through the Settings UI will take precedence.
-</Note>
-
-<Note>
-   **Looking for Environment Variables?** All configuration options can also be set using environment variables. 
-   See the [Environment Variables Reference](./environment-variables) for a complete list with examples.
-</Note>
-
-## Location of the `config.toml` File
-
-When running OpenHands in CLI, headless, or development mode, you can use a project-specific `config.toml` file for configuration, which must be
-located in the same directory from which the command is run. Alternatively, you may use the `--config-file` option to
-specify a different path to the `config.toml` file.
-
-## Core Configuration
-
-The core configuration options are defined in the `[core]` section of the `config.toml` file.
-
-Core configuration options can be set as environment variables by converting to uppercase. For example:
- `debug` → `DEBUG`
- `cache_dir` → `CACHE_DIR`
- `runtime` → `RUNTIME`
-
-### Workspace
- `workspace_base` **(Deprecated)**
-  - Type: `str`
-  - Default: `"./workspace"`
-  - Description: Base path for the workspace. **Deprecated: Use `SANDBOX_VOLUMES` instead.**
-
- `cache_dir`
-  - Type: `str`
-  - Default: `"/tmp/cache"`
-  - Description: Cache directory path
-
-### Debugging and Logging
- `debug`
-  - Type: `bool`
-  - Default: `false`
-  - Description: Enable debugging
-
- `disable_color`
-  - Type: `bool`
-  - Default: `false`
-  - Description: Disable color in terminal output
-
-### Trajectories
- `save_trajectory_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_path`
-  - Type: `str`
-  - Default: `"/tmp/file_store"`
-  - Description: File store path
-
- `file_store`
-  - Type: `str`
-  - Default: `"memory"`
-  - Description: File store type
-
- `file_uploads_allowed_extensions`
-  - Type: `list of str`
-  - Default: `[".*"]`
-  - Description: List of allowed file extensions for uploads
-
- `file_uploads_max_file_size_mb`
-  - Type: `int`
-  - Default: `0`
-  - Description: Maximum file size for uploads, in megabytes
-
- `file_uploads_restrict_file_types`
-  - Type: `bool`
-  - Default: `false`
-  - Description: Restrict file types for file uploads
-
- `file_uploads_allowed_extensions`
-  - Type: `list of str`
-  - Default: `[".*"]`
-  - Description: List of allowed file extensions for uploads
-
-### Task Management
- `max_budget_per_task`
-  - Type: `float`
-  - Default: `0.0`
-  - Description: Maximum budget per task (0.0 means no limit)
-
- `max_iterations`
-  - Type: `int`
-  - Default: `100`
-  - Description: Maximum number of iterations
-
-### Sandbox Configuration
- `volumes`
-  - Type: `str`
-  - Default: `None`
-  - Description: Volume mounts in the format 'host_path:container_path[:mode]', e.g. '/my/host/dir:/workspace:rw'. Multiple mounts can be specified using commas, e.g. '/path1:/workspace/path1,/path2:/workspace/path2:ro'
-
- `workspace_mount_path_in_sandbox` **(Deprecated)**
-  - Type: `str`
-  - Default: `"/workspace"`
-  - Description: Path to mount the workspace in the sandbox. **Deprecated: Use `SANDBOX_VOLUMES` instead.**
-
- `workspace_mount_path` **(Deprecated)**
-  - Type: `str`
-  - Default: `""`
-  - Description: Path to mount the workspace. **Deprecated: Use `SANDBOX_VOLUMES` instead.**
-
- `workspace_mount_rewrite` **(Deprecated)**
-  - Type: `str`
-  - 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. **Deprecated: Use `SANDBOX_VOLUMES` instead.**
-
-### Miscellaneous
- `run_as_openhands`
-  - Type: `bool`
-  - Default: `true`
-  - Description: Run as OpenHands
-
- `runtime`
-  - Type: `str`
-  - Default: `"docker"`
-  - Description: Runtime environment
-
- `default_agent`
-  - Type: `str`
-  - Default: `"CodeActAgent"`
-  - Description: Name of the default agent
-
- `jwt_secret`
-  - Type: `str`
-  - Default: `uuid.uuid4().hex`
-  - Description: JWT secret for authentication. Please set it to your own value.
-
-## LLM Configuration
-
-The LLM (Large Language Model) configuration options are defined in the `[llm]` section of the `config.toml` file.
-
-To use these with the docker command, pass in `-e LLM_<option>`. Example: `-e LLM_NUM_RETRIES`.
-
-All LLM configuration options can be set as environment variables by prefixing with `LLM_` and converting to uppercase. For example:
- `model` → `LLM_MODEL`
- `api_key` → `LLM_API_KEY`
- `base_url` → `LLM_BASE_URL`
-
-<Note>
-For development setups, you can also define custom named LLM configurations. See [Custom LLM Configurations](./llms/custom-llm-configs) for details.
-</Note>
-
-**AWS Credentials**
- `aws_access_key_id`
-  - Type: `str`
-  - Default: `""`
-  - Description: AWS access key ID
-
- `aws_region_name`
-  - Type: `str`
-  - Default: `""`
-  - Description: AWS region name
-
- `aws_secret_access_key`
-  - Type: `str`
-  - Default: `""`
-  - Description: AWS secret access key
-
-### API Configuration
- `api_key`
-  - Type: `str`
-  - Default: `None`
-  - Description: API key to use
-
- `base_url`
-  - Type: `str`
-  - Default: `""`
-  - Description: API base URL
-
- `api_version`
-  - Type: `str`
-  - Default: `""`
-  - Description: API version
-
- `input_cost_per_token`
-  - Type: `float`
-  - Default: `0.0`
-  - Description: Cost per input token
-
- `output_cost_per_token`
-  - Type: `float`
-  - Default: `0.0`
-  - Description: Cost per output token
-
-### Custom LLM Provider
- `custom_llm_provider`
-  - Type: `str`
-  - Default: `""`
-  - Description: Custom LLM provider
-
-
-### Message Handling
- `max_message_chars`
-  - Type: `int`
-  - Default: `30000`
-  - Description: The approximate maximum number of characters in the content of an event included in the prompt to the LLM. Larger observations are truncated.
-
- `max_input_tokens`
-  - Type: `int`
-  - Default: `0`
-  - Description: Maximum number of input tokens
-
- `max_output_tokens`
-  - Type: `int`
-  - Default: `0`
-  - Description: Maximum number of output tokens
-
-### Model Selection
- `model`
-  - Type: `str`
-  - Default: `"claude-3-5-sonnet-20241022"`
-  - Description: Model to use
-
-### Retrying
- `num_retries`
-  - Type: `int`
-  - Default: `8`
-  - Description: Number of retries to attempt
-
- `retry_max_wait`
-  - Type: `int`
-  - Default: `120`
-  - Description: Maximum wait time (in seconds) between retry attempts
-
- `retry_min_wait`
-  - Type: `int`
-  - Default: `15`
-  - Description: Minimum wait time (in seconds) between retry attempts
-
- `retry_multiplier`
-  - Type: `float`
-  - Default: `2.0`
-  - Description: Multiplier for exponential backoff calculation
-
-### Advanced Options
- `drop_params`
-  - Type: `bool`
-  - Default: `false`
-  - Description: Drop any unmapped (unsupported) params without causing an exception
-
- `caching_prompt`
-  - Type: `bool`
-  - Default: `true`
-  - Description: Using the prompt caching feature if provided by the LLM and supported
-
- `ollama_base_url`
-  - Type: `str`
-  - Default: `""`
-  - Description: Base URL for the OLLAMA API
-
- `temperature`
-  - Type: `float`
-  - Default: `0.0`
-  - Description: Temperature for the API
-
- `timeout`
-  - Type: `int`
-  - Default: `0`
-  - Description: Timeout for the API
-
- `top_p`
-  - Type: `float`
-  - Default: `1.0`
-  - Description: Top p for the API
-
- `disable_vision`
-  - Type: `bool`
-  - Default: `None`
-  - Description: If model is vision capable, this option allows to disable image processing (useful for cost reduction)
-
-## Agent Configuration
-
-The agent configuration options are defined in the `[agent]` and `[agent.<agent_name>]` sections of the `config.toml` file.
-
-Agent configuration options can be set as environment variables by prefixing with `AGENT_` and converting to uppercase. For example:
- `enable_browsing` → `AGENT_ENABLE_BROWSING`
- `function_calling` → `AGENT_FUNCTION_CALLING`
- `llm_config` → `AGENT_LLM_CONFIG`
-
-### LLM Configuration
- `llm_config`
-  - Type: `str`
-  - Default: `'your-llm-config-group'`
-  - Description: The name of the LLM config to use
-
-### ActionSpace Configuration
- `function_calling`
-  - Type: `bool`
-  - Default: `true`
-  - Description: Whether function calling is enabled
-
- `enable_browsing`
-  - Type: `bool`
-  - Default: `false`
-  - Description: Whether browsing delegate is enabled in the action space (only works with function calling)
-
- `enable_llm_editor`
-  - Type: `bool`
-  - Default: `false`
-  - Description: Whether LLM editor is enabled in the action space (only works with function calling)
-
- `enable_jupyter`
-  - Type: `bool`
-  - 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`
-  - Type: `bool`
-  - Default: `true`
-  - Description: Whether to use microagents at all
-
- `disabled_microagents`
-  - Type: `list of str`
-  - Default: `None`
-  - Description: A list of microagents to disable
-
-## Sandbox Configuration
-
-The sandbox configuration options are defined in the `[sandbox]` section of the `config.toml` file.
-
-
-
-To use these with the docker command, pass in `-e SANDBOX_<option>`. Example: `-e SANDBOX_TIMEOUT`.
-
-All sandbox configuration options can be set as environment variables by prefixing with `SANDBOX_` and converting to uppercase. For example:
- `timeout` → `SANDBOX_TIMEOUT`
- `user_id` → `SANDBOX_USER_ID`
- `base_container_image` → `SANDBOX_BASE_CONTAINER_IMAGE`
-
-### Execution
- `timeout`
-  - Type: `int`
-  - Default: `120`
-  - Description: Sandbox timeout in seconds
-
- `user_id`
-  - Type: `int`
-  - Default: `1000`
-  - Description: Sandbox user ID
-
-### Container Image
- `base_container_image`
-  - Type: `str`
-  - Default: `"nikolaik/python-nodejs:python3.12-nodejs22"`
-  - Description: Container image to use for the sandbox
-
-### 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
- `enable_auto_lint`
-  - Type: `bool`
-  - Default: `false`
-  - Description: Enable auto linting after editing
-
- `initialize_plugins`
-  - Type: `bool`
-  - Default: `true`
-  - Description: Whether to initialize plugins
-
-### Dependencies and Environment
- `runtime_extra_deps`
-  - Type: `str`
-  - Default: `""`
-  - Description: Extra dependencies to install in the runtime image
-
- `runtime_startup_env_vars`
-  - Type: `dict`
-  - Default: `{}`
-  - Description: Environment variables to set at the launch of the runtime
-
-### Evaluation
- `browsergym_eval_env`
-  - Type: `str`
-  - Default: `""`
-  - Description: BrowserGym environment to use for evaluation
-
-## Security Configuration
-
-The security configuration options are defined in the `[security]` section of the `config.toml` file.
-
-To use these with the docker command, pass in `-e SECURITY_<option>`. Example: `-e SECURITY_CONFIRMATION_MODE`.
-
-All security configuration options can be set as environment variables by prefixing with `SECURITY_` and converting to uppercase. For example:
- `confirmation_mode` → `SECURITY_CONFIRMATION_MODE`
- `security_analyzer` → `SECURITY_SECURITY_ANALYZER`
-
-### Confirmation Mode
- `confirmation_mode`
-  - Type: `bool`
-  - Default: `false`
-  - Description: Enable confirmation mode
-
-### Security Analyzer
- `security_analyzer`
-  - Type: `str`
-  - Default: `""`
-  - Description: The security analyzer to use
-
---
-
-> **Note**: Adjust configurations carefully, especially for memory, security, and network-related settings to ensure optimal performance and security.
-Please note that the configuration options may be subject to change in future versions of OpenHands. It's recommended to refer to the official documentation for the most up-to-date information.
--- a/docs/usage/confirmation-mode.mdx
+++ b/docs/usage/confirmation-mode.mdx
@ -1,52 +0,0 @@
-# Confirmation Mode and Security Analyzers
-
-OpenHands provides a security framework to help protect users from potentially risky actions through **Confirmation Mode** and **Security Analyzers**. This system analyzes agent actions and prompts users for confirmation when high-risk operations are detected.
-
-## Overview
-
-The security system consists of two main components:
-
-1. **Confirmation Mode**: When enabled, the agent will pause and ask for user confirmation before executing actions that are flagged as high-risk by the security analyzer.
-
-2. **Security Analyzers**: These are modules that evaluate the risk level of agent actions and determine whether user confirmation is required.
-
-## Configuration
-
-### CLI
-In CLI mode, confirmation is enabled by default. You will have an option to uses the LLM Analyzer and will automatically confirm LOW and MEDIUM risk actions, only prompting for HIGH risk actions.
-
-## Security Analyzers
-
-OpenHands includes multiple analyzers:
-
- **No Analyzer**: Do not use any security analyzer. The agent will prompt you to confirm *EVERY* action.
- **LLM Risk Analyzer** (default): Uses the same LLM as the agent to assess action risk levels
- **Invariant Analyzer**: Uses Invariant Labs' policy engine to evaluate action traces against security policies
-
-### LLM Risk Analyzer
-The default analyzer that leverages the agent's LLM to evaluate the security risk of each action. It considers the action type, parameters, and context to assign risk levels.
-
-### Invariant Analyzer
-An advanced analyzer that:
- Collects conversation events and parses them into a trace
- Checks the trace against an Invariant policy to classify risk (low, medium, high)
- Manages an Invariant server container automatically if needed
- Supports optional browsing-alignment and harmful-content checks
-
-## How It Works
-
-1. **Action Analysis**: When the agent wants to perform an action, the selected security analyzer evaluates its risk level.
-
-2. **Risk Assessment**: The analyzer returns one of three risk levels:
-   - **LOW**: Action proceeds without confirmation
-   - **MEDIUM**: Action proceeds without confirmation (may be configurable in future)
-   - **HIGH**: Action is paused, and user confirmation is requested
-
-3. **User Confirmation**: For high-risk actions, a confirmation dialog appears with:
-   - Description of the action
-   - Risk assessment explanation
-   - Options to approve or deny action
-
-4. **Action Execution**: Based on user response:
-   - **Approve**: Action proceeds as planned
-   - **Deny**: Action is cancelled
--- a/docs/usage/environment-variables.mdx
+++ b/docs/usage/environment-variables.mdx
@ -1,251 +0,0 @@
---
-title: Environment Variables Reference
-description: Complete reference of all environment variables supported by OpenHands
---
-
-This page provides a reference of environment variables that can be used to configure OpenHands. Environment variables provide an alternative to TOML configuration files and are particularly useful for containerized deployments, CI/CD pipelines, and cloud environments.
-
-## Environment Variable Naming Convention
-
-OpenHands follows a consistent naming pattern for environment variables:
-
- **Core settings**: Direct uppercase mapping (e.g., `debug` → `DEBUG`)
- **LLM settings**: Prefixed with `LLM_` (e.g., `model` → `LLM_MODEL`)
- **Agent settings**: Prefixed with `AGENT_` (e.g., `enable_browsing` → `AGENT_ENABLE_BROWSING`)
- **Sandbox settings**: Prefixed with `SANDBOX_` (e.g., `timeout` → `SANDBOX_TIMEOUT`)
- **Security settings**: Prefixed with `SECURITY_` (e.g., `confirmation_mode` → `SECURITY_CONFIRMATION_MODE`)
-
-## Core Configuration Variables
-
-These variables correspond to the `[core]` section in `config.toml`:
-
-| Environment Variable | Type | Default | Description |
-|---------------------|------|---------|-------------|
-| `DEBUG` | boolean | `false` | Enable debug logging throughout the application |
-| `DISABLE_COLOR` | boolean | `false` | Disable colored output in terminal |
-| `CACHE_DIR` | string | `"/tmp/cache"` | Directory path for caching |
-| `SAVE_TRAJECTORY_PATH` | string | `"./trajectories"` | Path to store conversation trajectories |
-| `REPLAY_TRAJECTORY_PATH` | string | `""` | Path to load and replay a trajectory file |
-| `FILE_STORE_PATH` | string | `"/tmp/file_store"` | File store directory path |
-| `FILE_STORE` | string | `"memory"` | File store type (`memory`, `local`, etc.) |
-| `FILE_UPLOADS_MAX_FILE_SIZE_MB` | integer | `0` | Maximum file upload size in MB (0 = no limit) |
-| `FILE_UPLOADS_RESTRICT_FILE_TYPES` | boolean | `false` | Whether to restrict file upload types |
-| `FILE_UPLOADS_ALLOWED_EXTENSIONS` | list | `[".*"]` | List of allowed file extensions for uploads |
-| `MAX_BUDGET_PER_TASK` | float | `0.0` | Maximum budget per task (0.0 = no limit) |
-| `MAX_ITERATIONS` | integer | `100` | Maximum number of iterations per task |
-| `RUNTIME` | string | `"docker"` | Runtime environment (`docker`, `local`, `cli`, etc.) |
-| `DEFAULT_AGENT` | string | `"CodeActAgent"` | Default agent class to use |
-| `JWT_SECRET` | string | auto-generated | JWT secret for authentication |
-| `RUN_AS_OPENHANDS` | boolean | `true` | Whether to run as the openhands user |
-| `VOLUMES` | string | `""` | Volume mounts in format `host:container[:mode]` |
-
-## LLM Configuration Variables
-
-These variables correspond to the `[llm]` section in `config.toml`:
-
-| Environment Variable | Type | Default | Description |
-|---------------------|------|---------|-------------|
-| `LLM_MODEL` | string | `"claude-3-5-sonnet-20241022"` | LLM model to use |
-| `LLM_API_KEY` | string | `""` | API key for the LLM provider |
-| `LLM_BASE_URL` | string | `""` | Custom API base URL |
-| `LLM_API_VERSION` | string | `""` | API version to use |
-| `LLM_TEMPERATURE` | float | `0.0` | Sampling temperature |
-| `LLM_TOP_P` | float | `1.0` | Top-p sampling parameter |
-| `LLM_MAX_INPUT_TOKENS` | integer | `0` | Maximum input tokens (0 = no limit) |
-| `LLM_MAX_OUTPUT_TOKENS` | integer | `0` | Maximum output tokens (0 = no limit) |
-| `LLM_MAX_MESSAGE_CHARS` | integer | `30000` | Maximum characters that will be sent to the model in observation content |
-| `LLM_TIMEOUT` | integer | `0` | API timeout in seconds (0 = no timeout) |
-| `LLM_NUM_RETRIES` | integer | `8` | Number of retry attempts |
-| `LLM_RETRY_MIN_WAIT` | integer | `15` | Minimum wait time between retries (seconds) |
-| `LLM_RETRY_MAX_WAIT` | integer | `120` | Maximum wait time between retries (seconds) |
-| `LLM_RETRY_MULTIPLIER` | float | `2.0` | Exponential backoff multiplier |
-| `LLM_DROP_PARAMS` | boolean | `false` | Drop unsupported parameters without error |
-| `LLM_CACHING_PROMPT` | boolean | `true` | Enable prompt caching if supported |
-| `LLM_DISABLE_VISION` | boolean | `false` | Disable vision capabilities for cost reduction |
-| `LLM_CUSTOM_LLM_PROVIDER` | string | `""` | Custom LLM provider name |
-| `LLM_OLLAMA_BASE_URL` | string | `""` | Base URL for Ollama API |
-| `LLM_INPUT_COST_PER_TOKEN` | float | `0.0` | Cost per input token |
-| `LLM_OUTPUT_COST_PER_TOKEN` | float | `0.0` | Cost per output token |
-| `LLM_REASONING_EFFORT` | string | `""` | Reasoning effort for o-series models (`low`, `medium`, `high`) |
-
-### AWS Configuration
-| Environment Variable | Type | Default | Description |
-|---------------------|------|---------|-------------|
-| `LLM_AWS_ACCESS_KEY_ID` | string | `""` | AWS access key ID |
-| `LLM_AWS_SECRET_ACCESS_KEY` | string | `""` | AWS secret access key |
-| `LLM_AWS_REGION_NAME` | string | `""` | AWS region name |
-
-## Agent Configuration Variables
-
-These variables correspond to the `[agent]` section in `config.toml`:
-
-| Environment Variable | Type | Default | Description |
-|---------------------|------|---------|-------------|
-| `AGENT_LLM_CONFIG` | string | `""` | Name of LLM config group to use |
-| `AGENT_FUNCTION_CALLING` | boolean | `true` | Enable function calling |
-| `AGENT_ENABLE_BROWSING` | boolean | `false` | Enable browsing delegate |
-| `AGENT_ENABLE_LLM_EDITOR` | boolean | `false` | Enable LLM-based editor |
-| `AGENT_ENABLE_JUPYTER` | boolean | `false` | Enable Jupyter integration |
-| `AGENT_ENABLE_HISTORY_TRUNCATION` | boolean | `true` | Enable history truncation |
-| `AGENT_ENABLE_PROMPT_EXTENSIONS` | boolean | `true` | Enable microagents (prompt extensions) |
-| `AGENT_DISABLED_MICROAGENTS` | list | `[]` | List of microagents to disable |
-
-## Sandbox Configuration Variables
-
-These variables correspond to the `[sandbox]` section in `config.toml`:
-
-| Environment Variable | Type | Default | Description |
-|---------------------|------|---------|-------------|
-| `SANDBOX_TIMEOUT` | integer | `120` | Sandbox timeout in seconds |
-| `SANDBOX_USER_ID` | integer | `1000` | User ID for sandbox processes |
-| `SANDBOX_BASE_CONTAINER_IMAGE` | string | `"nikolaik/python-nodejs:python3.12-nodejs22"` | Base container image |
-| `SANDBOX_USE_HOST_NETWORK` | boolean | `false` | Use host networking |
-| `SANDBOX_RUNTIME_BINDING_ADDRESS` | string | `"0.0.0.0"` | Runtime binding address |
-| `SANDBOX_ENABLE_AUTO_LINT` | boolean | `false` | Enable automatic linting |
-| `SANDBOX_INITIALIZE_PLUGINS` | boolean | `true` | Initialize sandbox plugins |
-| `SANDBOX_RUNTIME_EXTRA_DEPS` | string | `""` | Extra dependencies to install |
-| `SANDBOX_RUNTIME_STARTUP_ENV_VARS` | dict | `{}` | Environment variables for runtime |
-| `SANDBOX_BROWSERGYM_EVAL_ENV` | string | `""` | BrowserGym evaluation environment |
-| `SANDBOX_VOLUMES` | string | `""` | Volume mounts (replaces deprecated workspace settings) |
-| `SANDBOX_RUNTIME_CONTAINER_IMAGE` | string | `""` | Pre-built runtime container image |
-| `SANDBOX_KEEP_RUNTIME_ALIVE` | boolean | `false` | Keep runtime alive after session ends |
-| `SANDBOX_PAUSE_CLOSED_RUNTIMES` | boolean | `false` | Pause instead of stopping closed runtimes |
-| `SANDBOX_CLOSE_DELAY` | integer | `300` | Delay before closing idle runtimes (seconds) |
-| `SANDBOX_RM_ALL_CONTAINERS` | boolean | `false` | Remove all containers when stopping |
-| `SANDBOX_ENABLE_GPU` | boolean | `false` | Enable GPU support |
-| `SANDBOX_CUDA_VISIBLE_DEVICES` | string | `""` | Specify GPU devices by ID |
-| `SANDBOX_VSCODE_PORT` | integer | auto | Specific port for VSCode server |
-
-### Sandbox Environment Variables
-Variables prefixed with `SANDBOX_ENV_` are passed through to the sandbox environment:
-
-| Environment Variable | Description |
-|---------------------|-------------|
-| `SANDBOX_ENV_*` | Any variable with this prefix is passed to the sandbox (e.g., `SANDBOX_ENV_OPENAI_API_KEY`) |
-
-## Security Configuration Variables
-
-These variables correspond to the `[security]` section in `config.toml`:
-
-| Environment Variable | Type | Default | Description |
-|---------------------|------|---------|-------------|
-| `SECURITY_CONFIRMATION_MODE` | boolean | `false` | Enable confirmation mode for actions |
-| `SECURITY_SECURITY_ANALYZER` | string | `"llm"` | Security analyzer to use (`llm`, `invariant`) |
-| `SECURITY_ENABLE_SECURITY_ANALYZER` | boolean | `true` | Enable security analysis |
-
-## Debug and Logging Variables
-
-| Environment Variable | Type | Default | Description |
-|---------------------|------|---------|-------------|
-| `DEBUG` | boolean | `false` | Enable general debug logging |
-| `DEBUG_LLM` | boolean | `false` | Enable LLM-specific debug logging |
-| `DEBUG_RUNTIME` | boolean | `false` | Enable runtime debug logging |
-| `LOG_TO_FILE` | boolean | auto | Log to file (auto-enabled when DEBUG=true) |
-
-## Runtime-Specific Variables
-
-### Docker Runtime
-| Environment Variable | Type | Default | Description |
-|---------------------|------|---------|-------------|
-| `SANDBOX_VOLUME_OVERLAYS` | string | `""` | Volume overlay configurations |
-
-### Remote Runtime
-| Environment Variable | Type | Default | Description |
-|---------------------|------|---------|-------------|
-| `SANDBOX_API_KEY` | string | `""` | API key for remote runtime |
-| `SANDBOX_REMOTE_RUNTIME_API_URL` | string | `""` | Remote runtime API URL |
-
-### Local Runtime
-| Environment Variable | Type | Default | Description |
-|---------------------|------|---------|-------------|
-| `RUNTIME_URL` | string | `""` | Runtime URL for local runtime |
-| `RUNTIME_URL_PATTERN` | string | `""` | Runtime URL pattern |
-| `RUNTIME_ID` | string | `""` | Runtime identifier |
-| `LOCAL_RUNTIME_MODE` | string | `""` | Enable local runtime mode (`1` to enable) |
-
-## Integration Variables
-
-### GitHub Integration
-| Environment Variable | Type | Default | Description |
-|---------------------|------|---------|-------------|
-| `GITHUB_TOKEN` | string | `""` | GitHub personal access token |
-
-### Third-Party API Keys
-| Environment Variable | Type | Default | Description |
-|---------------------|------|---------|-------------|
-| `OPENAI_API_KEY` | string | `""` | OpenAI API key |
-| `ANTHROPIC_API_KEY` | string | `""` | Anthropic API key |
-| `GOOGLE_API_KEY` | string | `""` | Google API key |
-| `AZURE_API_KEY` | string | `""` | Azure API key |
-| `TAVILY_API_KEY` | string | `""` | Tavily search API key |
-
-## Server Configuration Variables
-
-These are primarily used when running OpenHands as a server:
-
-| Environment Variable | Type | Default | Description |
-|---------------------|------|---------|-------------|
-| `FRONTEND_PORT` | integer | `3000` | Frontend server port |
-| `BACKEND_PORT` | integer | `8000` | Backend server port |
-| `FRONTEND_HOST` | string | `"localhost"` | Frontend host address |
-| `BACKEND_HOST` | string | `"localhost"` | Backend host address |
-| `WEB_HOST` | string | `"localhost"` | Web server host |
-| `SERVE_FRONTEND` | boolean | `true` | Whether to serve frontend |
-
-## Deprecated Variables
-
-These variables are deprecated and should be replaced:
-
-| Environment Variable | Replacement | Description |
-|---------------------|-------------|-------------|
-| `WORKSPACE_BASE` | `SANDBOX_VOLUMES` | Use volume mounting instead |
-| `WORKSPACE_MOUNT_PATH` | `SANDBOX_VOLUMES` | Use volume mounting instead |
-| `WORKSPACE_MOUNT_PATH_IN_SANDBOX` | `SANDBOX_VOLUMES` | Use volume mounting instead |
-| `WORKSPACE_MOUNT_REWRITE` | `SANDBOX_VOLUMES` | Use volume mounting instead |
-
-## Usage Examples
-
-### Basic Setup with OpenAI
-```bash
-export LLM_MODEL="gpt-4o"
-export LLM_API_KEY="your-openai-api-key"
-export DEBUG=true
-```
-
-### Docker Deployment with Custom Volumes
-```bash
-export RUNTIME="docker"
-export SANDBOX_VOLUMES="/host/workspace:/workspace:rw,/host/data:/data:ro"
-export SANDBOX_TIMEOUT=300
-```
-
-### Remote Runtime Configuration
-```bash
-export RUNTIME="remote"
-export SANDBOX_API_KEY="your-remote-api-key"
-export SANDBOX_REMOTE_RUNTIME_API_URL="https://your-runtime-api.com"
-```
-
-### Security-Enhanced Setup
-```bash
-export SECURITY_CONFIRMATION_MODE=true
-export SECURITY_SECURITY_ANALYZER="llm"
-export DEBUG_RUNTIME=true
-```
-
-## Notes
-
-1. **Boolean Values**: Environment variables expecting boolean values accept `true`/`false`, `1`/`0`, or `yes`/`no` (case-insensitive).
-
-2. **List Values**: Lists should be provided as Python literal strings, e.g., `AGENT_DISABLED_MICROAGENTS='["microagent1", "microagent2"]'`.
-
-3. **Dictionary Values**: Dictionaries should be provided as Python literal strings, e.g., `SANDBOX_RUNTIME_STARTUP_ENV_VARS='{"KEY": "value"}'`.
-
-4. **Precedence**: Environment variables take precedence over TOML configuration files.
-
-5. **Docker Usage**: When using Docker, pass environment variables with the `-e` flag:
-   ```bash
-   docker run -e LLM_API_KEY="your-key" -e DEBUG=true openhands/openhands
-   ```
-
-6. **Validation**: Invalid environment variable values will be logged as errors and fall back to defaults.
--- a/docs/usage/faqs.mdx
+++ b/docs/usage/faqs.mdx
@ -1,96 +0,0 @@
---
-title: FAQs
-description: Frequently asked questions about OpenHands
-icon: question
---
-
-## Getting Started
-
-### I'm new to OpenHands. Where should I start?
-
-1. **Quick start**: Use [OpenHands Cloud](/usage/cloud/openhands-cloud) to get started quickly with
-  [GitHub](/usage/cloud/github-installation), [GitLab](/usage/cloud/gitlab-installation),
-  and [Slack](/usage/cloud/slack-installation) integrations.
-2. **Run on your own**: If you prefer to run it on your own hardware, follow our [Getting Started guide](/usage/local-setup).
-3. **First steps**: Read over the [start building guidelines](/usage/getting-started) and
-  [prompting best practices](/usage/prompting/prompting-best-practices) to learn the basics.
-
-### Can I use OpenHands for production workloads?
-
-OpenHands is meant to be run by a single user on their local workstation. It is not appropriate for multi-tenant
-deployments where multiple users share the same instance. There is no built-in authentication, isolation, or scalability.
-
-If you're interested in running OpenHands in a multi-tenant environment, check out the source-available,
-commercially-licensed [OpenHands Cloud Helm Chart](https://github.com/all-Hands-AI/OpenHands-cloud).
-
-<Info>
-Using OpenHands for work? We'd love to chat! Fill out
-[this short form](https://docs.google.com/forms/d/e/1FAIpQLSet3VbGaz8z32gW9Wm-Grl4jpt5WgMXPgJ4EDPVmCETCBpJtQ/viewform)
-to join our Design Partner program, where you'll get early access to commercial features and the opportunity to provide
-input on our product roadmap.
-</Info>
-
-## Safety and Security
-
-### It's doing stuff without asking, is that safe?
-
-**Generally yes, but with important considerations.** OpenHands runs all code in a secure, isolated Docker container
-(called a "sandbox") that is separate from your host system. However, the safety depends on your configuration:
-
-**What's protected:**
- Your host system files and programs (unless you mount them using [this feature](/usage/runtimes/docker#connecting-to-your-filesystem))
- Host system resources
- Other containers and processes
-
-**Potential risks to consider:**
- The agent can access the internet from within the container.
- If you provide credentials (API keys, tokens), the agent can use them.
- Mounted files and directories can be modified or deleted.
- Network requests can be made to external services.
-
-For detailed security information, see our [Runtime Architecture](/usage/architecture/runtime),
-[Security Configuration](/usage/configuration-options#security-configuration),
-and [Hardened Docker Installation](/usage/runtimes/docker#hardened-docker-installation) documentation.
-
-## File Storage and Access
-
-### Where are my files stored?
-
-Your files are stored in different locations depending on how you've configured OpenHands:
-
-**Default behavior (no file mounting):**
- Files created by the agent are stored inside the runtime Docker container.
- These files are temporary and will be lost when the container is removed.
- The agent works in the `/workspace` directory inside the runtime container.
-
-**When you mount your local filesystem (following [this](/usage/runtimes/docker#connecting-to-your-filesystem)):**
- Your local files are mounted into the container's `/workspace` directory.
- Changes made by the agent are reflected in your local filesystem.
- Files persist after the container is stopped.
-
-<Warning>
-Be careful when mounting your filesystem - the agent can modify or delete any files in the mounted directory.
-</Warning>
-
-## Development Tools and Environment
-
-### How do I get the dev tools I need?
-
-OpenHands comes with a basic runtime environment that includes Python and Node.js.
-It also has the ability to install any tools it needs, so usually it's sufficient to ask it to set up its environment.
-
-If you would like to set things up more systematically, you can:
- **Use setup.sh**: Add a [setup.sh file](/usage/prompting/repository#setup-script) file to
-  your repository, which will be run every time the agent starts.
- **Use a custom sandbox**: Use a [custom docker image](/usage/how-to/custom-sandbox-guide) to initialize the sandbox.
-
-### Something's not working. Where can I get help?
-
-1. **Search existing issues**: Check our [GitHub issues](https://github.com/All-Hands-AI/OpenHands/issues) to see if
-  others have encountered the same problem.
-2. **Join our community**: Get help from other users and developers:
-   - [Slack community](https://dub.sh/openhands)
-3. **Check our troubleshooting guide**: Common issues and solutions are documented in
-  [Troubleshooting](/usage/troubleshooting/troubleshooting).
-4. **Report bugs**: If you've found a bug, please [create an issue](https://github.com/All-Hands-AI/OpenHands/issues/new)
-  and fill in as much detail as possible.
--- a/docs/usage/feedback.mdx
+++ b/docs/usage/feedback.mdx
@ -1,50 +0,0 @@
-# ✅ Providing Feedback
-
-When using OpenHands, you will encounter cases where things work well, and others where they don't. We encourage you to
-provide feedback when you use OpenHands to help give feedback to the development team, and perhaps more importantly,
-create an open corpus of coding agent training examples -- Share-OpenHands!
-
-## 📝 How to Provide Feedback
-
-Providing feedback is easy! When you are using OpenHands, you can press the thumbs-up or thumbs-down button at any point
-during your interaction. You will be prompted to provide your email address
-(e.g. so we can contact you if we want to ask any follow-up questions), and you can choose whether you want to provide feedback publicly or privately.
-
-<iframe width="560" height="315" src="https://www.youtube.com/embed/5rFx-StMVV0?si=svo7xzp6LhGK_GXr" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
-
-## 📜 Data Use and Privacy
-
-### Data sharing settings
-
-When you submit data, you can submit it either publicly or privately.
-
- **Public** data will be distributed under the MIT License, like OpenHands itself, and can be used by the community to
-train and test models. Obviously, feedback that you can make public will be more valuable for the community as a whole,
-so when you are not dealing with sensitive information, we would encourage you to choose this option!
- **Private** data will be made available to the OpenHands team for the purpose of improving OpenHands.
-However, a link with a unique ID will still be created that you can share publicly with others.
-
-### Who collects and stores the data?
-
-The data is collected and stored by [All Hands AI](https://all-hands.dev), a company founded by OpenHands maintainers to support and improve OpenHands.
-
-### How will public data be released?
-
-The public data will be released when we hit fixed milestones, such as 1,000 public examples, 10,000 public examples, etc.
-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.
-
-### What if I want my data deleted?
-
-For data on the All Hands AI servers, we are happy to delete it at request:
-
-**One Piece of Data:** If you want one piece of data deleted, we will shortly be adding a mechanism to delete pieces of
-data using the link and password that is displayed on the interface when you submit data.
-
-**All Data:** If you would like all pieces of your data deleted, or you do not have the ID and password that you
-received when submitting the data, please contact `contact@all-hands.dev` from the email address that you registered
-when you originally submitted the data.
--- a/docs/usage/getting-started.mdx
+++ b/docs/usage/getting-started.mdx
@ -1,100 +0,0 @@
---
-title: Start Building
-description: So you've [run OpenHands](/usage/installation). Now what?
-icon: code
---
-
-OpenHands can assist with a range of engineering tasks. However, the technology is still new, and we’re far from having
-agents that can handle complex tasks independently. It’s important to understand what the agent does well and where it
-needs support.
-
-## Hello World
-
-Start with a simple "hello world" example. It might be trickier than it seems!
-
-Prompt the agent with:
-> Write a bash script hello.sh that prints "hello world!"
-
-The agent will write the script, set the correct permissions, and run it to check the output.
-
-You can continue prompting the agent to refine your code. This is a great way to
-work with agents. Start simple, and iterate.
-
-> Modify hello.sh so that it accepts a name as the first argument, but defaults to "world"
-
-You can also use any language you need. The agent may need time to set up the environment.
-
-> Please convert hello.sh to a Ruby script, and run it
-
-## Building From Scratch
-
-Agents excel at "greenfield" tasks, where they don’t need context about existing code and
-they can start from scratch.
-Begin with a simple task and iterate from there. Be specific about what you want and the tech stack.
-
-For example, we might build a TODO app:
-
-> Build a frontend-only TODO app in React. All state should be stored in localStorage.
-
-Once the basic structure is in place, continue refining:
-
-> Allow adding an optional due date to each task.
-
-Just like normal development, commit and push your code often.
-This way you can always revert back to an old state if the agent goes off track.
-You can ask the agent to commit and push for you:
-
-> Commit the changes and push them to a new branch called "feature/due-dates"
-
-## Adding New Code
-
-OpenHands is great at adding new code to an existing codebase.
-
-For instance, you can ask OpenHands to add a GitHub action that lints your code. It might check your codebase to
-determine the language, then create a new file in `./github/workflows/lint.yml`.
-
-> Add a GitHub action that lints the code in this repository.
-
-Some tasks need more context. While OpenHands can use commands like ls and grep to search, providing context upfront
-speeds things up and reduces token usage.
-
-> Modify ./backend/api/routes.js to add a new route that returns a list of all tasks.
-
-> Add a new React component to the ./frontend/components directory to display a list of Widgets.
-> It should use the existing Widget component.
-
-## Refactoring
-
-OpenHands does great at refactoring code in small chunks. Rather than rearchitecting the entire codebase,
-it's more effective to break up long files and functions or rename variables.
-
-> Rename all the single-letter variables in ./app.go.
-
-> Split the `build_and_deploy_widgets` function into two functions, `build_widgets` and `deploy_widgets` in widget.php.
-
-> Break ./api/routes.js into separate files for each route.
-
-## Bug Fixes
-
-OpenHands can help track down and fix bugs, but bug fixing can be tricky and often requires more context.
-It’s helpful if you’ve already diagnosed the issue and just need OpenHands to handle the logic.
-
-> The email field in the `/subscribe` endpoint is rejecting .io domains. Fix this.
-
-> The `search_widgets` function in ./app.py is doing a case-sensitive search. Make it case-insensitive.
-
-For bug fixing, test-driven development can be really useful. You can ask the agent to write a new test and iterate
-until the bug is fixed:
-
-> The `hello` function crashes on the empty string. Write a test that reproduces this bug, then fix the code so it passes.
-
-## More
-
-OpenHands can assist with nearly any coding task, but it takes some practice to get the best results.
-Keep these tips in mind:
-* Keep your tasks small.
-* Be specific.
-* Provide plenty of context.
-* Commit and push frequently.
-
-See [Prompting Best Practices](./prompting/prompting-best-practices) for more tips on how to get the most out of OpenHands.
--- a/docs/usage/how-to/cli-mode.mdx
+++ b/docs/usage/how-to/cli-mode.mdx
@ -1,231 +0,0 @@
---
-title: CLI
-description: The Command-Line Interface (CLI) provides a powerful interface that lets you engage with OpenHands
-  directly from your terminal.
---
-
-This mode is different from the [headless mode](/usage/how-to/headless-mode), which is non-interactive and better
-for scripting.
-
-<iframe
-  className="w-full aspect-video"
-  src="https://www.youtube.com/embed/PfvIx4y8h7w"
-  title="OpenHands CLI Tutorial"
-  frameBorder="0"
-  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
-  allowFullScreen>
-</iframe>
-
-## Getting Started
-
-### Running with Python
-
-**Note** - OpenHands requires Python version 3.12 or higher (Python 3.14 is not currently supported) and `uv` for the default `fetch` MCP server (more details below).
-
-#### Recommended: Using uv
-
-We recommend using [uv](https://docs.astral.sh/uv/) for the best OpenHands experience. uv provides better isolation from your current project's virtual environment and is required for OpenHands' default MCP servers.
-
-1. **Install uv** (if you haven't already):
-
-   See the [uv installation guide](https://docs.astral.sh/uv/getting-started/installation/) for the latest installation instructions for your platform.
-
-2. **Launch OpenHands CLI**:
-```bash
-uvx --python 3.12 --from openhands-ai openhands
-```
-
-<AccordionGroup>
-
-<Accordion title="Alternative: Traditional pip installation">
-
-If you prefer to use pip:
-
-```bash
-# Install OpenHands
-pip install openhands-ai
-```
-
-Note that you'll still need `uv` installed for the default MCP servers to work properly.
-
-</Accordion>
-
-<Accordion title="Create shell aliases for easy access across environments">
-
-Add the following to your shell configuration file (`.bashrc`, `.zshrc`, etc.):
-
-```bash
-# Add OpenHands aliases (recommended)
-alias openhands="uvx --python 3.12 --from openhands-ai openhands"
-alias oh="uvx --python 3.12 --from openhands-ai openhands"
-```
-
-After adding these lines, reload your shell configuration with `source ~/.bashrc` or `source ~/.zshrc` (depending on your shell).
-
-</Accordion>
-
-<Accordion title="Install OpenHands in home directory without global installation">
-
-You can install OpenHands in a virtual environment in your home directory using `uv`:
-
-```bash
-# Create a virtual environment in your home directory
-cd ~
-uv venv .openhands-venv --python 3.12
-
-# Install OpenHands in the virtual environment
-uv pip install -t ~/.openhands-venv/lib/python3.12/site-packages openhands-ai
-
-# Add the bin directory to your PATH in your shell configuration file
-echo 'export PATH="$PATH:$HOME/.openhands-venv/bin"' >> ~/.bashrc  # or ~/.zshrc
-
-# Reload your shell configuration
-source ~/.bashrc  # or source ~/.zshrc
-```
-
-</Accordion>
-
-</AccordionGroup>
-
-<Note>
-  If you have cloned the repository, you can also run the CLI directly using Poetry:
-
-  poetry run openhands
-</Note>
-
-3. Set your model, API key, and other preferences using the UI (or alternatively environment variables, below).
-
-This command opens an interactive prompt where you can type tasks or commands and get responses from OpenHands.
-The first time you run the CLI, it will take you through configuring the required LLM
-settings. These will be saved for future sessions.
-
-The conversation history will be saved in `~/.openhands/sessions`.
-
-### Running with Docker
-
-1. Set the following environment variables in your terminal:
-   - `SANDBOX_VOLUMES` to specify the directory you want OpenHands to access ([See using SANDBOX_VOLUMES for more info](../runtimes/docker#using-sandbox_volumes))
-   - `LLM_MODEL` - the LLM model to use (e.g. `export LLM_MODEL="anthropic/claude-sonnet-4-20250514"` or `export LLM_MODEL="anthropic/claude-sonnet-4-5-20250929"`)
-   - `LLM_API_KEY` - your API key (e.g. `export LLM_API_KEY="sk_test_12345"`)
-
-2. Run the following command:
-
-```bash
-docker run -it \
-    --pull=always \
-    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.58-nikolaik \
-    -e SANDBOX_USER_ID=$(id -u) \
-    -e SANDBOX_VOLUMES=$SANDBOX_VOLUMES \
-    -e LLM_API_KEY=$LLM_API_KEY \
-    -e LLM_MODEL=$LLM_MODEL \
-    -v /var/run/docker.sock:/var/run/docker.sock \
-    -v ~/.openhands:/.openhands \
-    --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.58 \
-    python -m openhands.cli.entry --override-cli-mode true
-```
-
-<Note>
-  If you used OpenHands before version 0.44, you may want to run `mv ~/.openhands-state ~/.openhands` to migrate your
-  conversation history to the new location.
-</Note>
-
-This launches the CLI in Docker, allowing you to interact with OpenHands.
-
-The `-e SANDBOX_USER_ID=$(id -u)` is passed to the Docker command to ensure the sandbox user matches the host user’s
-permissions. This prevents the agent from creating root-owned files in the mounted workspace.
-
-The conversation history will be saved in `~/.openhands/sessions`.
-
-## Interactive CLI Overview
-
-### What is CLI Mode?
-
-CLI mode enables real-time interaction with OpenHands agents. You can type natural language tasks, use interactive
-commands, and receive instant feedback—all inside your terminal.
-
-### Starting a Conversation
-
-When you start the CLI, you'll see a welcome message and a prompt (`>`). Enter your first task or type a command to
-begin your conversation.
-
-### Available Commands
-
-You can use the following commands whenever the prompt (`>`) is displayed:
-
-| Command      | Description                                                    |
-|--------------|----------------------------------------------------------------|
-| `/help`      | Show all available interactive commands and their descriptions |
-| `/exit`      | Exit the application                                           |
-| `/init`      | Initialize a new repository for agent exploration              |
-| `/status`    | Show conversation details and usage metrics                    |
-| `/new`       | Start a new conversation                                       |
-| `/settings`  | View and modify current LLM/agent settings                     |
-| `/resume`    | Resume the agent if paused                                     |
-| `/mcp`       | Manage MCP server configuration and view connection errors    |
-
-#### Settings and Configuration
-
-You can update your model, API key, agent, and other preferences interactively using the `/settings` command. Just
-follow the prompts:
-
- **Basic settings**: Choose a model/provider and enter your API key.
- **Advanced settings**: Set custom endpoints, enable or disable confirmation mode, and configure memory condensation.
-
-Settings can also be managed via the `config.toml` file in the current directory or `~/.openhands/config.toml`.
-
-#### Repository Initialization
-
-The `/init` command helps the agent understand your project by creating a `.openhands/microagents/repo.md` file with
-project details and structure. Use this when onboarding the agent to a new codebase.
-
-#### Agent Pause/Resume Feature
-
-You can pause the agent while it is running by pressing `Ctrl-P`. To continue the conversation after pausing, simply
-type `/resume` at the prompt.
-
-#### MCP Server Management
-
-To configure Model Context Protocol (MCP) servers, you can refer to the documentation on [MCP servers](../mcp) and use the `/mcp` command in the CLI. This command provides an interactive interface for managing Model Context Protocol (MCP) servers:
-
- **List configured servers**: View all currently configured MCP servers (SSE, Stdio, and SHTTP)
- **Add new server**: Interactively add a new MCP server with guided prompts
- **Remove server**: Remove an existing MCP server from your configuration
- **View errors**: Display any connection errors that occurred during MCP server startup
-
-This command modifies your `~/.openhands/config.toml` file and will prompt you to restart OpenHands for changes to take effect.
-
-By default, the [Fetch MCP server](https://github.com/modelcontextprotocol/servers/tree/main/src/fetch) will be automatically configured for OpenHands. You can also [enable search engine](../search-engine-setup) via the [Tavily MCP server](https://github.com/tavily-ai/tavily-mcp) by setting the `search_api_key` under the `[core]` section in the `~/.openhands/config.toml` file.
-
-##### Example of the `config.toml` file with MCP server configuration:
-
-```toml
-[core]
-search_api_key = "tvly-your-api-key-here"
-
-[mcp]
-stdio_servers = [
-    {name="fetch", command="uvx", args=["mcp-server-fetch"]},
-]
-
-sse_servers = [
-    # Basic SSE server with just a URL
-    "http://example.com:8080/sse",
-]
-
-shttp_servers = [
-    # Streamable HTTP server with API key authentication
-    {url="https://secure-example.com/mcp", api_key="your-api-key"}
-]
-```
-
-## Tips and Troubleshooting
-
- Use `/help` at any time to see the list of available commands.
- If you encounter permission issues, make sure your workspace directory is trusted and all required environment variables are set correctly.
- For advanced LLM configuration, use the advanced options in `/settings`.
- When confirmation mode is enabled, the CLI will prompt before sensitive operations. You can type `a` or `always` at the first confirmation prompt to automatically confirm subsequent actions for the current conversation.
- If you want to start over, use `/new` to begin a fresh conversation without restarting the CLI.
-
---
--- a/docs/usage/how-to/custom-sandbox-guide.mdx
+++ b/docs/usage/how-to/custom-sandbox-guide.mdx
@ -1,101 +0,0 @@
---
-title: Custom Sandbox
-description: This guide is for users that would like to use their own custom Docker image for the runtime.
-  For example, with certain tools or programming languages pre-installed.
---
-
-The sandbox is where the agent performs its tasks. Instead of running commands directly on your computer
-(which could be risky), the agent runs them inside a Docker container.
-
-The default OpenHands sandbox (`python-nodejs:python3.12-nodejs22`
-from [nikolaik/python-nodejs](https://hub.docker.com/r/nikolaik/python-nodejs)) comes with some packages installed such
-as python and Node.js but may need other software installed by default.
-
-You have two options for customization:
-
- Use an existing image with the required software.
- Create your own custom Docker image.
-
-If you choose the first option, you can skip the `Create Your Docker Image` section.
-
-## Create Your Docker Image
-
-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:
-
-```dockerfile
-FROM nikolaik/python-nodejs:python3.12-nodejs22
-
-# 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
-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](/usage/local-setup#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 \
-    ...
-```
-
-## Using the Development Workflow
-
-### Setup
-
-First, ensure you can run OpenHands by following the instructions in [Development.md](https://github.com/All-Hands-AI/OpenHands/blob/main/Development.md).
-
-### 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.
-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"
-```
-
-### Run
-
-Run OpenHands by running ```make run``` in the top level directory.
--- a/docs/usage/how-to/debugging.mdx
+++ b/docs/usage/how-to/debugging.mdx
@ -1,73 +0,0 @@
---
-title: Debugging
---
-
-The following is intended as a primer on debugging OpenHands for Development purposes.
-
-## Server / VSCode
-
-The following `launch.json` will allow debugging the agent, controller and server elements, but not the sandbox (Which runs inside docker). It will ignore any changes inside the `workspace/` directory:
-
-```
-{
-    "version": "0.2.0",
-    "configurations": [
-        {
-            "name": "OpenHands CLI",
-            "type": "debugpy",
-            "request": "launch",
-            "module": "openhands.cli.main",
-            "justMyCode": false
-        },
-        {
-            "name": "OpenHands WebApp",
-            "type": "debugpy",
-            "request": "launch",
-            "module": "uvicorn",
-            "args": [
-                "openhands.server.listen:app",
-                "--reload",
-                "--reload-exclude",
-                "${workspaceFolder}/workspace",
-                "--port",
-                "3000"
-            ],
-            "justMyCode": false
-        }
-    ]
-}
-```
-
-More specific debugging configurations which include more parameters may be specified:
-
-```
-    ...
-    {
-      "name": "Debug CodeAct",
-      "type": "debugpy",
-      "request": "launch",
-      "module": "openhands.core.main",
-      "args": [
-        "-t",
-        "Ask me what your task is.",
-        "-d",
-        "${workspaceFolder}/workspace",
-        "-c",
-        "CodeActAgent",
-        "-l",
-        "llm.o1",
-        "-n",
-        "prompts"
-      ],
-      "justMyCode": false
-    }
-    ...
-```
-
-Values in the snippet above can be updated such that:
-
-    * *t*: the task
-    * *d*: the openhands workspace directory
-    * *c*: the agent
-    * *l*: the LLM config (pre-defined in config.toml)
-    * *n*: session name (e.g. eventstream name)
--- a/docs/usage/how-to/development-overview.mdx
+++ b/docs/usage/how-to/development-overview.mdx
@ -1,71 +0,0 @@
---
-title: Development Overview
-description: 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`
--- a/docs/usage/how-to/evaluation-harness.mdx
+++ b/docs/usage/how-to/evaluation-harness.mdx
@ -1,280 +0,0 @@
---
-title: Evaluation Harness
---
-
-This guide provides an overview of how to integrate your own evaluation benchmark into the OpenHands framework.
-
-## Setup Environment and LLM Configuration
-
-Please follow instructions [here](https://github.com/All-Hands-AI/OpenHands/blob/main/Development.md) to setup your local development environment.
-OpenHands in development mode uses `config.toml` to keep track of most configurations.
-
-Here's an example configuration file you can use to define and use multiple LLMs:
-
-```toml
-[llm]
-# IMPORTANT: add your API key here, and set the model to the one you want to evaluate
-model = "claude-3-5-sonnet-20241022"
-api_key = "sk-XXX"
-
-[llm.eval_gpt4_1106_preview_llm]
-model = "gpt-4-1106-preview"
-api_key = "XXX"
-temperature = 0.0
-
-[llm.eval_some_openai_compatible_model_llm]
-model = "openai/MODEL_NAME"
-base_url = "https://OPENAI_COMPATIBLE_URL/v1"
-api_key = "XXX"
-temperature = 0.0
-```
-
-
-## How to use OpenHands in the command line
-
-OpenHands can be run from the command line using the following format:
-
-```bash
-poetry run python ./openhands/core/main.py \
-        -i <max_iterations> \
-        -t "<task_description>" \
-        -c <agent_class> \
-        -l <llm_config>
-```
-
-For example:
-
-```bash
-poetry run python ./openhands/core/main.py \
-        -i 10 \
-        -t "Write me a bash script that prints hello world." \
-        -c CodeActAgent \
-        -l llm
-```
-
-This command runs OpenHands with:
- A maximum of 10 iterations
- The specified task description
- Using the CodeActAgent
- With the LLM configuration defined in the `llm` section of your `config.toml` file
-
-## How does OpenHands work
-
-The main entry point for OpenHands is in `openhands/core/main.py`. Here's a simplified flow of how it works:
-
-1. Parse command-line arguments and load the configuration
-2. Create a runtime environment using `create_runtime()`
-3. Initialize the specified agent
-4. Run the controller using `run_controller()`, which:
-   - Attaches the runtime to the agent
-   - Executes the agent's task
-   - Returns a final state when complete
-
-The `run_controller()` function is the core of OpenHands's execution. It manages the interaction between the agent, the runtime, and the task, handling things like user input simulation and event processing.
-
-
-## Easiest way to get started: Exploring Existing Benchmarks
-
-We encourage you to review the various evaluation benchmarks available in the [`evaluation/benchmarks/` directory](https://github.com/All-Hands-AI/OpenHands/blob/main/evaluation/benchmarks) of our repository.
-
-To integrate your own benchmark, we suggest starting with the one that most closely resembles your needs. This approach can significantly streamline your integration process, allowing you to build upon existing structures and adapt them to your specific requirements.
-
-## How to create an evaluation workflow
-
-
-To create an evaluation workflow for your benchmark, follow these steps:
-
-1. Import relevant OpenHands utilities:
-   ```python
-    import openhands.agenthub
-    from evaluation.utils.shared import (
-        EvalMetadata,
-        EvalOutput,
-        make_metadata,
-        prepare_dataset,
-        reset_logger_for_multiprocessing,
-        run_evaluation,
-    )
-    from openhands.controller.state.state import State
-    from openhands.core.config import (
-        AppConfig,
-        SandboxConfig,
-        get_llm_config_arg,
-        parse_arguments,
-    )
-    from openhands.core.logger import openhands_logger as logger
-    from openhands.core.main import create_runtime, run_controller
-    from openhands.events.action import CmdRunAction
-    from openhands.events.observation import CmdOutputObservation, ErrorObservation
-    from openhands.runtime.runtime import Runtime
-   ```
-
-2. Create a configuration:
-   ```python
-   def get_config(instance: pd.Series, metadata: EvalMetadata) -> AppConfig:
-       config = AppConfig(
-           default_agent=metadata.agent_class,
-           runtime='docker',
-           max_iterations=metadata.max_iterations,
-           sandbox=SandboxConfig(
-               base_container_image='your_container_image',
-               enable_auto_lint=True,
-               timeout=300,
-           ),
-       )
-       config.set_llm_config(metadata.llm_config)
-       return config
-   ```
-
-3. Initialize the runtime and set up the evaluation environment:
-   ```python
-   def initialize_runtime(runtime: Runtime, instance: pd.Series):
-       # Set up your evaluation environment here
-       # For example, setting environment variables, preparing files, etc.
-       pass
-   ```
-
-4. Create a function to process each instance:
-   ```python
-   from openhands.utils.async_utils import call_async_from_sync
-   def process_instance(instance: pd.Series, metadata: EvalMetadata) -> EvalOutput:
-       config = get_config(instance, metadata)
-       runtime = create_runtime(config)
-       call_async_from_sync(runtime.connect)
-       initialize_runtime(runtime, instance)
-
-       instruction = get_instruction(instance, metadata)
-
-       state = run_controller(
-           config=config,
-           task_str=instruction,
-           runtime=runtime,
-           fake_user_response_fn=your_user_response_function,
-       )
-
-       # Evaluate the agent's actions
-       evaluation_result = await evaluate_agent_actions(runtime, instance)
-
-       return EvalOutput(
-           instance_id=instance.instance_id,
-           instruction=instruction,
-           test_result=evaluation_result,
-           metadata=metadata,
-           history=compatibility_for_eval_history_pairs(state.history),
-           metrics=state.metrics.get() if state.metrics else None,
-           error=state.last_error if state and state.last_error else None,
-       )
-   ```
-
-5. Run the evaluation:
-   ```python
-   metadata = make_metadata(llm_config, dataset_name, agent_class, max_iterations, eval_note, eval_output_dir)
-   output_file = os.path.join(metadata.eval_output_dir, 'output.jsonl')
-   instances = prepare_dataset(your_dataset, output_file, eval_n_limit)
-
-   await run_evaluation(
-       instances,
-       metadata,
-       output_file,
-       num_workers,
-       process_instance
-   )
-   ```
-
-This workflow sets up the configuration, initializes the runtime environment, processes each instance by running the agent and evaluating its actions, and then collects the results into an `EvalOutput` object. The `run_evaluation` function handles parallelization and progress tracking.
-
-Remember to customize the `get_instruction`, `your_user_response_function`, and `evaluate_agent_actions` functions according to your specific benchmark requirements.
-
-By following this structure, you can create a robust evaluation workflow for your benchmark within the OpenHands framework.
-
-
-## Understanding the `user_response_fn`
-
-The `user_response_fn` is a crucial component in OpenHands's evaluation workflow. It simulates user interaction with the agent, allowing for automated responses during the evaluation process. This function is particularly useful when you want to provide consistent, predefined responses to the agent's queries or actions.
-
-
-### Workflow and Interaction
-
-The correct workflow for handling actions and the `user_response_fn` is as follows:
-
-1. Agent receives a task and starts processing
-2. Agent emits an Action
-3. If the Action is executable (e.g., CmdRunAction, IPythonRunCellAction):
-   - The Runtime processes the Action
-   - Runtime returns an Observation
-4. If the Action is not executable (typically a MessageAction):
-   - The `user_response_fn` is called
-   - It returns a simulated user response
-5. The agent receives either the Observation or the simulated response
-6. Steps 2-5 repeat until the task is completed or max iterations are reached
-
-Here's a more accurate visual representation:
-
-```
-                 [Agent]
-                    |
-                    v
-               [Emit Action]
-                    |
-                    v
-            [Is Action Executable?]
-           /                       \
-         Yes                        No
-          |                          |
-          v                          v
-     [Runtime]               [user_response_fn]
-          |                          |
-          v                          v
-  [Return Observation]    [Simulated Response]
-           \                        /
-            \                      /
-             v                    v
-           [Agent receives feedback]
-                    |
-                    v
-         [Continue or Complete Task]
-```
-
-In this workflow:
-
- Executable actions (like running commands or executing code) are handled directly by the Runtime
- Non-executable actions (typically when the agent wants to communicate or ask for clarification) are handled by the `user_response_fn`
- The agent then processes the feedback, whether it's an Observation from the Runtime or a simulated response from the `user_response_fn`
-
-This approach allows for automated handling of both concrete actions and simulated user interactions, making it suitable for evaluation scenarios where you want to test the agent's ability to complete tasks with minimal human intervention.
-
-### Example Implementation
-
-Here's an example of a `user_response_fn` used in the SWE-Bench evaluation:
-
-```python
-def codeact_user_response(state: State | None) -> str:
-    msg = (
-        'Please continue working on the task on whatever approach you think is suitable.\n'
-        'If you think you have solved the task, please first send your answer to user through message and then <execute_bash> exit </execute_bash>.\n'
-        'IMPORTANT: YOU SHOULD NEVER ASK FOR HUMAN HELP.\n'
-    )
-
-    if state and state.history:
-        # check if the agent has tried to talk to the user 3 times, if so, let the agent know it can give up
-        user_msgs = [
-            event
-            for event in state.history
-            if isinstance(event, MessageAction) and event.source == 'user'
-        ]
-        if len(user_msgs) >= 2:
-            # let the agent know that it can give up when it has tried 3 times
-            return (
-                msg
-                + 'If you want to give up, run: <execute_bash> exit </execute_bash>.\n'
-            )
-    return msg
-```
-
-This function does the following:
-
-1. Provides a standard message encouraging the agent to continue working
-2. Checks how many times the agent has attempted to communicate with the user
-3. If the agent has made multiple attempts, it provides an option to give up
-
-By using this function, you can ensure consistent behavior across multiple evaluation runs and prevent the agent from getting stuck waiting for human input.
--- a/docs/usage/how-to/github-action.mdx
+++ b/docs/usage/how-to/github-action.mdx
@ -1,53 +0,0 @@
---
-title: OpenHands GitHub Action
-description: This guide explains how to use the OpenHands GitHub Action in your own projects.
---
-
-## Using the Action in the OpenHands Repository
-
-To use the OpenHands GitHub Action in a repository, you can:
-
-1. Create an issue in the repository.
-2. Add the `fix-me` label to the issue or leave a comment on the issue starting with `@openhands-agent`.
-
-The action will automatically trigger and attempt to resolve the issue.
-
-## Installing the Action in a New Repository
-
-To install the OpenHands GitHub Action in your own repository, follow
-the [README for the OpenHands Resolver](https://github.com/All-Hands-AI/OpenHands/blob/main/openhands/resolver/README.md).
-
-## Usage Tips
-
-### Iterative resolution
-
-1. Create an issue in the repository.
-2. Add the `fix-me` label to the issue, or leave a comment starting with `@openhands-agent`.
-3. Review the attempt to resolve the issue by checking the pull request.
-4. Follow up with feedback through general comments, review comments, or inline thread comments.
-5. Add the `fix-me` label to the pull request, or address a specific comment by starting with `@openhands-agent`.
-
-### Label versus Macro
-
- Label (`fix-me`): Requests OpenHands to address the **entire** issue or pull request.
- Macro (`@openhands-agent`): Requests OpenHands to consider only the issue/pull request description and **the specific comment**.
-
-## Advanced Settings
-
-### Add custom repository settings
-
-You can provide custom directions for OpenHands by following the [README for the resolver](https://github.com/All-Hands-AI/OpenHands/blob/main/openhands/resolver/README.md#providing-custom-instructions).
-
-### 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.
-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](/usage/how-to/custom-sandbox-guide))                                   | `OPENHANDS_BASE_CONTAINER_IMAGE="custom_image"`    |
-| `TARGET_BRANCH`                  | Variable | Merge to branch other than `main`                                                                   | `TARGET_BRANCH="dev"`                              |
-| `TARGET_RUNNER`                  | Variable | Target runner to execute the agent workflow (default ubuntu-latest)                                 | `TARGET_RUNNER="custom-runner"`                    |
--- a/docs/usage/how-to/gui-mode.mdx
+++ b/docs/usage/how-to/gui-mode.mdx
@ -1,257 +0,0 @@
---
-title: GUI
-description: High level overview of the Graphical User Interface (GUI) in OpenHands.
---
-
-## Prerequisites
-
- [OpenHands is running](/usage/local-setup)
-
-## Launching the GUI Server
-
-### Using the CLI Command
-
-You can launch the OpenHands GUI server directly from the command line using the `serve` command:
-
-<Callout type="info">
-**Prerequisites**: You need to have the [OpenHands CLI installed](/usage/how-to/cli-mode) first, OR have `uv` installed and run `uvx --python 3.12 --from openhands-ai openhands serve`. Otherwise, you'll need to use Docker directly (see the [Docker section](#using-docker-directly) below).
-</Callout>
-
-```bash
-openhands serve
-```
-
-This command will:
- Check that Docker is installed and running
- Pull the required Docker images
- Launch the OpenHands GUI server at http://localhost:3000
- Use the same configuration directory (`~/.openhands`) as the CLI mode
-
-#### Mounting Your Current Directory
-
-To mount your current working directory into the GUI server container, use the `--mount-cwd` flag:
-
-```bash
-openhands serve --mount-cwd
-```
-
-This is useful when you want to work on files in your current directory through the GUI. The directory will be mounted at `/workspace` inside the container.
-
-#### Using GPU Support
-
-If you have NVIDIA GPUs and want to make them available to the OpenHands container, use the `--gpu` flag:
-
-```bash
-openhands serve --gpu
-```
-
-This will enable GPU support via nvidia-docker, mounting all available GPUs into the container. You can combine this with other flags:
-
-```bash
-openhands serve --gpu --mount-cwd
-```
-
-**Prerequisites for GPU support:**
- NVIDIA GPU drivers must be installed on your host system
- [NVIDIA Container Toolkit (nvidia-docker2)](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html) must be installed and configured
-
-#### Requirements
-
-Before using the `openhands serve` command, ensure that:
- Docker is installed and running on your system
- You have internet access to pull the required Docker images
- Port 3000 is available on your system
-
-The CLI will automatically check these requirements and provide helpful error messages if anything is missing.
-
-### Using Docker Directly
-
-Alternatively, you can run the GUI server using Docker directly. See the [local setup guide](/usage/local-setup) for detailed Docker instructions.
-
-## Overview
-
-### Initial Setup
-
-1. Upon first launch, you'll see a settings popup.
-2. Select an `LLM Provider` and `LLM Model` from the dropdown menus. If the required model does not exist in the list,
-   select `see advanced settings`. Then toggle `Advanced` options and enter it with the correct prefix in the
-   `Custom Model` text box.
-3. Enter the corresponding `API Key` for your chosen provider.
-4. Click `Save Changes` to apply the settings.
-
-### Settings
-
-You can use the Settings page at any time to:
-
- Setup the LLM provider and model for OpenHands.
- [Setup the search engine](/usage/search-engine-setup).
- [Configure MCP servers](/usage/settings/mcp-settings).
- [Connect to GitHub](/usage/how-to/gui-mode#github-setup), [connect to GitLab](/usage/how-to/gui-mode#gitlab-setup)
-  and [connect to Bitbucket](/usage/how-to/gui-mode#bitbucket-setup).
- Set application settings like your preferred language, notifications and other preferences.
- [Manage custom secrets](/usage/settings/secrets-settings).
-
-#### GitHub Setup
-
-OpenHands automatically exports a `GITHUB_TOKEN` to the shell environment if provided:
-
-<AccordionGroup>
-<Accordion title="Setting Up a GitHub Token">
-
-  1. **Generate a Personal Access Token (PAT)**:
-   - On GitHub, go to Settings > Developer Settings > Personal Access Tokens > Tokens (classic).
-   - **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` and `Content = Read and Write` for branch creation)
-  2. **Enter Token in OpenHands**:
-   - In the Settings page, navigate to the `Integrations` tab.
-   - Paste your token in the `GitHub Token` field.
-   - Click `Save Changes` to apply the changes.
-
-  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**:
-   - Go to your token settings on GitHub.
-   - Look for the organization under `Organization access`.
-   - If required, click `Enable SSO` next to your organization.
-   - Complete the SSO authorization process.
-</Accordion>
-
-<Accordion title="Troubleshooting">
-  Common issues and solutions:
-
-  - **Token Not Recognized**:
-     - 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.
-</Accordion>
-</AccordionGroup>
-
-#### GitLab Setup
-
-OpenHands automatically exports a `GITLAB_TOKEN` to the shell environment if provided:
-
-<AccordionGroup>
-<Accordion title="Setting Up a GitLab Token">
-  1. **Generate a Personal Access Token (PAT)**:
-   - On GitLab, go to User Settings > Access Tokens.
-   - Create a new token with the following scopes:
-     - `api` (API access)
-     - `read_user` (Read user information)
-     - `read_repository` (Read repository)
-     - `write_repository` (Write repository)
-   - Set an expiration date or leave it blank for a non-expiring token.
-  2. **Enter Token in OpenHands**:
-   - In the Settings page, navigate to the `Integrations` tab.
-   - Paste your token in the `GitLab Token` field.
-   - Click `Save Changes` to apply the changes.
-
-  3. **(Optional): Restrict agent permissions**
-   - Create another PAT using Step 1 and exclude `api` scope .
-   - In the Settings page, in the `Secrets` tab, create a new secret `GITLAB_TOKEN` and paste your lower scope token.
-   - OpenHands will use the higher scope token, and the agent will use the lower scope token
-</Accordion>
-
-<Accordion title="Troubleshooting">
-  Common issues and solutions:
-
-  - **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.
-
-  - **Access Denied**:
-     - Verify project access permissions.
-     - Check if the token has the necessary scopes.
-     - For group/organization repositories, ensure you have proper access.
-</Accordion>
-</AccordionGroup>
-
-#### BitBucket Setup
-<AccordionGroup>
-<Accordion title="Setting Up a BitBucket Password">
-1. **Generate an App Password**:
-   - On BitBucket, go to Personal Settings > App Password.
-   - Create a new password with the following scopes:
-     - `account`: `read`
-     - `repository: write`
-     - `pull requests: write`
-     - `issues: write`
-   - App passwords are non-expiring token. OpenHands will migrate to using API tokens in the future.
-  2. **Enter Token in OpenHands**:
-   - In the Settings page, navigate to the `Integrations` tab.
-   - Paste your token in the `BitBucket Token` field.
-   - Click `Save Changes` to apply the changes.
-</Accordion>
-
-<Accordion title="Troubleshooting">
-  Common issues and solutions:
-
-  - **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.
-
-  - **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.
-</Accordion>
-
-</AccordionGroup>
-
-#### Advanced Settings
-
-The `Advanced` settings allows configuration of additional LLM settings. Inside the Settings page, under the `LLM` tab,
-toggle `Advanced` options to access additional settings.
-
- Custom Model: Use the `Custom Model` text box to manually enter a model. Make sure to use the correct prefix based on litellm docs.
- Base URL: Specify a `Base URL` if required by your LLM provider.
- Memory Condensation: The memory condenser manages the LLM's context by ensuring only the most important and relevant information is presented.
- Confirmation Mode: Enabling this mode will cause OpenHands to confirm an action with the user before performing it.
-
-### Key Features
-
-For an overview of the key features available inside a conversation, please refer to the [Key Features](/usage/key-features)
-section of the documentation.
-
-### Status Indicator
-
-The status indicator located in the bottom left of the screen will cycle through a number of states as a new conversation
-is loaded. Typically these include:
-
-* `Disconnected` : The frontend is not connected to any conversation.
-* `Connecting` : The frontend is connecting a websocket to a conversation.
-* `Building Runtime...` : The server is building a runtime. This is typically in development mode only while building a docker image.
-* `Starting Runtime...` : The server is starting a new runtime instance - probably a new docker container or remote runtime.
-* `Initializing Agent...` : The server is starting the agent loop (This step does not appear at present with Nested runtimes).
-* `Setting up workspace...` : Usually this means a `git clone ...` operation.
-* `Setting up git hooks` : Setting up the git pre commit hooks for the workspace.
-* `Agent is awaiting user input...` : Ready to go!
-
-## Tips for Effective Use
-
- Be specific in your requests to get the most accurate and helpful responses, as described in the [prompting best practices](../prompting/prompting-best-practices).
- Use one of the recommended models, as described in the [LLMs section](/usage/llms/llms).
-
-## Other Ways to Run Openhands
- [Run OpenHands in a scriptable headless mode.](/usage/how-to/headless-mode)
- [Run OpenHands with a friendly CLI.](/usage/how-to/cli-mode)
- [Run OpenHands on GitHub issues with a GitHub action.](/usage/how-to/github-action)
--- a/docs/usage/how-to/headless-mode.mdx
+++ b/docs/usage/how-to/headless-mode.mdx
@ -1,96 +0,0 @@
---
-title: Headless
-description: You can run OpenHands with a single command, without starting the web application. This makes it easy to
-  write scripts and automate tasks with OpenHands.
---
-
-This is different from [the CLI](./cli-mode), which is interactive, and better for active development.
-
-## With Python
-
-To run OpenHands in headless mode with Python:
-1. Ensure you have followed the [Development setup instructions](https://github.com/All-Hands-AI/OpenHands/blob/main/Development.md).
-2. Run the following command:
-```bash
-poetry run python -m openhands.core.main -t "write a bash script that prints hi"
-```
-
-You'll need to be sure to set your model, API key, and other settings via environment variables
-[or the `config.toml` file](https://github.com/All-Hands-AI/OpenHands/blob/main/config.template.toml).
-
-### Working with Repositories
-
-You can specify a repository for OpenHands to work with using `--selected-repo` or the `SANDBOX_SELECTED_REPO` environment variable:
-
-> **Note**: Currently, authentication tokens (GITHUB_TOKEN, GITLAB_TOKEN, or BITBUCKET_TOKEN) are required for all repository operations, including public repositories. This is a known limitation that may be addressed in future versions to allow tokenless access to public repositories.
-
-```bash
-# Using command-line argument
-poetry run python -m openhands.core.main \
-  --selected-repo "owner/repo-name" \
-  -t "analyze the codebase and suggest improvements"
-
-# Using environment variable
-export SANDBOX_SELECTED_REPO="owner/repo-name"
-poetry run python -m openhands.core.main -t "fix any linting issues"
-
-# Authentication tokens are currently required for ALL repository operations (public and private)
-# This includes GitHub, GitLab, and Bitbucket repositories
-export GITHUB_TOKEN="your-token"  # or GITLAB_TOKEN, BITBUCKET_TOKEN
-poetry run python -m openhands.core.main \
-  --selected-repo "owner/repo-name" \
-  -t "review the security implementation"
-
-# Using task files instead of inline task
-echo "Review the README and suggest improvements" > task.txt
-poetry run python -m openhands.core.main -f task.txt --selected-repo "owner/repo"
-```
-
-## With Docker
-
-Set environment variables and run the Docker command:
-
-```bash
-# Set required environment variables
-export SANDBOX_VOLUMES="/path/to/workspace:/workspace:rw"  # Format: host_path:container_path:mode
-export LLM_MODEL="anthropic/claude-sonnet-4-20250514"  # or "anthropic/claude-sonnet-4-5-20250929"
-export LLM_API_KEY="your-api-key"
-export SANDBOX_SELECTED_REPO="owner/repo-name"  # Optional: requires GITHUB_TOKEN
-export GITHUB_TOKEN="your-token"  # Required for repository operations
-
-# Run OpenHands
-docker run -it \
-    --pull=always \
-    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.58-nikolaik \
-    -e SANDBOX_USER_ID=$(id -u) \
-    -e SANDBOX_VOLUMES=$SANDBOX_VOLUMES \
-    -e LLM_API_KEY=$LLM_API_KEY \
-    -e LLM_MODEL=$LLM_MODEL \
-    -e SANDBOX_SELECTED_REPO=$SANDBOX_SELECTED_REPO \
-    -e GITHUB_TOKEN=$GITHUB_TOKEN \
-    -e LOG_ALL_EVENTS=true \
-    -v /var/run/docker.sock:/var/run/docker.sock \
-    -v ~/.openhands:/.openhands \
-    --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.58 \
-    python -m openhands.core.main -t "write a bash script that prints hi"
-```
-
-> **Note**: If you used OpenHands before version 0.44, run `mv ~/.openhands-state ~/.openhands` to migrate your conversation history.
-
-The `-e SANDBOX_USER_ID=$(id -u)` is passed to the Docker command to ensure the sandbox user matches the host user’s
-permissions. This prevents the agent from creating root-owned files in the mounted workspace.
-
-## Additional Options
-
-Common command-line options:
- `-d "/path/to/workspace"` - Set working directory
- `-f task.txt` - Load task from file
- `-i 50` - Set max iterations
- `-b 10.0` - Set budget limit (USD)
- `--no-auto-continue` - Interactive mode
-
-Run `poetry run python -m openhands.core.main --help` for all options.
-
-Set `export LOG_ALL_EVENTS=true` to log all agent actions.
--- a/docs/usage/how-to/websocket-connection.mdx
+++ b/docs/usage/how-to/websocket-connection.mdx
@ -1,179 +0,0 @@
---
-title: WebSocket Connection
---
-
-This guide explains how to connect to the OpenHands WebSocket API to receive real-time events and send actions to the agent.
-
-## Overview
-
-OpenHands uses [Socket.IO](https://socket.io/) for WebSocket communication between the client and server. The WebSocket connection allows you to:
-
-1. Receive real-time events from the agent
-2. Send user actions to the agent
-3. Maintain a persistent connection for ongoing conversations
-
-## Connecting to the WebSocket
-
-### Connection Parameters
-
-When connecting to the WebSocket, you need to provide the following query parameters:
-
- `conversation_id`: The ID of the conversation you want to join
- `latest_event_id`: The ID of the latest event you've received (use `-1` for a new connection)
- `providers_set`: (Optional) A comma-separated list of provider types
-
-### Connection Example
-
-Here's a basic example of connecting to the WebSocket using JavaScript:
-
-```javascript
-import { io } from "socket.io-client";
-
-const socket = io("http://localhost:3000", {
-  transports: ["websocket"],
-  query: {
-    conversation_id: "your-conversation-id",
-    latest_event_id: -1,
-    providers_set: "github,gitlab" // Optional
-  }
-});
-
-socket.on("connect", () => {
-  console.log("Connected to OpenHands WebSocket");
-});
-
-socket.on("oh_event", (event) => {
-  console.log("Received event:", event);
-});
-
-socket.on("connect_error", (error) => {
-  console.error("Connection error:", error);
-});
-
-socket.on("disconnect", (reason) => {
-  console.log("Disconnected:", reason);
-});
-```
-
-## Sending Actions to the Agent
-
-To send an action to the agent, use the `oh_user_action` event:
-
-```javascript
-// Send a user message to the agent
-socket.emit("oh_user_action", {
-  type: "message",
-  source: "user",
-  message: "Hello, can you help me with my project?"
-});
-```
-
-## Receiving Events from the Agent
-
-The server emits events using the `oh_event` event type. Here are some common event types you might receive:
-
- User messages (`source: "user", type: "message"`)
- Agent messages (`source: "agent", type: "message"`)
- File edits (`action: "edit"`)
- File writes (`action: "write"`)
- Command executions (`action: "run"`)
-
-Example event handler:
-
-```javascript
-socket.on("oh_event", (event) => {
-  if (event.source === "agent" && event.type === "message") {
-    console.log("Agent says:", event.message);
-  } else if (event.action === "run") {
-    console.log("Command executed:", event.args.command);
-    console.log("Result:", event.result);
-  }
-});
-```
-
-## Using Websocat for Testing
-
-[Websocat](https://github.com/vi/websocat) is a command-line tool for interacting with WebSockets. It's useful for testing your WebSocket connection without writing a full client application.
-
-### Installation
-
-```bash
-# On macOS
-brew install websocat
-
-# On Linux
-curl -L https://github.com/vi/websocat/releases/download/v1.11.0/websocat.x86_64-unknown-linux-musl > websocat
-chmod +x websocat
-sudo mv websocat /usr/local/bin/
-```
-
-### Connecting to the WebSocket
-
-```bash
-# Connect to the WebSocket and print all received messages
-echo "40{}" | \
-websocat "ws://localhost:3000/socket.io/?EIO=4&transport=websocket&conversation_id=your-conversation-id&latest_event_id=-1"
-```
-
-### Sending a Message
-
-```bash
-# Send a message to the agent
-echo '42["oh_user_action",{"type":"message","source":"user","message":"Hello, agent!"}]' | \
-websocat "ws://localhost:3000/socket.io/?EIO=4&transport=websocket&conversation_id=your-conversation-id&latest_event_id=-1"
-```
-
-### Complete Example with Websocat
-
-Here's a complete example of connecting to the WebSocket, sending a message, and receiving events:
-
-```bash
-# Start a persistent connection
-websocat -v "ws://localhost:3000/socket.io/?EIO=4&transport=websocket&conversation_id=your-conversation-id&latest_event_id=-1"
-
-# In another terminal, send a message
-echo '42["oh_user_action",{"type":"message","source":"user","message":"Can you help me with my project?"}]' | \
-websocat "ws://localhost:3000/socket.io/?EIO=4&transport=websocket&conversation_id=your-conversation-id&latest_event_id=-1"
-```
-
-## Event Structure
-
-Events sent and received through the WebSocket follow a specific structure:
-
-```typescript
-interface OpenHandsEvent {
-  id: string;           // Unique event ID
-  source: string;       // "user" or "agent"
-  timestamp: string;    // ISO timestamp
-  message?: string;     // For message events
-  type?: string;        // Event type (e.g., "message")
-  action?: string;      // Action type (e.g., "run", "edit", "write")
-  args?: any;           // Action arguments
-  result?: any;         // Action result
-}
-```
-
-## Best Practices
-
-1. **Handle Reconnection**: Implement reconnection logic in your client to handle network interruptions.
-2. **Track Event IDs**: Store the latest event ID you've received and use it when reconnecting to avoid duplicate events.
-3. **Error Handling**: Implement proper error handling for connection errors and failed actions.
-4. **Rate Limiting**: Avoid sending too many actions in a short period to prevent overloading the server.
-
-## Troubleshooting
-
-### Connection Issues
-
- Verify that the OpenHands server is running and accessible
- Check that you're providing the correct conversation ID
- Ensure your WebSocket URL is correctly formatted
-
-### Authentication Issues
-
- Make sure you have the necessary authentication cookies if required
- Verify that you have permission to access the specified conversation
-
-### Event Handling Issues
-
- Check that you're correctly parsing the event data
- Verify that your event handlers are properly registered
--- a/docs/usage/installation.mdx
+++ b/docs/usage/installation.mdx
@ -1,20 +0,0 @@
---
-title: Quick Start
-description: Running OpenHands Cloud or running on your own.
-icon: rocket
---
-
-<Tabs>
-  <Tab title="OpenHands Cloud">
-    The easiest way to get started with OpenHands is on OpenHands Cloud, which comes with $20 in free credits for new users.
-
-    To get started with OpenHands Cloud, visit [app.all-hands.dev](https://app.all-hands.dev).
-
-    For more information see [getting started with OpenHands Cloud.](/usage/cloud/openhands-cloud)
-  </Tab>
-  <Tab title="Running OpenHands on Your Own">
-    Run OpenHands on your local system and bring your own LLM and API key.
-
-    For more information see [running OpenHands on your own.](/usage/local-setup)
-  </Tab>
-</Tabs>
--- a/docs/usage/key-features.mdx
+++ b/docs/usage/key-features.mdx
@ -1,32 +0,0 @@
---
-title: Key Features
-icon: bars
---
-
-![overview](/static/img/oh-features.png)
-
-### Chat Panel
- Displays the conversation between the user and OpenHands.
- OpenHands explains its actions in this panel.
-
-### Changes
- Shows the file changes performed by OpenHands.
-
-### VS Code
- Embedded VS Code for browsing and modifying files.
- Can also be used to upload and download files.
-
-### Terminal
- A space for OpenHands and users to run terminal commands.
-
-### Jupyter
- Shows all Python commands that were executed by OpenHands.
- Particularly handy when using OpenHands to perform data visualization tasks.
-
-### App
- Displays the web server when OpenHands runs an application.
- Users can interact with the running application.
-
-### Browser
- Used by OpenHands to browse websites.
- The browser is non-interactive.
--- a/docs/usage/llms/azure-llms.mdx
+++ b/docs/usage/llms/azure-llms.mdx
@ -1,42 +0,0 @@
---
-title: Azure
-description: OpenHands uses LiteLLM to make calls to Azure's chat models. You can find their documentation on using Azure as a provider [here](https://docs.litellm.ai/docs/providers/azure).
---
-
-## 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):
-
-```
-LLM_API_VERSION="<api-version>"              # e.g. "2023-05-15"
-```
-
-Example:
-```bash
-docker run -it --pull=always \
-    -e LLM_API_VERSION="2023-05-15"
-    ...
-```
-
-Then in the OpenHands UI Settings under the `LLM` tab:
-
-<Note>
-You will need your ChatGPT deployment name which can be found on the deployments page in Azure. This is referenced as
-&lt;deployment-name&gt; below.
-</Note>
-
-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
-
-### Azure OpenAI Configuration
-
-When running OpenHands, set the following environment variable using `-e` in the
-[docker run command](../installation#running-openhands):
-
-```
-LLM_API_VERSION="<api-version>"                                    # e.g. "2024-02-15-preview"
-```
--- a/docs/usage/llms/custom-llm-configs.mdx
+++ b/docs/usage/llms/custom-llm-configs.mdx
@ -1,137 +0,0 @@
---
-title: Custom LLM Configurations
-description: 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.
-</Note>
--- a/docs/usage/llms/google-llms.mdx
+++ b/docs/usage/llms/google-llms.mdx
@ -1,30 +0,0 @@
---
-title: Google Gemini/Vertex
-description: OpenHands uses LiteLLM to make calls to Google's chat models. You can find their documentation on using Google as a provider -> [Gemini - Google AI Studio](https://docs.litellm.ai/docs/providers/gemini), [VertexAI - Google Cloud Platform](https://docs.litellm.ai/docs/providers/vertex)
---
-
-## Gemini - Google AI Studio Configs
-
-When running OpenHands, you'll need to set the following in the OpenHands UI through the Settings under the `LLM` tab:
- `LLM Provider` to `Gemini`
- `LLM Model` to the model you will be using.
-If the model is not in the list, enable `Advanced` options, and enter it in `Custom Model`
-(e.g. gemini/&lt;model-name&gt; like `gemini/gemini-2.0-flash`).
- `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):
-
-```
-GOOGLE_APPLICATION_CREDENTIALS="<json-dump-of-gcp-service-account-json>"
-VERTEXAI_PROJECT="<your-gcp-project-id>"
-VERTEXAI_LOCATION="<your-gcp-location>"
-```
-
-Then set the following in the OpenHands UI through the Settings under the `LLM` tab:
- `LLM Provider` to `VertexAI`
- `LLM Model` to the model you will be using.
-If the model is not in the list, enable `Advanced` options, and enter it in `Custom Model`
-(e.g. vertex_ai/&lt;model-name&gt;).
--- a/docs/usage/llms/groq.mdx
+++ b/docs/usage/llms/groq.mdx
@ -1,23 +0,0 @@
---
-title: Groq
-description: OpenHands uses LiteLLM to make calls to chat models on Groq. You can find their documentation on using Groq as a provider [here](https://docs.litellm.ai/docs/providers/groq).
---
-
-## Configuration
-
-When running OpenHands, you'll need to set the following in the OpenHands UI through the Settings under the `LLM` tab:
- `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,
-enable `Advanced` options, and enter it in `Custom Model` (e.g. groq/&lt;model-name&gt; 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).
-
-## Using Groq as an OpenAI-Compatible Endpoint
-
-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 under the `LLM` tab:
-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`
-   - `API Key` to your Groq API key
--- a/docs/usage/llms/litellm-proxy.mdx
+++ b/docs/usage/llms/litellm-proxy.mdx
@ -1,22 +0,0 @@
---
-title: LiteLLM Proxy
-description: OpenHands supports using the [LiteLLM proxy](https://docs.litellm.ai/docs/proxy/quick_start) to access various LLM providers.
---
-
-## Configuration
-
-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 under the `LLM` tab:
-  * 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
-
-## Supported Models
-
-The supported models depend on your LiteLLM proxy configuration. OpenHands supports any model that your LiteLLM proxy
-is configured to handle.
-
-Refer to your LiteLLM proxy configuration for the list of available models and their names.
--- a/Show More
+++ b/Show More