Spaces:
Running
Running
| # Black Dragon AI - App Details | |
| ## Name | |
| Black Dragon AI | |
| ## Creator | |
| Sir Roky | |
| ## Type | |
| Local AI web app with Python backend and browser frontend. | |
| ## Current Local URL | |
| ```text | |
| http://127.0.0.1:8787/ | |
| ``` | |
| ## Main Features | |
| - Backend AI chat through backend-only API key | |
| - Persistent backend memory | |
| - Memory mode with view/save/clear controls | |
| - Automatic simple personal-fact memory for clear user statements | |
| - Creator identity lock | |
| - Safe PC assistant | |
| - Microsoft Defender scan integration | |
| - Suspicious-file fallback scanner | |
| - Voice input and voice output | |
| - Live talk mode | |
| - File/image attachment flow | |
| - Scan-before-accept upload flow for text, image, and binary files | |
| - Browser image lookup | |
| - Browser/web app shortcuts | |
| - Air Draw 2D-to-3D preview | |
| - Notes section with typed notes and mouse/finger drawing notes | |
| - Gaming Zone | |
| - RAG-style text ingestion and search | |
| - Compliance-style hash logs | |
| - Prompt-injection firewall | |
| - PII masking | |
| - Feature registry for enterprise roadmap | |
| ## Backend Files | |
| ```text | |
| backend/server.py | |
| backend_data/black_dragon.db | |
| backend_data/secrets.json | |
| ``` | |
| ## Frontend File | |
| ```text | |
| index.html | |
| ``` | |
| ## Security Rules | |
| - API key stays in backend only. | |
| - Frontend has no API-key box. | |
| - Terms and Privacy acceptance is required before interactive/sensitive actions. | |
| - Dangerous PC commands are blocked. | |
| - Uploaded files are scanned before being accepted. | |
| - Notes are stored in the backend database. | |
| - Browser image results are third-party/browser sourced. | |
| - Every backend chat is mirrored to `%TEMP%\BlackDragonChats\`. | |
| - The app requires the backend to be running; the frontend does not contain the API key. | |
| ## Known Production Notes | |
| For a true public production deployment: | |
| - move secrets to environment variables or a managed secret store, | |
| - use HTTPS, | |
| - configure authentication, | |
| - configure a proper grievance/contact process, | |
| - review Terms and Privacy Policy with a lawyer, | |
| - deploy backend on a trusted server, | |
| - add monitoring and backup, | |
| - do not expose local PC-control endpoints publicly without authentication. | |
| ## APK Note | |
| An APK wrapper can open the backend URL, but the backend must run on a reachable machine. For production phone use, deploy the backend as a public HTTPS server and rebuild the APK with that HTTPS URL. For local testing only, use the PC LAN IP or hotspot URL. | |