Glowbom OSS
Run the open backend, CLI, and local coding interface with Buzz connection controls.
Loading page content...
Run the open backend, CLI, and local coding interface with Buzz connection controls.
Loading page content...
Glowbom OSS is the open-source local backend, CLI, and browser interface for coding agents and Buzz connections. Load a project, work with coding agents, and review results. It works with Glowbom projects and can also work with other project structures. The full Chat, Draw, Studio, Book, onboarding, and Tauri interfaces belong to the separate Desktop client. Backend APIs and portable records remain open; the public browser does not expose every API as a screen.
The software is free to use. Model providers may charge for their services. A Glowbom account is not required for the local workflow.
Glowbom Live is a separate, closed-source app downloaded from GitHub release assets. The Buzz button in OSS connects your channel; the installed Live app displays its 3D office. Live is optional for coding.
For the full Mac app, sign up for Glowbom Desktop early access.
Install these tools and make sure they are available in your terminal:
On macOS and Linux, use your regular terminal. On Windows, use WSL with the tools installed inside your Linux environment for this setup.
Install the Glowbom CLI:
curl -fsSL https://raw.githubusercontent.com/glowbom/glowbom-oss/main/scripts/install.sh | sudo shThis installs the CLI in /usr/local/bin and may ask for your administrator
password. Then get the repository below. The installer does not install the
required development tools.
Alternatively, download a matching binary from the GitHub releases page.
The CLI needs a checkout containing backend/ and web/ side by side:
git clone https://github.com/glowbom/glowbom-oss.git
cd glowbom-oss
glowbom doctorIf you already have a checkout, open that folder instead of cloning it again.
Resolve missing dependencies reported by doctor before continuing.
If a release binary is unavailable for your machine, build it from the checkout:
cd cli
go run . doctor
go run . startKeep using go run . COMMAND from cli/ for source commands.
Open Settings → Coding agent and choose OpenCode, Codex, Claude Code, Cursor, or an ACP connection. Install and authenticate the selected agent first. The Agents guide lists installation links and login commands, including Codex App Server and manual ACP setup for Cline, Goose, and other agents.
The OSS interface runs one agent at a time. This is an interface choice; the shared backend can serve concurrent runs from other clients.
Glowbom OSS uses that configuration; it does not require you to enter provider credentials into a separate Glowbom account. Hosted models send requests over the network. Local models require a compatible configuration and enough hardware.
To try an Ollama model on your own computer, follow the optional local AI guide. Its guided setup screens belong to Desktop; OpenCode configuration and backend integration notes also apply to other clients.
From the repository root:
glowbom startThe CLI starts the local backend and web interface, then opens your browser.
If it does not open automatically, visit http://127.0.0.1:4572.
Press Ctrl+C in the terminal to stop the stack.
The backend uses port 4569; the browser interface uses port 4572.
The optional command below prints a project path hint. You still load the project
in the interface; it is not an automatic import or cloud download:
glowbom start /absolute/path/to/projectLoad your local project folder in the interface, choose an available model, and describe one change. Review the agent output and test the relevant platform before accepting the result as ready to ship.
The repository includes a starter in project/. Copy it to your own working
folder before modifying it:
project/
glowbom.json
prototype/
apple/
android/
web/Keep the manifest and assets with the project. You can remove platform folders you do not need. Building Apple, Android, and web targets requires their respective tools; installing the CLI does not install Xcode or Android Studio.
When launched through glowbom start:
127.0.0.1).Do not expose these development services through a public network tunnel without separately designing remote access controls. OpenCode manages its own provider credentials; local service credentials and provider credentials are different.
glowbom start --show-local-auth prints local access credentials for debugging.
Treat that output as sensitive and leave it out of screenshots and issue reports.
Manual backend launches need equivalent authentication configuration. The backend refuses a network-facing bind address without a bearer token. Keep provider credentials outside projects, source, logs, and release archives. The optional file-based account store rejects detected project and source locations, including symlink targets; the system keyring remains the default.
Command not found: restart your terminal and check the tool's install directory
is in PATH. Run go version, bun --version, and opencode --version to identify
which dependency is missing.
Checkout not found: run glowbom start from the repository root, where
backend/ and web/ are siblings. A project export alone is not that checkout.
No models or sign-in failure: check the selected agent's login and account
access, then refresh the model menu. For Cursor, run cursor-agent status and
cursor-agent models; wait up to 45 seconds after signing in before refreshing.
See Agents for setup checks.
Project folder picker unavailable: enter the absolute path manually when the interface offers a path field. On Windows, use a path visible inside WSL.
The open Project Book backend collects saved runs into portable records and can generate stories and sketches with a connected model. Its full reader and editing controls belong to Desktop. The public Agent + Buzz browser does not include those screens.
The current CLI source supports optional Glowbom account login, saved project downloads, and image generation with your Glowbom allowance. It can also download a clean starter without signing in. See the CLI guide for these commands. Your installed release may need an update or a source build to include them.
Glowbom OSS was previously called Glowby OSS. Existing compatibility aliases may
remain in the source. Use glowbom start for new instructions; glowbom code is
a deprecated alias.