The terminal cannot find niblet
PATH. See Install the CLI
if you need to reinstall it.
Sign-in opens but never finishes
Keep the original CLI process running and complete authorization on the same computer. The browser must return to a temporary127.0.0.1 address opened by
that CLI process.
The authorization link expires after five minutes. If it times out—or you opened
it on another device—run niblet auth login again and use the new link.
MCP connects but Niblet tools are missing
Confirm the server URL is exactly:The local preview fails
Runniblet apps validate . and start with the first error it reports. Confirm
the project contains manifest.yaml, exactly one top-level .star file, and
a main() function that returns render.Root.
The app works locally but review requests changes
Look for local filesystem assumptions, private network endpoints, unapproved redirects, missing configuration defaults, or protected values that were placed in ordinary settings. Reviewers evaluate both the source and the exact preview uploaded by the CLI.The installer cannot find the display
Use a data-capable USB cable, connect directly instead of through a hub, and close other installer tabs, serial monitors, and IDEs that may already be using the port. Original Tidbyt Gen 1 uses WebUSB; Tidbyt Gen 2 uses Web Serial. If a firmware write was interrupted, reconnect the display and repeat the installer for the same model.Troubleshoot Tidbyt installation
Fix Windows access errors, bootloader sync failures, missing ports, and Wi-Fi setup.