DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to host the Web UI for a team with login enabled with AI Security Tool

Deploy the web interface on a shared server with password authentication and local terminal access turned off.

Credentials. The SERVER_SECRET and SERVER_PASS values in .env are the only barrier to the Web UI, so store them safely and never commit the file to version control.

Remote script. The one-line installers pipe remote scripts into bash or run a downloaded batch file, so review the script before running it on a production server.

Who it is forA team lead or platform engineer who wants several colleagues to reach the tool from their browsers on a shared server.

The problemA web-based security terminal exposed to a network without authentication or with local shell access enabled is a serious risk.

The outcomeA running Web UI behind an Nginx reverse proxy, with password authentication on and local server terminal access disabled.

What you need first

  • A Linux, macOS, or Windows machine with internet access to download the build
  • A web browser to open the Web UI at http://127.0.0.1:5577
  • Written authorization to scan or access every target system you plan to use
  • An API key for DeepSeek, OpenAI, or a custom LLM provider if you want the AI assistant or agents to call a model

Steps

  1. Create a .env file in the project folder and set ENABLE_AUTH=1, DISABLE_LOCAL_TERMINAL=1, SERVER_SECRET, and SERVER_PASS to strong values.
  2. Start the service with ./run-ai-security-tool-web.sh.
  3. Adapt the example configuration in examples/nginx.conf to your domain and add your SSL certificate paths. (inferred, check the README)
  4. Reload Nginx and open your public domain in a browser to confirm the login page appears before the Web UI loads.
  5. Confirm that the local terminal option is unavailable in the Web UI after login.

Prompt for your agent

Using the AI Security Tool repo at https://github.com/ZeroDayEvil/ai-security-tool, configure the .env file with ENABLE_AUTH=1 and DISABLE_LOCAL_TERMINAL=1 and start the web service for <domain-name>. Expected output: the service starts and the public URL shows a password prompt. Verify that an unauthenticated request to the URL is refused before the Web UI loads.

Caveat. The README says the AI agents can execute system commands, so keep the host's permissions minimal and watch agent activity on the real-time dashboard.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page