mirror of https://github.com/langbot-app/LangBot.git synced 2026-08-24 19:17:14 +00:00

Files

T

huanghuoguoguo 5b2826fa49 Add performance and reliability QA gates (#2283 )

* Add performance and reliability QA gates

* test(skills): prepare user path performance gate

* test(skills): add debug chat load gate

* test(skills): extend fake provider load profiles

* test(skills): add debug chat timing and isolation probes

* test(skills): clarify manual QA perf gates

2026-06-25 21:02:44 +08:00

1.9 KiB

Raw Blame History

Service Startup

Use this reference for LangBot backend/frontend readiness checks regardless of OS or browser-control method. Read skills/.env first and override those defaults with user-provided values or detected running services.

Variables

LANGBOT_REPO
LANGBOT_WEB_REPO
LANGBOT_BACKEND_URL
LANGBOT_FRONTEND_URL
LANGBOT_DEV_FRONTEND_URL

Backend

Start LangBot from the backend repo:

cd "$LANGBOT_REPO"
uv run main.py

Healthy startup includes:

Running on http://0.0.0.0:<backend-port>
Connected to plugin runtime.
Plugin langbot/local-agent initialized

Quick check:

curl -I --max-time 3 "$LANGBOT_BACKEND_URL/login"

If bin/lbs env doctor reports that LANGBOT_BACKEND_URL has no TCP listener, the backend is not running at the configured host and port. A reachable standalone frontend on LANGBOT_FRONTEND_URL does not prove backend readiness.

Prefer a visible terminal session while debugging backend startup. Detached background startup methods can hide early process exits in local agent runs; if you use one, immediately verify both the process and the listener:

ps -eo pid,cmd | rg 'main.py|uv run main|langbot'
ss -ltnp | rg ':5300'
curl -I --max-time 3 "$LANGBOT_BACKEND_URL/login"

Frontend

Start the new frontend from the web repo:

cd "$LANGBOT_WEB_REPO"
VITE_API_BASE_URL="$LANGBOT_BACKEND_URL" pnpm dev --host 0.0.0.0

Healthy startup includes:

Local: <frontend-url>

Quick check:

curl -I --max-time 3 "$LANGBOT_FRONTEND_URL"

If VITE_API_BASE_URL is missing, Vite still serves the page but frontend API calls may go to the frontend port instead of the backend port. That produces false browser failures in login, wizard, pipeline, and Debug Chat cases.

Completion Signal

Environment setup is not complete until the required frontend/backend URLs are reachable and the chosen browser-control path can open the WebUI.

1.9 KiB Raw Blame History