{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihdki7l7vvgyczfn7iq3gqlrvmkw3774l7wrozyx5c3r3yxdax3by",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mppyrr6evp42"
  },
  "path": "/t/space-bitguy07-browser-automation-studio-incorrectly-flagged-as-abusive-request-review/177390#post_1",
  "publishedAt": "2026-07-03T06:37:02.000Z",
  "site": "https://discuss.huggingface.co",
  "tags": [
    "Bitguy07/browser-automation-studio",
    "https://huggingface.co/spaces/Bitguy07/browser-automation-studio"
  ],
  "textContent": "**Subject:** Space “Bitguy07/browser-automation-studio” incorrectly flagged as abusive — request review\n\nHello Hugging Face Team,\n\nMy Space **Bitguy07/browser-automation-studio** is being automatically flagged as abusive and paused immediately after every successful build. The runtime API returns:\n\n\n    json\n\n\n{\n\n“stage”: “PAUSED”,\n\n“errorMessage”: “Flagged as abusive”\n\n}\n\n### **What the project is**\n\nThis is a **personal learning/research project** — a self-hosted AI browser automation platform. It lets me control a Chrome browser using natural language through a web UI or Telegram, powered by a local vision-language model (Qwen2.5-VL via Ollama).\n\nIt’s a single-user tool for my own use, not a service, not a proxy, and not a bot farm.\n\n### **Why I believe it was flagged**\n\nI understand my tech stack contains components that may trigger automated abuse detection:\n\n  * **Google Chrome + Xvfb** — needed to run a real browser for AI-driven web automation (the core purpose of the project)\n  * **x11vnc + noVNC + websockify** — used to provide a live view of what the browser is doing, so I can watch the AI navigate pages in real-time\n  * **Ollama** — runs a local Qwen2.5-VL-7B model inside the container for vision-language inference\n  * **Supervisord** — orchestrates these processes with staggered startup to stay within free-tier memory limits\n\n\n\nI am **not** :\n\n  * Running a crypto miner\n  * Reselling compute or remote desktop access\n  * Operating a scraping farm or bot network\n  * Tunneling traffic or proxying connections\n  * Violating any Hugging Face terms of service\n\n\n\n### **What I’ve tried**\n\n  * Verified the Docker build completes successfully (all layers cached)\n  * Confirmed the HEALTHCHECK returns 200 OK on `GET /health`\n  * Confirmed the root endpoint (`GET /`) returns 200 OK\n  * The Space transitions from `BUILDING` → `APP_STARTING` → `PAUSED` in approximately 3 seconds, with zero container logs — indicating the container is killed before any process can start\n  * Installed diagnostic tooling (hf-flight-recorder-agent) which confirmed no metrics are collected before the pause\n\n\n\n### **Request**\n\nCould you please **review and unflag** my Space? I’m happy to:\n\n  * Make the Space public if that helps with review\n  * Add any required disclaimers or documentation\n  * Modify the configuration if specific components are problematic\n  * Discuss the project’s purpose in more detail\n\n\n\n**Space URL:** https://huggingface.co/spaces/Bitguy07/browser-automation-studio\n**Username:** Bitguy07\n**Hardware:** cpu-basic (free tier)\n\nThank you for your time. I understand the need for abuse prevention and appreciate the free hosting — I just want to get my legitimate project running.\n\nBest regards,\nBitguy07",
  "title": "Space \"Bitguy07/browser-automation-studio\" incorrectly flagged as abusive — request review"
}