One command installs OpenClaw + a complete browser-based AI workstation. Agent chat, shared browser, code sandbox, remote desktop, terminal, email, skills marketplace, and automations โ connect providers with account sign-in where supported or API keys where preferred. Free and open source.
Ubuntu 22.04+ or Debian 12+ on a compatible host. Installation time depends on downloads, host resources, and enabled features. Review any interruption before retrying.
Runs the public Windows bootstrapper for the experimental WSL 2 local preview. Not a supported production hosting profile.
Chat with AI agents, preview live HTML, switch models, and manage projects โ from your phone, tablet, or desktop. No app install needed.
It turns any cheap server into a full AI workspace you control from your browser. Chat with multiple AI models. Let your AI browse the web while you watch. Run code safely in sandboxes. Manage files, send email from your own domain, install new abilities from a marketplace, and schedule tasks to run while you sleep. The Portal is free; you provide the server, provider access, and any domain or mail configuration.
One installer provisions the workstation and guided setup connects the capabilities your host and provider accounts support.
Portal 5 brings Project Work and broader harness support. Version 5.0.8 fixes duplicate message and tool activity, preserves repeated replies, and adds clearer chat-scoped Tasks progress. Recent patches also improve signed updates, backup verification, and interrupted-maintenance recovery.
Your agent drives a real Chrome session while you watch on the same screen. Take the mouse back whenever you want โ it is collaboration, not a black box.
Install reviewed skills, wire up MCP tools, and schedule recurring agent work โ then inspect the runs instead of treating background actions as fire-and-forget.
Pending Agent Chat and Project Chat questions appear as persistent, expandable notifications. Choose an option, type a response, send, or deliberately skip โ without navigating away from the page you are working on.
Reconnect replay, bounded history, exact-run steering, cancellation, and stable tool and thought timelines make long turns usable after ordinary browser disruption.
Compatible hosts get non-root, project-bound runtimes with one writable workspace, live attestation, and controlled public egress. Providers qualify before they can run there.
Backups include project and standalone app sources. Update and restore paths preserve data, reconcile running-app intent, and keep a last known-good deployment available when promotion fails.
The Owner sees signed release details and starts the update. Portal checks backup freshness, serializes maintenance, applies migrations, verifies service and runtime health, and rolls back a candidate that cannot become healthy.
Fresh installs create a secure Owner first. Readiness cards then guide optional domain, mail, provider, local model, Remote Desktop, and other host capabilities.
Allow time for package downloads and runtime provisioning. Start with at least 3.5 GB RAM and 35 GB disk; 4 GB+ RAM is recommended.
The portal is free. Your monthly cost is your VPS plus whatever model access you choose โ subscription-style sign-in where supported, API keys where needed, or local Ollama.
* Provider costs depend on your account, harness, and access method. Subscription sign-in, metered APIs, and local compute have different limits and charges; no flat-rate provider access is included.
What Portal provides, and what you still bring.
| Capability | Portal | Requirement or boundary |
|---|---|---|
| Agent Chat and Project Work | Browser-based conversations and workspaces | Available harness, supported host, and provider access |
| Shared browser and desktop | Chrome and noVNC integration | Provisioned desktop; separate provider sign-ins where needed |
| Project isolation | Scoped containers and controlled egress | Compatible Docker, kernel, and AppArmor; operator chat is separate |
| Mail and public sharing | Optional domain mail and scoped share links | Domain, DNS, TLS, and deliberate public exposure |
| Updates | Owner-started signed Portal updates | Compatible AI tools use separate explicit maintenance |
| Backups | Portal data; optional agent reference exports | No mail, provider logins, runtime databases, or whole-server restore |
| Costs and privacy | MIT-licensed, self-hosted workstation | VPS/provider costs and external AI traffic remain yours |
Portal data is self-hosted. External AI requests leave your server; optional operational telemetry, update checks, and installer events are explained in the privacy notice.
Automatic SSL certificates via Let's Encrypt. HSTS headers, CSP policies, and strict security headers out of the box.
Project Chat uses project-scoped containers and controlled egress on supported hosts. Main Agent Chat and Terminal are separate operator-level surfaces, not tenant sandboxes.
Owner, admin, user, and viewer roles. New accounts require approval. Disabled or banned accounts are locked out immediately.
Dedicated middleware blocks directory traversal, symlink escapes, and access to system paths. Repeated violations are tracked and escalated.
The VPS profile configures UFW. Internal APIs, browser control, and database services stay private; configured public mail protocols and share links have their own exposure.
Uploaded files are scanned with ClamAV before storage. Detected threats are rejected automatically.
Full details in our security policy โ including known limitations and hardening recommendations.
BridgesLLM Portal runs on OpenClaw โ the open-source agent framework for running agent workflows on infrastructure you control. Connect Claude, Codex, Gemini, Grok, or local Ollama models through account sign-in, setup-token, API keys, or local-model paths depending on the provider. Predictable infrastructure cost, clearer ownership, and a full browser workspace.
OpenClaw (agent framework)
Claude Code (Anthropic)
Codex (OpenAI)
Gemini (Google)
Grok (xAI) New
Agent Zero New
Ollama (local models)Provider availability depends on your account and the connection path you choose. OpenClaw, Claude, Codex, Gemini, Grok, Agent Zero, and Ollama names and logos are trademarks of their respective owners and are shown for identification only.
Get a compatible VPS, run the installer, and follow setup. Some host prerequisites and recovery operations require administrator access.
Hetzner, DigitalOcean, Vultr, Linode โ any supported Ubuntu or Debian VPS. 3.5GB+ RAM, 35GB disk, typically $20โ40/mo.
One installer command provisions the stack and prints the setup URL. Timing varies with the host and downloads.
Domain, SSL, admin account โ all in the browser. No config files to touch.
The setup wizard connects your AI providers โ paste an API key or sign in with OAuth. Start chatting immediately.
Everything you need for each step, including commands and tips.
Watch: Full install + setup walkthrough
SSH into your VPS and paste the install command. The script installs all dependencies, sets up the database, configures SSL, and starts the portal.
Choose Install on a new host or Update / Repair on an existing installation. Follow the printed setup URL to create the Owner in the browser.
Open the portal URL in your browser. The setup wizard walks you through domain configuration, SSL certificates, and your admin account. Everything is handled in the browser โ no config files to edit.
The setup wizard walks you through connecting AI providers. Depending on the provider, you can use:
You can add, change, or remove providers any time from the Settings page in the portal.
openclaw onboard in the portal's Terminal to configure providers manually.Open Agent Chat, choose an available harness/model, and confirm a real reply. Readiness indicators describe checks; they do not guarantee account entitlement or a successful turn.
That's it โ your AI workstation is live. Start chatting, create projects, or explore the file manager and remote desktop.
Copy the prompt below and paste it into your OpenClaw agent's workspace file (e.g. AGENTS.md or system prompt). This teaches the agent how your portal works โ where files live, how projects are structured, and how to interact with users through the portal interface.
โ Scroll down to the "Agent Portal Prompt" section to copy it.
Check the selected harness readiness and recorded error first. A gateway startup, missing login, incompatible plugin, or interrupted maintenance needs its own remedy. Inspect services without restarting an active conversation:
Make sure your domain's DNS A record points to your VPS IP. After DNS propagates, re-run the installer to pick up the domain and provision SSL:
The installer detects the existing installation and only updates what's needed.
Use the Owner-only Update action on the Dashboard after checking backup recoverability. See the update guide. The installer also offers an explicit Update / Repair menu:
If something isn't working, check that both services are running:
Portal and gateway logs are available via journalctl:
Go to Settings in the portal sidebar. You can add, remove, or switch providers (OAuth or API key) at any time. Alternatively, run from the terminal:
Paste this into your OpenClaw agent's workspace instructions to teach it how your portal works. Your agent will know where to find files, how projects are structured, and how to help users through the interface.
Use a supported box with enough RAM and disk. Smaller instances may start, but this is the supported baseline.
Yes. The installer detects an existing OpenClaw installation and uses it instead of requiring a clean server. If OpenClaw is not already installed, the installer installs it for you.
No. Portal Update preserves OpenClaw core and native runtime versions. A narrow question-plugin repair on supported OpenClaw 9.x may briefly restart the gateway. Update Compatible AI Tools is a separate, explicit maintenance action with its own Node prerequisites.
Use Ubuntu 22.04+ or Debian 12+, 3.5 GB RAM minimum (4 GB+ recommended), 35 GB free disk space, root or sudo access, and ideally 2+ CPUs. Smaller instances may boot, but that is the supported baseline.
The installer sets up the core portal stack for you: the portal app, OpenClaw, PostgreSQL, Caddy, and the main system services. The browser setup flow then handles guided configuration such as your admin account, provider connection, and domain/SSL steps.
It depends on the provider and harness. Supported account sign-in, API credentials, and local Ollama each have their own access requirements. Availability and charges follow your provider account; Portal does not require one universal Claude billing arrangement or grant model access.
BridgesLLM Portal itself is free and MIT-licensed. You pay for the VPS, optional domain/services, and whichever model access you use: subscription access where supported, metered APIs, or local compute.
Yes. Your portal data, projects, files, and local services stay on your server. If you connect external AI providers, requests for those models still go to the provider you chose, but the portal itself runs on infrastructure you control.
OpenClaw is the underlying agent/runtime layer. BridgesLLM Portal is the browser-based workstation built on top of it, adding agent chat, shared browser, code sandbox, remote desktop, terminal, files, and guided setup.
Free to install. Use the provider access method you prefer โ OAuth where supported or API keys where needed. You pay for the VPS and any model/provider access you choose.
Questions before you install? Email support@bridgesllm.com or open an issue on GitHub.