TinyWebUI v0.1.4

No more password prompt on first run

npx tinywebui now starts without asking you to create a password. The terminal prints a sign-in link instead:

[tinywebui:server] sign in: http://127.0.0.1:7777/#token=…

Open it and your browser stays signed in, including across restarts. Only someone who can read that terminal can get in. Other programs and users on the same machine that try the port are refused. The token changes every time the server starts.

What still needs a password

• Listening on the network. Starting with --host 0.0.0.0 or any non-loopback address still refuses to run until you set a password with tinywebui set-password or TINYWEBUI_PASSWORD. Docker is unchanged, because the container listens on a network interface.
• If you already have a password, nothing changes: you keep signing in with it, and the link does not work.

DNS-rebinding protection for authMode: "none"

With login turned off, TinyWebUI now answers only to loopback host names (localhost, 127.0.0.1, [::1]). This stops a malicious website from pointing its own domain at your machine and using the chat UI and its tools through your browser. To reach a no-login install by another name, add it to the new allowedHosts setting in tinywebui.config.json.

Upgrading

No action needed. Configs with a password keep working as before. Configs without one now use the sign-in link on loopback and still refuse to start on a network address.

Full Changelog: v0.1.3...v0.1.4

v0.1.3

TinyWebUI v0.1.3

This release improves Docker packaging and npm release tracking.

• Docker images now use a separate build stage, leaving npm and npx out of the runtime image. This addresses the vulnerable npm dependency found by Trivy.
• MCP servers in Docker can connect over HTTP; stdio servers that need extra executables require a custom image.
• Successful npm publishes now create a GitHub deployment record linked to the package.

Full Changelog: v0.1.2...v0.1.3

TinyWebUI v0.1.2

TinyWebUI v0.1.2

This release adds easier MCP server management, more control over access, and stronger checks for fresh installations.

• Manage MCP servers through the new connector interface and the manage_mcp tool.
• Let admins edit access policies and users set personal instructions.
• Require an owner password on fresh installs and headless starts.
• Add Trivy security scans for source, configuration, and the Docker image.
• Refresh Docker’s Node.js version and dependencies, and update the README and branding.

Full changelog: v0.1.1...v0.1.2