bl setup
Set up Blaxel for your coding agents and log in
Synopsis
Set up everything Blaxel needs on this machine, then log in.
When logging in without a specified workspace, if your account has no
workspaces, setup opens the Console so you can create or join one, and waits
up to five minutes for it to become available.
For the coding agents found on this machine (Claude Code, Codex, Cursor, …),
setup installs the Blaxel agent skills and adds two MCP servers: blaxel, to
manage your workspace resources, and blaxel-docs, to search the Blaxel
documentation. It then logs you in to Blaxel in your browser. The agents use
that login through bl mcp, so they need no sign-in of their own.
In a terminal, setup shows everything it found, selected, and installs it
when you press Enter; —yes installs it without showing the plan. Without a
terminal, setup installs the same defaults and skips the browser login, so
run bl login afterwards. The usage and error reports toggle controls the saved
tracking preference. New setup plans keep reports selected by default; an
existing saved choice is retained. Anonymous usage capture is disabled in CI,
by any nonempty DO_NOT_TRACK, or by BL_INSTALL_TRACKING=false. Error reports
keep the SDK’s existing DO_NOT_TRACK semantics.
Events, properties and opt-outs: https://docs.blaxel.ai/Security/Data-collection-and-privacy
Setup only adds what is missing, and it is safe to run again after
installing another agent. MCP server entries you configured yourself are left
unchanged; the hosted blaxel server added by earlier versions is switched to
bl mcp. A blaxel server that the Blaxel plugin provides is left to the plugin.
Examples
Options
Options inherited from parent commands
SEE ALSO
- bl - Blaxel CLI - manage and deploy AI agents, sandboxes, and resources
Last modified on October 21, 2026