Desktop vs CLI
A visual project workspace or a terminal-first task? Compare teams, tools and installation.
| Capability | Firstbeam Desktop | Firstbeam CLI |
|---|---|---|
| Best for | Project conversations and visual review | Individual provider tasks |
| Teams | Shared team editor and conversation rosters | Desktop orchestration is not available |
| Workspace tools | Files, Git, terminals and plans | Commands and provider-native output |
| Installation | Windows installer includes the CLI | Standalone PowerShell bootstrap |
| Provider access | Your existing engine accounts | Your existing engine accounts |
How to decide
Start with the job you want to complete, then select the surface and permission level that make the result easiest to review. Provider access, model availability and charges remain governed by your selected accounts.
Desktop or CLI-only installation
The Windows desktop installer includes the CLI and registers its current-user directory. For CLI-only installation on Windows x64 with Node.js 20+, run the npm command below. The packaged launcher verifies its native executable. A PowerShell installer is also available on the download page.
npm install -g https://firstbeam.xyz/cli/package.tgzRefresh 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.
where firstbeam
firstbeam --versionStart 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.
firstbeam
/engineChoose 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.
"%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.
Compare side by side
Choose a guide for the full table and practical setup steps.