Your workspace. Your engines.
codex · claude · opencodeOne install. Desktop and terminal.
Why the desktop includes the CLI, and how to install just the terminal launcher.
Desktop or CLI-only installation
The Windows desktop installer includes the CLI and registers its current-user directory. For CLI-only installation, run the official PowerShell command. The bootstrap checks the archive and executable hashes before installing into your local Firstbeam folder.
Terminal
irm https://firstbeam.xyz/cli/install.ps1 | iexRefresh the terminal host
Fully close Windows Terminal, PowerShell or your terminal host after installation. A new tab inside a running host can inherit the old PATH. Reopen CMD and check where firstbeam resolves before launching a conversation.
Terminal
where firstbeam
firstbeam --version
firstbeam doctorStart a conversation or task
Run firstbeam for the interactive launcher, choose an engine and enter a task. Use help to inspect available commands and options. Existing engine authentication is used; a working launcher does not imply the provider account is authenticated.
Terminal
firstbeam
firstbeam --help
firstbeam chat
firstbeam run "Inspect this project and explain its test setup"Choose the right surface
The CLI supports provider conversations and individual tasks. Desktop team orchestration and bidirectional desktop-feed synchronization are separate capabilities and are not currently available in the CLI. Use Desktop when you need the shared team editor and visual project tools.
If CMD cannot find the command
Check the installed executable directly before changing PATH. If the executable reports its version, the binary is present and the remaining problem is command lookup. Run install-path to register that directory, close the terminal host completely and try where firstbeam again. Do not replace an installed working executable with an unrelated archive.
Terminal
"%LOCALAPPDATA%\Firstbeam\cli\firstbeam.exe" --version
"%LOCALAPPDATA%\Firstbeam\cli\firstbeam.exe" install-pathRead the doctor result
Doctor checks engine installation and account bindings. Treat the selected engine, account and project as separate inputs. A provider error should be investigated in its native runtime; a CLI input or rendering issue should be reported with terminal size and reproduction steps. Keep the exact help output close to hand because supported commands can change between releases.