README
¶
Baseten CLI
CLI for Baseten.
Installation
Homebrew (macOS and Linux)
# Add and trust the tap
brew tap basetenlabs/baseten
brew trust basetenlabs/baseten
# Install the CLI
brew install baseten
# Upgrade to the latest release
brew update
brew upgrade baseten
Prebuilt binaries
Download the latest release for Windows, macOS, or Linux, extract the archive, and place the baseten executable on your PATH.
Windows, macOS, and Linux one-liners
Windows (x64)
PowerShell:
Invoke-WebRequest `
https://github.com/basetenlabs/baseten-cli/releases/download/v1.1.0/baseten_1.1.0_windows_amd64.zip `
-OutFile baseten.zip; Expand-Archive -Force baseten.zip .
Then move baseten.exe to a directory on your PATH.
macOS (arm64)
curl -sL https://github.com/basetenlabs/baseten-cli/releases/download/v1.1.0/baseten_1.1.0_darwin_arm64.tar.gz \
| sudo tar xz -C /usr/local/bin baseten
Linux (x64)
curl -sL https://github.com/basetenlabs/baseten-cli/releases/download/v1.1.0/baseten_1.1.0_linux_amd64.tar.gz \
| sudo tar xz -C /usr/local/bin baseten
Usage
Authenticate via baseten auth login, or set BASETEN_API_KEY in the environment.
Run baseten --help (or baseten <command> --help) for the full command tree.
Deploying Models
From inside a model directory containing a config.yaml:
baseten model push
The directory defaults to the current working directory and is configurable via --dir. Useful flags:
--tailstreams build and runtime logs to stderr after the push completes.--waitblocks until the deployment reaches an active status and exits non-zero on terminal failure.
Calling a Model
baseten model predict --model-id <model-id> --data '{"prompt":"hello"}'
--model-name is also accepted. Pass --file <path> (or --file - for stdin) to send a request body from a file.
Viewing Logs
baseten model deployment logs --model-id <model-id> --deployment-id <deployment-id> --tail
Omit --tail and pass --since 1h (or --start/--end) to fetch a historical window.
Run baseten --help for more, and see docs.baseten.co for general Baseten platform documentation.
Building
To build from source, clone this repository and run:
go build ./cmd/baseten
See CONTRIBUTING.md for contribution guidelines.
Directories
¶
| Path | Synopsis |
|---|---|
|
baseten
command
|
|
|
internal
|
|
|
cmddocs
command
Command cmddocs walks the declarative cmd.Root tree and emits a versioned JSON description for consumption by docs.baseten.co.
|
Command cmddocs walks the declarative cmd.Root tree and emits a versioned JSON description for consumption by docs.baseten.co. |
|
deploymentpatch
Package deploymentpatch builds the deployment-patch primitives the watch loop needs: a managementapi.DeploymentPatchPoint describing a source tree (BuildPatchPoint) and the patch ops between two points (BuildPatchOps).
|
Package deploymentpatch builds the deployment-patch primitives the watch loop needs: a managementapi.DeploymentPatchPoint describing a source tree (BuildPatchPoint) and the patch ops between two points (BuildPatchOps). |
|
harness
Package harness configures coding harnesses (Claude Code, Codex, OpenCode, and Pi) to use Baseten routes, and removes that configuration again.
|
Package harness configures coding harnesses (Claude Code, Codex, OpenCode, and Pi) to use Baseten routes, and removes that configuration again. |
|
help
Package help renders our CLI's help output and provides the Execute wrapper around cobra used by internal/cmd.Execute.
|
Package help renders our CLI's help output and provides the Execute wrapper around cobra used by internal/cmd.Execute. |
|
sandboxconnect
Package sandboxconnect opens an interactive terminal to a sandbox over the WebSocket its execution API serves at /terminal/ws.
|
Package sandboxconnect opens an interactive terminal to a sandbox over the WebSocket its execution API serves at /terminal/ws. |
|
ssh
Package ssh implements the local mechanics behind the SSH access commands: generating a keypair, writing the managed ~/.ssh/config block, signing a certificate against the REST API, and relaying a connection through the SSH proxy.
|
Package ssh implements the local mechanics behind the SSH access commands: generating a keypair, writing the managed ~/.ssh/config block, signing a certificate against the REST API, and relaying a connection through the SSH proxy. |