Spaces:
Runtime error
Runtime error
Commit History
-
Add complete API reference docs
Akash Yadavfb8468e
-
Harden monitor (gate all routes), swap ChatGPT backend to free-Chatgpt-api, clean repoβ
akashyadav758 +1: Claude Opus 4.8 (1M context)- Security: gate /, /api/*, /chrome.log behind API_KEY (Bearer / ?key= / apikey cookie). Previously these were public β anyone could view+drive the logged-in ChatGPT/Gemini/Google sessions. This was the likely "abusive" flag cause. - ChatGPT backend: replace chatgpt-free-api with the free-Chatgpt-api rewrite (drop-in: same 127.0.0.1:9225, same /api/chat + /v1/chat/completions). Update Dockerfile COPY paths. - Cleanup: drop leftover per-service Dockerfiles, redundant sub-READMEs, dev-only docs/test scripts, the prebuilt linux binary, and cdp_* debug scripts. - Docs: fix references, mark all routes key-gated, note the Space is now private. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>5c7f4b5 -
Fix: extension SW DidStartWorkerFail + hanging /gpt API β drop renderer-capping Chrome flagsβ
akashyadav758 +1: Claude Opus 4.8 (1M context)Remove --renderer-process-limit=1, --process-per-site and --no-zygote from the headless Chrome launch. Each of the 3 extensions runs an MV3 service worker (its own renderer) and the chat flow injects via chrome.scripting.executeScript; capping renderers to 1 starved them, so the GPT extension failed to start (DidStartWorkerFail) and never connected, and when it did start executeScript hung β making /gpt (and /gemini /flow) hang forever despite the browser UI chatting fine. HF cpu-basic has 16 GB (usage ~1-2 GB) so the memory flags weren't needed. Bump V8 heap 256->512MB. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>9d8e1f7 -
Add HOWTOUSE.md and docs/ for fast, error-free new setupβ
akashyadav758 +1: Claude Opus 4.8 (1M context)HOWTOUSE.md: per-service API endpoints + correct payloads + curl examples (key as placeholder, never the real value). docs/: architecture, persistence, api-gateway, deployment, troubleshooting β documents everything added on top of the base image so a fresh HF or Docker deploy doesn't hit the errors we already solved. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>8ea09fa