---
title: "judgment judges"
deprecated: true
description: "The server-backed Judgment CLI judge commands are no longer supported."
sidebar:
  label: "Judges"
  hidden: true
seo:
  title: "Retired Judgment CLI Judge Commands | Judgment Docs"
  description: "The server endpoints for the Judgment CLI judge commands have been removed."
---

> **Warning**
>
> The server endpoints backing `judges create`, `delete`, `get`, `get-settings`,
> `list`, `models`, `set-tag`, `update`, `update-settings`, and `upload` have
> been removed. Existing CLI releases may still show these commands in
> `--help`, but calls against current servers return 404 responses.

Use the Judgment Platform or [Judgment MCP server](/documentation/mcp-server)
to view and manage judges and their behaviors.

## Local judge scaffolding

`judges init` remains available because it only creates files on your local
machine. The generated custom judge cannot be uploaded with the CLI because
`judges upload` is no longer supported.

```bash
judgment judges init [OPTIONS]
```

| Flag | Type | Required | Description |
| ---- | ---- | -------- | ----------- |
| `-t`, `--response-type` | `binary`, `categorical`, `numeric` | yes | Response type for the judge. |
| `-n`, `--name` | text | yes | Judge class name (must be a valid Python identifier). |
| `-p`, `--init-path` | text | no | Directory in which to create the judge file. |
| `-r`, `--include-requirements` | boolean | no | Also create an empty `requirements.txt` next to the judge file. |
| `-y`, `--yes` | boolean | no | Skip the file creation confirmation prompt. |