LobeHub now operates agent work, not only chat
LobeHub describes itself as a chief agent operator. The application creates agent teammates, schedules their work, groups them inside projects and workspaces, and reports what they deliver. Pages give humans and multiple agents a shared writing surface. Personal memory is structured and editable. The Agent Builder configures roles, while skills and MCP connections supply tools. This is a broader job than putting several model providers behind one chat box.
A team can keep conversations, project context, scheduled runs, goals, and results in one product. It also adopts LobeHub's opinions about ownership, memory, supervision, and review. If your requirement ends at talking to an Ollama or OpenAI-compatible model, most of the operator layer is extra surface.
commit 3ec5348 expects pnpm 12.4.1 and calls Bun
The tested package file declares pnpm 12.4.1. Its workspaces cover packages/*, business packages, end-to-end code, the desktop main process, sharing, and workbench applications. The build script calls Bun for several SPA targets before the Next.js build. Even the README's development instructions say pnpm install, followed by pnpm dev, with Bun offered for the SPA-only path on port 9876.
That makes the package manager part of the setup contract. A generic Node image with npm is not equivalent to the documented development path. The repository contained 17,817 files and about 2,579,688 lines of source at the measured commit, occupying 244.9 MB before installation. It is a monorepo with 33 CI workflow files, a Dockerfile, and a tests directory. This is application-platform scale, and the toolchain should be pinned before anyone waits for a first build.
What happened when we ran it
Our sandbox used Node 22 in an unprivileged Debian container with 3 CPUs, 8 GB of RAM, and no secrets. At commit 3ec5348, npm install ran for 623 seconds and then exited 1. The final error was EUNSUPPORTEDPROTOCOL, followed by Unsupported URL Type "workspace:": workspace:*. Retrying with npm's force protection disabled reached the same protocol error.
The install did not complete, so this run produced no successful dependency count, installed disk total, build result, or test result. We are not treating the failure as proof that the documented pnpm path is broken. It proves the narrower point that npm in the supplied Node 22 image could not install this workspace at that commit. Any team whose build system silently substitutes npm for pnpm will hit that boundary before it reaches LobeHub itself.
Self-hosting now includes gateway keys and database migrations
The README makes the first Docker experience look short: run a setup script, then start Docker Compose. Release v2.2.18 gives the more useful production picture. Existing Compose deployments need a deployment-specific JWKS_KEY, a matching public-only key, GATEWAY_SERVICE_TOKEN, and a browser-reachable AGENT_GATEWAY_URL. Separate internal URLs handle gateway and object-storage traffic between containers. Missing gateway settings trigger a warning and move chat execution back to the browser.
The same release carries database migrations 0162 through 0166 and tells operators to back up before upgrading. It says full production upgrade and rollback verification was not completed. PostgreSQL search has another edge: FTS_SEARCH_PROVIDER=pg_like can select an extension-free query backend for smaller instances, but historical migrations still require pg_search. One setting therefore does not turn a fresh install into a plain-PostgreSQL deployment.
Commercial derivatives need a separate license
GitHub's license field does not identify a standard SPDX license for this repository. The LICENSE file calls the terms the LobeHub Community License, based on Apache 2.0 with extra conditions. Unmodified commercial use as a frontend or backend service is allowed. Developing and distributing a commercial derivative requires a commercial license from LobeHub. Contributors also agree that the producer may tighten or relax the agreement and may use contributed code commercially.
Those terms are readable, but they are not the plain Apache 2.0 badge still referenced in part of the README link definitions. A company can self-host the existing product without the same concern as a vendor shipping a modified edition. The moment a roadmap includes distributing that derivative, legal review belongs before engineering work. LibreChat's MIT license is a cleaner alternative when redistribution rights are a deciding requirement.
Current MCP and PDF issues expose integration edges
The README advertises MCP-compatible plugins as part of a library of more than 10,000 skills. An open issue from September 27 asks for MCP protocol version 2026-07-28 after a server rejected the older version requested by LobeHub. That is one user report, not a claim that every MCP server fails. It is still specific enough to test the exact servers your agents need before making the marketplace count a buying reason.
Open issue 20138 describes a separate document edge. Scanned PDFs were not sent through a vision-capable model's native image channel and instead fell back to analyzeMedia, which needs two additional multimodal environment settings. The reporter's workaround is to configure that provider and model or convert PDF pages to images. Teams building document-heavy agents should reproduce this path with their own models rather than assuming ordinary image support covers scanned PDFs.
October activity is high, while release validation has limits
GitHub showed 82,940 stars and a push on October 1, 2026. Search returned 380 open issues and 145 open pull requests, plus 66 issues closed or updated since September 1. Release v2.2.18 arrived on September 20 with 177 non-merge commits from 12 contributors since the previous tag. Those dates show a heavily worked project, not a dormant repository.
Release preparation did not rerun product tests, lint, or type checking, several acceptance paths remained partial, and a full production upgrade or rollback was not claimed. Our npm install also stopped before a build. Use the declared pnpm toolchain, rehearse Compose migration against copied production data, and test the gateway, MCP, document, and agent paths you plan to depend on.