Glowbom OSS
Build with local project files, OpenCode, and an open React interface.
Loading page content...
Glowbom OSS is the open local workflow behind Glowbom. A Go backend and a React interface help you load a project, work with coding agents, and review results. It works with Glowbom projects and can also work with other project structures.
The software is free to use. Model providers may charge for their services. A Glowbom account is not required for the local workflow.
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 sh
This 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 doctor
If 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 build -o ../glowbom .
cd ..
./glowbom doctor
./glowbom start
Use ./glowbom for the remaining commands when using this source build.
Configure your provider through OpenCode:
opencode auth login
Choose an available provider and follow its sign-in instructions. Authentication methods and model availability depend on the provider and your installed OpenCode version. See OpenCode provider setup.
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.
From the repository root:
glowbom start
The 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/project
Load 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.
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 your OpenCode provider configuration and account access before retrying in Glowbom OSS.
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 Project Book is the direction for preserving intent and history alongside code. Its integrated workflow is under development.
Glowbom account login, cloud generation transfer, and spending Glowbom credits from the CLI are planned work, not commands in the current CLI. Continue using local files and your OpenCode provider configuration today.
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.