--- title: "Judgment CLI" deprecated: true description: "Legacy documentation for the deprecated Judgment CLI" sidebar: label: "CLI" hidden: true seo: title: "Deprecated Judgment CLI | Legacy Documentation" description: "The Judgment CLI is deprecated and no longer under active development. Legacy documentation remains available for existing users." --- > **Warning** > > **Deprecated as of July 9, 2026.** The Judgment CLI is no longer under active > development and is not recommended for new workflows. The server-backed > `judgment behaviors` commands and `judgment judges` commands are no longer > supported and return 404 responses against current servers. `judgment judges > init` remains available because it only creates local files. Use the Judgment > Platform or [Judgment MCP server](/documentation/mcp-and-agent-tools) for > judge and behavior workflows, or the [Python > SDK](/sdk-reference/python/judgeval) and [TypeScript > SDK](/sdk-reference/typescript/judgeval) for programmatic integrations. > Existing releases remain available, but compatibility with future API changes > is not guaranteed. Existing installations are not being shut down as part of > this change. We may revisit a CLI in the future. The documentation below is retained for existing CLI users. For the full command and flag reference, see the [CLI reference](/cli-reference). ## Legacy installation **curl** ```bash curl -fsSL https://judgmentlabs.ai/install.sh | bash ``` Pin a specific version: ```bash curl -fsSL https://github.com/JudgmentLabs/cli/releases/download/v0.1.0/install.sh | bash ``` The installer creates an isolated venv at `~/.local/share/judgment-cli/venv` and symlinks `judgment` into `~/.local/bin`. Override locations with `INSTALL_DIR=...` and `PREFIX=...`. Requires Python ≥ 3.9 — set `PYTHON=...` to pick a specific interpreter. Set `NO_COMPLETIONS=1` to skip wiring up shell completions. **Homebrew** ```bash brew install JudgmentLabs/tap/judgment-cli ``` `brew upgrade judgment-cli` picks up new releases automatically. Formula source: [JudgmentLabs/homebrew-tap](https://github.com/JudgmentLabs/homebrew-tap). The formula installs the zsh completion script in `$(brew --prefix)/share/zsh/site-functions/`. zsh picks it up once you've followed [Homebrew's one-time shell-completion setup](https://docs.brew.sh/Shell-Completion). ## Authenticate ### Log in ```bash judgment login # Opens your browser to authorize the CLI. ``` By default, `judgment login` opens your browser to complete an OAuth flow. Two flags adjust this behavior: ```bash judgment login --api-key # prompt for an API key instead of opening the browser judgment login --no-browser # print the authorization URL instead of opening a browser (useful for remote shells) ``` OAuth access tokens are refreshed automatically when they expire, so you stay logged in without re-running `judgment login`. Credentials are written atomically with `0600` permissions to a platform-appropriate config dir resolved via [`platformdirs`](https://pypi.org/project/platformdirs/): | OS | Path | | ------- | ------------------------------------------------------------------- | | macOS | `~/Library/Application Support/judgment/credentials.json` | | Linux | `$XDG_CONFIG_HOME/judgment/credentials.json` (default `~/.config/...`) | | Windows | `%APPDATA%\JudgmentLabs\judgment\credentials.json` | Use `judgment configure` to update stored credentials interactively, `judgment status` to see which sources are resolved, and `judgment logout` to delete the credentials file. ### Other credential sources | Priority | Method | Variables / Path | | -------- | ----------- | -------------------------------------------------------- | | 1 | Env vars | `JUDGMENT_API_KEY`, `JUDGMENT_ORG_ID`, `JUDGMENT_BASE_URL`, `JUDGMENT_AUTH_URL` | | 2 | Config file | Written by `judgment login` | Environment variables always win over the config file. ## Shell completion The `curl` installer wires up completions automatically (zsh, bash, fish). To install completions manually: ```bash # bash (~/.bashrc, or ~/.bash_profile on macOS) eval "$(judgment completion bash)" # zsh (~/.zshrc) autoload -Uz compinit && compinit eval "$(judgment completion zsh)" # fish (~/.config/fish/completions/judgment.fish — auto-loaded) judgment completion fish > ~/.config/fish/completions/judgment.fish ``` ## Quickstart Run `judgment --help` for the full command list, and `judgment --help` for the flags on a specific command. JSON-shaped flags (filters, pagination, conditions, actions) accept inline JSON strings. ```bash # Projects judgment projects list judgment projects create "My Project" # Traces judgment traces search --pagination '{"limit":25,"cursorSortValue":null,"cursorItemId":null}' judgment traces get judgment traces spans judgment traces add-tags --tags reviewed --tags urgent judgment traces evaluate --trace-ids # Sessions judgment sessions search --pagination '{"limit":25,"cursorSortValue":null,"cursorItemId":null}' judgment sessions get judgment sessions trace-behaviors # Automations judgment automations list # Prompts judgment prompts list judgment prompts get [--commit-id | --tag ] judgment prompts versions judgment prompts commit "" [--tags production --tags staging] judgment prompts tag --tags production judgment prompts untag --tags production # Docs judgment docs search "how do I instrument my app" judgment docs get-page /docs/getting-started ``` For the per-group, per-command, per-flag reference — including the JSON shapes accepted by complex flags like `--conditions`, `--actions`, `--filters`, and `--span-triggers` — see the [CLI reference](/cli-reference).