Judgment CLI

Warning

Deprecated as of July 9, 2026. The Judgment CLI is no longer under active development and is not recommended for new workflows. Existing releases remain available, but compatibility with future API changes is not guaranteed. Use the Judgment MCP server for agent workflows or the Python and TypeScript SDKs for programmatic integrations. Existing installations are not being shut down as part of this change. We may revisit a CLI in the future.

Command-line interface for the Judgment API. Commands are auto-generated from the API's OpenAPI spec, so the CLI surface always matches the server.

Installation

Quick install (curl)

curl -fsSL https://judgmentlabs.ai/install.sh | bash

Pin a specific version:

curl -fsSL https://github.com/JudgmentLabs/cli/releases/download/v0.1.0/install.sh | bash

This puts 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.

Homebrew

brew install JudgmentLabs/tap/judgment-cli

brew upgrade judgment-cli picks up new releases automatically. Formula source: JudgmentLabs/homebrew-tap.

From source

pip install .

Authentication

Login (recommended)

judgment login
# Opens your browser to authorize the CLI.

Credentials are written atomically with 0600 permissions to a platform-appropriate config dir resolved via 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

Other methods

Priority	Method	Example
1	Env vars	JUDGMENT_API_KEY, JUDGMENT_ORG_ID, JUDGMENT_PROJECT_ID, JUDGMENT_BASE_URL, JUDGMENT_AUTH_URL
2	Config file	judgment login

judgment login --api-key  # manually store an API key instead
judgment login --no-browser  # print the browser URL for remote shells
judgment status   # show resolved sources
judgment logout   # delete the credentials file

Shell completion

The curl installer wires up completions automatically (zsh, bash, fish). Set NO_COMPLETIONS=1 before piping to bash to opt out, or remove the # >>> judgment cli completion >>> block from your rc file later.

brew install drops 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 — this same setup enables completions for every brew-installed CLI, not just judgment.

To install completions manually for any shell:

# 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

Usage

Run judgment --help for the full command list, and judgment <group> <command> --help for the flags on a specific command.

Select a default organization and project from the CLI:

judgment context set   # arrow-key selector; type to filter orgs/projects
judgment context show

Once context is set, project-scoped commands can omit IDs. You can still pass --organization-id, --project-id, --organization, --project, or the old positional IDs for scripts.

# Projects
judgment projects list

# Traces
judgment traces search --pagination '{"limit":25,"cursorSortValue":null,"cursorItemId":null}'
judgment traces search    <PROJECT_ID> --pagination '{"limit":25,"cursorSortValue":null,"cursorItemId":null}'
judgment traces get       <PROJECT_ID> <TRACE_ID>
judgment traces spans     <PROJECT_ID> <TRACE_ID>
judgment traces tags      <PROJECT_ID> <TRACE_ID>
judgment traces behaviors <PROJECT_ID> <TRACE_ID>
judgment traces span      <PROJECT_ID> --spans '[{"trace_id":"...","span_id":"..."}]'

# Sessions
judgment sessions search          <PROJECT_ID> --pagination '{"limit":25,"cursorSortValue":null,"cursorItemId":null}'
judgment sessions get             <PROJECT_ID> <SESSION_ID>
judgment sessions trace-ids       <PROJECT_ID> <SESSION_ID>
judgment sessions trace-behaviors <PROJECT_ID> <SESSION_ID>

# Behaviors / judges / automations
judgment behaviors list   <PROJECT_ID>
judgment behaviors get    <PROJECT_ID> <BEHAVIOR_ID>
judgment judges settings  <PROJECT_ID> <JUDGE_ID>
judgment automations list <PROJECT_ID>

# Prompts
judgment prompts list     <PROJECT_ID>
judgment prompts get      <PROJECT_ID> <PROMPT_NAME> [--commit-id <SHA> | --tag <TAG>]
judgment prompts versions <PROJECT_ID> <PROMPT_NAME>
judgment prompts commit   <PROJECT_ID> <PROMPT_NAME> "<PROMPT_TEXT>" [--tags production --tags staging]
judgment prompts tag      <PROJECT_ID> <PROMPT_NAME> <COMMIT_ID> --tags production
judgment prompts untag    <PROJECT_ID> <PROMPT_NAME> --tags production

# Docs
judgment docs search "how do I instrument my app"
judgment docs read   /docs/getting-started

Development

uv sync --extra dev
uv run python scripts/generate_cli.py

generate_cli.py rewrites src/judgment_cli/generated/ from the OpenAPI spec. Pass --spec <url-or-file> to point at a different spec; --help for the full usage.