Skip to content

Agent Zero AI framework

Fix WebSocket CSRF validation failure on Chromium browsers over HTTPS

Paolo Calvi07f94ef4b5d7
diff --git a/run_ui.py b/run_ui.py
index e9b98dfb1..4f6049e08 100644
--- a/run_ui.py
+++ b/run_ui.py
@@ -52,7 +52,7 @@ WerkzeugRequest.max_form_memory_size = UPLOAD_LIMIT_BYTES
webapp.config.update(
JSON_SORT_KEYS=False,
SESSION_COOKIE_NAME="session_" + runtime.get_runtime_id(), # bind the session cookie name to runtime id to prevent session collision on same host
- SESSION_COOKIE_SAMESITE="Strict",
+ SESSION_COOKIE_SAMESITE="Lax",
SESSION_PERMANENT=True,
PERMANENT_SESSION_LIFETIME=timedelta(days=1),
MAX_CONTENT_LENGTH=int(os.getenv("FLASK_MAX_CONTENT_LENGTH", str(UPLOAD_LIMIT_BYTES))),
diff --git a/webui/js/api.js b/webui/js/api.js
index f79e9e834..df41a4845 100644
--- a/webui/js/api.js
+++ b/webui/js/api.js
@@ -219,7 +219,7 @@ export async function getCsrfToken() {
if (cookieRuntimeId) {
const _secureFlag =
window.location.protocol === "https:" ? "; Secure" : "";
- document.cookie = `csrf_token_${cookieRuntimeId}=${csrfToken}; SameSite=Strict; Path=/${_secureFlag}`;
+ document.cookie = `csrf_token_${cookieRuntimeId}=${csrfToken}; SameSite=Lax; Path=/${_secureFlag}`;
} else {
console.warn("CSRF runtime id missing; skipping cookie name binding.");
}