Converge integration

[david-rfai]

Changes

• Added support for running converge with rapidfireai start
• Pinned numpy version to 2.0.1 for compatibility with langchain-pinecone
• Pinned protobuf<6.0.0

Changelog Content

Additions

• Added support for running converge with rapidfireai start

Changes

• Pinned numpy version to 2.0.1 for compatibility with langchain-pinecone
• Pinned protobuf<6.0.0Include any issues addressed.

---

Note

Medium Risk
Modifies the multi-service startup/shutdown flow and introduces a new optional Converge process, which can affect service orchestration, port usage, and cleanup behavior.

Overview
Adds an opt-in Converge integration to rapidfireai start via a new --converge flag (and RF_CONVERGE_MODE env var) to start Converge instead of the legacy frontend, or to disable Converge entirely.

Updates setup/start.sh to validate Converge mode, detect rapidfireai-pro before starting Converge, manage Converge PIDs/logging, include Converge in shutdown cleanup, and surface converge.log in startup-failure summaries.

Pins evals dependencies by setting numpy==2.0.1 and adding protobuf<6.0.0, and expands rapidfireai doctor’s relevant package list (e.g., protobuf, langchain-pinecone, langchain-postgres).

^{Written by Cursor Bugbot for commit 9c8d15d. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

Autofix Details

Bugbot Autofix prepared fixes for both issues found in the latest run.

• ✅ Fixed: CLI overrides RF_CONVERGE_MODE environment variable silently
  • Changed --converge argument default from hardcoded 'all' to os.getenv('RF_CONVERGE_MODE', 'all') to respect environment variable.
• ✅ Fixed: Cleanup kills unrelated uvicorn processes with broad pattern
  • Scoped uvicorn pkill pattern from 'uvicorn.*main:app' to 'uvicorn.*converge' to avoid killing unrelated FastAPI processes.

Or push these changes by commenting:

@cursor push 6e2762362e

Preview (6e2762362e)

diff --git a/rapidfireai/cli.py b/rapidfireai/cli.py
--- a/rapidfireai/cli.py
+++ b/rapidfireai/cli.py
@@ -459,7 +459,7 @@
     parser.add_argument(
         "--converge",
         choices=["all", "none", "backend", "frontend"],
-        default="all",
+        default=os.getenv("RF_CONVERGE_MODE", "all"),
         help="Converge mode: all (default, start converge backend+frontend), none (use original frontend, do not start converge), backend (only converge backend), frontend (only converge frontend)",
     )
 

diff --git a/setup/start.sh b/setup/start.sh
--- a/setup/start.sh
+++ b/setup/start.sh
@@ -200,7 +200,7 @@
         pkill -f "python.*rapidfireai/frontend/server.py" 2>/dev/null || true
         # Stop Converge if it was running
         pkill -f "converge start" 2>/dev/null || true
-        pkill -f "uvicorn.*main:app" 2>/dev/null || true
+        pkill -f "uvicorn.*converge" 2>/dev/null || true
     fi
 
     print_success "All services stopped"

_{This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

Autofix Details

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Duplicate conflicting numpy constraints in requirements file
  • Removed the duplicate range constraint numpy>=1.26.4,<2.3 from line 30, keeping only the explicit numpy==2.0.1 pin for langchain-pinecone compatibility.

Or push these changes by commenting:

@cursor push 92929d66c6

Preview (92929d66c6)

diff --git a/setup/evals/requirements-local.txt b/setup/evals/requirements-local.txt
--- a/setup/evals/requirements-local.txt
+++ b/setup/evals/requirements-local.txt
@@ -27,7 +27,6 @@
 
 # Data Manipulation & Display
 unstructured>=0.18.15
-numpy>=1.26.4,<2.3
 
 # Other
 requests==2.32.5

_{This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}