av/harbor: README-based editorial guide

av/harbor describes itself in the README as "Stop configuring your AI stack. Start using it. One command brings a complete pre-wired LLM stack with hundreds of services to explore.". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "README", the README says: Harbor is a CLI and companion app that lets you spin up a complete local LLM stack,backends like Ollama, llama.cpp, or vLLM, frontends like Open WebUI, plus supporting services like SearXNG for web search, Speaches for voice chat, and. That establishes the project's stated boundary, not a production test.

The README's "News" section gives a useful starting point for deciding whether the project fits: v0.5.4 - Repairs first-boot and integration failures across 20+ services found by the new runnable integration suite, plus Boost error responses that propagate real backend status codes. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: v0.5.5 - New Speech-to-Speech (s2s) backend service, Dify upgraded to 1.x, and a large service repair sweep restoring Open WebUI web search, OpenHands, Perplexica, mistral.rs, TGI, Nexa, and a dozen more. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "Local Coding Tools". The source evidence includes: Use Harbor backends from installed coding and agent CLIs without hand-editing each tool's provider config. harbor launch starts or detects a Harbor OpenAI-compatible backend, wires the selected model into the host tool, and leaves the tool. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.