kaggle 2.2.3__tar.gz → 2.2.5__tar.gz

{kaggle-2.2.3 → kaggle-2.2.5}/CHANGELOG.md

@@ -3,6 +3,86 @@ Changelog
 
 ### Next
 
+### 2.2.5
+
+* Require `certifi >= 2026.10.19`, which drops the compromised emSign/eMudhra root CAs ([GHSA-6q48-6c7w-9gw2](https://github.com/certifi/python-certifi/security/advisories/GHSA-6q48-6c7w-9gw2)). `kaggle` only pulled in certifi through `requests`, which sets no minimum, so an existing install could keep a certifi that would accept a forged kaggle.com certificate and leak the user's API token to a man-in-the-middle
+* Reject kernel version numbers in `kaggle kernels delete` instead of failing with a `ValueError` when a version is included in `<owner>/<kernel>/<version>`
+* Report a 404 from `kaggle competitions submit` with a competition-specific hint on stderr, naming the notebook and version for code submissions. The check never matched a 404, so users got the generic `<owner>/<slug>` hint instead
+* Exit non-zero from `kaggle competitions submit` when the submission file upload fails. It printed "Could not submit to competition" and exited 0, so scripts treated the failed submission as a success
+* Include the UTC offset (`+00:00`) in `refreshAt` timestamps displayed by `kaggle quota`
+* Recommend installing with `pipx` or `uv` and add troubleshooting guidance for `externally-managed-environment` errors in the installation docs
+* Stream `kaggle kernels output` files to disk through the same download path as datasets and competitions, with a read timeout, a size check, and resume after a dropped connection. Each file used to be read into memory whole, so a 512 MiB output took about 1.2 GB of RAM, and a dropped connection failed the command and left an empty file behind
+* Honor the version in `<owner>/<kernel>/<version>` for `kaggle kernels pull`, `output`, `status`, `files` and `logs`, which previously returned 403 for `pull` and acted on the latest version for the others
+* Clarify in `--accelerator` help and kernels docs that `NvidiaTeslaT4` maps to GPU T4 x2 and `TpuV5E8` maps to TPU v5e-8
+* Reject dataset version numbers in `kaggle datasets delete` to prevent unintentionally deleting an entire dataset when targeting a single version
+* Show why a submission failed in `kaggle competitions submission <ref>`, which already comes back in the API response but was not displayed
+* Honor `-k/--kernel` in `kaggle kernels pull`, which was ignored when the positional kernel argument was omitted, causing the CLI to fall back to the local `kernel-metadata.json` and pull a different kernel
+* Refuse to write a `kaggle kernels output` file whose server-supplied name resolves outside the requested `--path` directory
+* Add `--no-run` to `kaggle kernels push` to save a new version without executing the notebook, the equivalent of Quick Save in the web UI
+* Honor `--unzip` when downloading a single file with `kaggle datasets download -f`, which extracts the file from the zip archive the server wraps large files in, and add `--unzip` to `kaggle competitions download`
+* Fix misleading validation error messages in `kaggle competitions submit` when `--kernel`, `--version`, or `--file` is missing for a code competition submission
+* Keep the requested folder when downloading a single file with `kaggle datasets download -f` or `kaggle competitions download -f`, instead of writing it to the download root
+* Report `slug` instead of `title` in the `kaggle datasets create` error message when the requested slug is already in use
+* Prevent HTTP errors during resumed `Range` downloads from overwriting existing partial download files
+* Check the HTTP status when downloading `kaggle kernels output` files so error responses are not saved as output files
+* Add `kaggle competitions host-add <comp> -u <user>` to grant host access on a competition to a Kaggle user
+* Suggest a next step on 403/404/429/5xx API errors, report unexpected errors as bugs instead of a traceback (with a new `--debug` flag), and list common examples in `kaggle --help`
+* Guard tar extraction in `kaggle models instances versions download --untar` against path traversal
+* Store resumable upload state in a private per-user directory (`0700`) and verify directory ownership and permissions before use
+* Add `kaggle benchmarks quota` to show Model Proxy (AI inference) spend quota, and bump `kagglesdk` to `>= 0.1.38`
+* Honor `--untar` in `kaggle models instances versions download` when the archive is already cached locally
+* Write kernel log files using UTF-8 in `kaggle kernels output` to avoid `UnicodeEncodeError` on Windows
+* Exclude omitted `overview` and `usage` fields from the update mask when updating a model instance
+* Add `kaggle competitions submission-download <id>` to download the submitted file for a single submission (requires `kagglesdk >= 0.1.36`)
+* Add `deadline` (Competition Deadline) to the competition settings command and bump `kagglesdk` to `>= 0.1.36`
+* Warn when `kaggle kernels push` requests a retired accelerator (`NvidiaTeslaP100`, `TpuV38`, `Tpu1VmV38`, `TpuV232` or `TpuV2256`), since the server runs the session on a replacement instead. Drop the retired shapes from the docs
+* Abort dataset, model version, and competition data uploads when a file upload fails instead of skipping the failed file and creating a partial upload
+* Use GitHub alerts and fix the `LLMS_AVAILABLE` token reference in the benchmarks documentation
+* Add unified `kaggle search` command across competitions, datasets, notebooks, models, users, and discussions
+* Parse duration suffixes (`s`, `m`, `h`, `d`, `w`) in `kaggle auth print-access-token --expiration` instead of raising a `TypeError`
+* Add `--wait`/`--poll-interval` to `kaggle competitions submit` to wait for scoring, and add `kaggle competitions submission <ref>` to look up a single submission's status and score
+* Show `N/A` instead of `Fail` in `kaggle benchmarks leaderboard` for a task result the server returned without a pass/fail or numeric score, which was reported as a failed task
+
+### 2.2.4
+
+* fix(benchmarks): support owner/task separator in benchmark commands (#1146)
+* Feat/competition submissions limits (#1144)
+* add competitions solution create/status commands (#1141)
+* fix(cli): prevent stale file corruption when resuming downloads (#1142)
+* fix(cli): fix collaborator role handling in dataset metadata update (#1138)
+* Refactor paging to use Protocols (#1137)
+* fix(cli): retry transient connection errors in with_retry (#1132)
+* Add Kaggle Secrets documentation (#1131)
+* Fix model and owner slug validation (#1134)
+* Implement ignore_patterns in uploading (combined) (#1130)
+* Refactor parser fixtures (#1118)
+* fix(auth): avoid skipping auth for programmatic imports (#1117)
+* fix(cli): resumable upload start offset when zero bytes uploaded (#1113)
+* refactor(cli): reuse _resolve_projection in dataset_status (#1116)
+* update supported model list (#1115)
+* fix(cli): handle deleted comments in topics show (#1114)
+* Add leaderboard subcommand to kaggle benchmarks (#1112)
+* feat(cli): add competitions settings update command (#1104)
+* feat(cli): add competitions hosts list command (#1107)
+* feat(cli): add competitions settings get command (#1103)
+* feat(cli): support --page-token and --page-size, preserve --page (#1098)
+* feat(cli): expose userRank in competitions list output (#1094)
+* fix(cli): read kernel metadata and source files using UTF-8 in kernels_push (#1093)
+* Fix crash when running kaggle command with invalid credentials (#1092)
+* feat(cli): add competitions data push command (#1085)
+* fix(cli): restore fallback for unknown kernel language/type in kernels_pull (#1091)
+* fix(auth): prioritize OAuth credentials over anonymous fallback (#1089)
+* feat(cli): add competitions pages update command (#1083)
+* fix(cli): stop treating subcommand -v as version flag (#1082)
+* fix(cli): honor --unzip for cached dataset downloads (#1086)
+* feat(cli): add competitions pages delete command (#1084)
+* feat(cli): add competitions init and create commands (#1080)
+* docs(competitions): add competition_creation.md for new host commands (#1081)
+* feat(cli): add competitions launch command (#1079)
+* feat(cli): add competitions pages create command (#1078)
+* fix(cli): avoid success message after canceled model deletion (#1077)
+* fix(cli): avoid success message after canceled dataset deletion (#1073)
+
 ### 2.2.3
 
 * Update --format help text to reference output_format.md (#1074)

{kaggle-2.2.3 → kaggle-2.2.5}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: kaggle
-Version: 2.2.3
+Version: 2.2.5
 Summary: Access Kaggle resources anywhere
 Project-URL: Homepage, https://github.com/Kaggle/kaggle-cli
 Project-URL: Issues, https://github.com/Kaggle/kaggle-cli/issues
@@ -213,8 +213,9 @@ Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python :: 3
 Requires-Python: >=3.11
 Requires-Dist: bleach
+Requires-Dist: certifi>=2026.10.19
 Requires-Dist: jupytext
-Requires-Dist: kagglesdk<1.0,>=0.1.30
+Requires-Dist: kagglesdk<1.0,>=0.1.38
 Requires-Dist: packaging
 Requires-Dist: protobuf
 Requires-Dist: python-dateutil
@@ -265,6 +266,14 @@ kaggle --help
 
 See the [User documentation](docs/README.md) for more examples & tutorials.
 
+## Hosting a competition
+
+End-to-end host commands — scaffold a new competition, author its pages,
+tune its settings, and launch it — are documented in
+[docs/competition_creation.md](docs/competition_creation.md). Covers
+`kaggle competitions init`, `create`, `pages create`, `hosts`,
+`settings get`, `settings update`, and `launch`.
+
 ## Development
 
 ### `kagglesdk` Updates
@@ -333,6 +342,31 @@ After setting up your credentials, you can run the integration tests as follows:
 hatch run test:integration
 ```
 
+### Code Coverage
+
+We measure code coverage using `pytest-cov`.
+
+To run unit tests with coverage and generate reports:
+
+```sh
+hatch run test:cov
+```
+
+This generates:
+*   Terminal output with a coverage summary.
+*   `coverage.xml` (XML report in the root, used by IDE integrations).
+*   `htmlcov/index.html` (HTML report for browser viewing).
+
+#### Editor Integration
+
+##### VSCode
+Install the **Coverage Gutters** extension. After running the coverage command, click the **Watch** button in the status bar to see coverage indicators in the editor margins.
+
+##### JetBrains Rider
+With the **Python** plugin installed:
+*   **Run with Coverage:** Create a Pytest run configuration and click the shield icon ("Run with Coverage").
+*   **Import Report:** Go to **Tools** -> **Show Code Coverage Data**, click **Add** (+), and select `coverage.xml`.
+
 ### Running `hatch` commands inside Docker
 
 This is useful to run in a consistent environment and easily switch between Python versions.

{kaggle-2.2.3 → kaggle-2.2.5}/README.md

@@ -38,6 +38,14 @@ kaggle --help
 
 See the [User documentation](docs/README.md) for more examples & tutorials.
 
+## Hosting a competition
+
+End-to-end host commands — scaffold a new competition, author its pages,
+tune its settings, and launch it — are documented in
+[docs/competition_creation.md](docs/competition_creation.md). Covers
+`kaggle competitions init`, `create`, `pages create`, `hosts`,
+`settings get`, `settings update`, and `launch`.
+
 ## Development
 
 ### `kagglesdk` Updates
@@ -106,6 +114,31 @@ After setting up your credentials, you can run the integration tests as follows:
 hatch run test:integration
 ```
 
+### Code Coverage
+
+We measure code coverage using `pytest-cov`.
+
+To run unit tests with coverage and generate reports:
+
+```sh
+hatch run test:cov
+```
+
+This generates:
+*   Terminal output with a coverage summary.
+*   `coverage.xml` (XML report in the root, used by IDE integrations).
+*   `htmlcov/index.html` (HTML report for browser viewing).
+
+#### Editor Integration
+
+##### VSCode
+Install the **Coverage Gutters** extension. After running the coverage command, click the **Watch** button in the status bar to see coverage indicators in the editor margins.
+
+##### JetBrains Rider
+With the **Python** plugin installed:
+*   **Run with Coverage:** Create a Pytest run configuration and click the shield icon ("Run with Coverage").
+*   **Import Report:** Go to **Tools** -> **Show Code Coverage Data**, click **Add** (+), and select `coverage.xml`.
+
 ### Running `hatch` commands inside Docker
 
 This is useful to run in a consistent environment and easily switch between Python versions.

{kaggle-2.2.3 → kaggle-2.2.5}/docs/README.md

@@ -4,15 +4,42 @@ Welcome to the Kaggle CLI documentation. This guide provides detailed informatio
 
 ## Installation
 
-Note: Ensure you have Python 3.11+ and the package manager `pip` installed.
+Note: Ensure you have Python 3.11+.
 
-Install the `kaggle` package with [pip](https://pypi.org/project/pip/):
+Recommended: install with [pipx](https://pipx.pypa.io/) or [uv](https://docs.astral.sh/uv/),
+which installs the CLI in an isolated environment and works on all platforms:
+
+```sh
+pipx install kaggle
+# or
+uv tool install kaggle
+```
+
+### Alternative: pip
+
+You can also install the package with [pip](https://pypi.org/project/pip/):
 
 ```sh
 pip install kaggle
 ```
 
-If you run into a `Command kaggle not found` error, ensure that your Python executable scripts are in your $PATH. For a local user install on Linux, the default location is `~/.local/bin`. On Windows, the default location is `$PYTHON_HOME/Scripts`.
+### Troubleshooting
+
+If you see `error: externally-managed-environment`, your operating system protects its
+system Python (this is the default on recent Debian and Ubuntu releases, among others).
+Use pipx or uv as described above. If that is not an option, you can override the
+protection with `--break-system-packages`:
+
+```sh
+pip install --break-system-packages kaggle
+```
+
+Note: this installs the package into the system Python and may conflict with packages
+managed by your OS.
+
+If you run into a `Command kaggle not found` error, ensure that your Python executable
+scripts are in your $PATH. For a local user install on Linux, the default location is
+`~/.local/bin`. On Windows, the default location is `$PYTHON_HOME/Scripts`.
 
 ## Authentication
 
@@ -55,7 +82,7 @@ The Kaggle CLI is organized into several command groups:
 *   [Competitions](./competitions.md): Manage and participate in Kaggle competitions.
 *   [Datasets](./datasets.md): Search, download, and manage Kaggle datasets.
 *   [Forums](./forums.md): Browse and read Kaggle discussion forums.
-*   [Kernels](./kernels.md): Interact with Kaggle Kernels (notebooks and scripts).
+*   [Kernels](./kernels.md): Interact with Kaggle Kernels (notebooks and scripts). Includes information on using [Kaggle Secrets](./kernels.md#using-secrets-in-kernels).
 *   [Models](./models.md): Manage your Kaggle Models.
 *   [Model Variations](./model_variations.md): Manage variations of your Kaggle Models.
 *   [Model Variation Versions](./model_variations_versions.md): Manage versions of your Kaggle Model Variations.

{kaggle-2.2.3 → kaggle-2.2.5}/docs/benchmarks.md

@@ -2,11 +2,14 @@
 
 Commands for interacting with Kaggle Benchmarks. Benchmarks let you define evaluation tasks as Python scripts, run them against one or more LLM models via the Kaggle Model Proxy, and download the results.
 
-The top-level command is `kaggle benchmarks` (alias: `kaggle b`), which has three sub-groups:
+The top-level command is `kaggle benchmarks` (alias: `kaggle b`), which has the following subcommands and groups:
 
 *   **`auth`** — Fetch Model Proxy credentials.
 *   **`init`** — Fetch credentials and default environment variables for local development.
+*   **`quota`** — Show your Model Proxy (AI inference) spend quota.
+*   **`leaderboard`** — Get benchmark leaderboard information.
 *   **`tasks`** (alias: `t`) — Manage benchmark tasks (push, run, list, status, download, log, models, delete, publish).
+*   **`topics`** — Browse discussion topics for a benchmark.
 
 ## `kaggle benchmarks auth`
 
@@ -77,7 +80,8 @@ In addition to the three credential variables written by `auth`, `init` also wri
 *   `LLM_DEFAULT_EVAL` — Default model slug for evaluation.
 *   `LLMS_AVAILABLE` — Comma-separated list of available model slugs.
 
-> **Note:** `LLMS_AVAILABLE` is a curated subset of models intended for local development and testing — it is **not** the full set of available models, and the Model Proxy token itself is not restricted to these models. To see all available models, use `kaggle benchmarks tasks models`. To run a task against any model (including those not in `LLMS_AVAILABLE`), use `kaggle benchmarks tasks run`, which executes on Kaggle's infrastructure with access to the full model catalog.
+> [!WARNING]
+> `LLMS_AVAILABLE` is a curated subset of models intended for local development and testing — it is **not** the full set of available models, and the Model Proxy token minted for local development **is** restricted to these models. To see all available models, use `kaggle benchmarks tasks models`. To run a task against any model (including those not in `LLMS_AVAILABLE`), use `kaggle benchmarks tasks run`, which executes on Kaggle's infrastructure with access to the full model catalog.
 
 `init` also creates two files alongside the example file:
 
@@ -88,10 +92,105 @@ If either file already exists, it is skipped without overwriting.
 
 ---
 
+## `kaggle benchmarks quota`
+
+Shows your current Model Proxy (AI inference) spend quota, one row per refill period.
+
+**Usage:**
+
+```bash
+kaggle benchmarks quota [options]
+```
+
+**Options:**
+
+*   `-v, --csv`: Print results in CSV format.
+*   `--format <FORMAT>`: Print results in the selected format (`csv`, `table`, `json`).
+
+**Example:**
+
+```bash
+$ kaggle b quota
+period   used    remaining  total    refillAt
+-------  ------  ---------  -------  -------------------------
+Daily    $1.20   $3.80      $5.00    2026-08-08T00:00:00+00:00
+Monthly  $14.50  $85.50     $100.00  2026-09-01T00:00:00+00:00
+```
+
+**Purpose:**
+
+Amounts are in USD and reflect inference spend through the Model Proxy — this is separate from the top-level `kaggle quota` command, which reports weekly GPU and TPU accelerator *hours*. `remaining` is derived as `total - used` and is clamped at `$0.00`, so an overage shows as zero remaining rather than a negative balance.
+
+---
+
+## `kaggle benchmarks leaderboard`
+
+Get benchmark leaderboard information.
+
+**Usage:**
+
+```bash
+kaggle benchmarks leaderboard <BENCHMARK> [options]
+```
+
+**Arguments:**
+
+*   `<BENCHMARK>`: Benchmark slug (e.g., `owner/benchmark-slug`).
+
+**Options:**
+
+*   `--version <VERSION>`: Benchmark version (optional).
+*   `-s, --show`: Show the leaderboard in the terminal.
+*   `-d, --download`: Download the leaderboard as a CSV file.
+*   `-p, --path <DIRECTORY>`: Folder where the leaderboard will be downloaded (defaults to current working directory).
+*   `-v, --csv`: Print results in CSV format (when used with `--show`).
+*   `--format <FORMAT>`: Print results in a specific format (e.g., `json`).
+
+**Examples:**
+
+1.  Show the leaderboard for a benchmark:
+
+    ```bash
+    kaggle b leaderboard owner/my-benchmark --show
+    ```
+
+2.  Download the leaderboard as CSV:
+
+    ```bash
+    kaggle b leaderboard owner/my-benchmark --download
+    ```
+
+3.  Show a specific version of the leaderboard in JSON format:
+
+    ```bash
+    kaggle b leaderboard owner/my-benchmark --version 2 --show --format json
+    ```
+
+**Purpose:**
+
+Displays or downloads the evaluation results for all models that have run tasks in the specified benchmark. The leaderboard is represented as a table where rows are model versions and columns are benchmark tasks, showing the score achieved by each model on each task.
+
+---
+
 ## Tasks Commands
 
 All tasks commands live under `kaggle benchmarks tasks` (alias: `kaggle b t`).
 
+### Task Name Format
+
+Task arguments (`<TASK>`) support two formats:
+
+*   **Bare slug** (`my-task`): Refers to a task owned by the current user.
+*   **Owner prefix** (`owner/my-task`): Refers to a specific owner's task (e.g., another user's public task, or `your-username/my-task`).
+
+| Command Group | Supported Formats | Description |
+|---|---|---|
+| **View & Run** (`run`, `status`, `download`, `log`) | `my-task`, `owner/my-task` | Interact with your own tasks or public tasks from other users |
+| **Publish** (`publish`) | `my-task`, `your-username/my-task` | Make your own task public (must be task owner) |
+| **Create** (`push`) | `my-task` only | Must match the `@task(name="...")` decorator in your Python source file |
+
+> **Slug Normalization:** Task names are automatically converted to URL-safe slugs (`My Task` → `my-task`). For `owner/task` arguments, each segment is slugified independently (`Owner/My Task` → `owner/my-task`) so the `/` separator is preserved.
+
 ### `kaggle benchmarks tasks push`
 
 Creates or updates a benchmark task from a local Python source file. The file must contain at least one function decorated with `@task`.
@@ -151,7 +250,8 @@ kaggle benchmarks tasks push <TASK> -f <FILE> [options]
 
 This command reads a `.py` file, converts it to a Jupyter notebook format, and uploads it to Kaggle as a benchmark task. If a task with the same slug already exists, a new version is created. The file is validated to ensure it contains a `@task` decorator matching the given task name.
  
-**Note on dataset attachment:** When `--kaggle-dataset` / `-d` is specified, the listed datasets are attached to the task's underlying notebook kernel. During execution, they are accessible at `/kaggle/input/<dataset-slug>/` by default, falling back to `/kaggle/input/<owner>/<dataset-slug>/` in the event of a naming conflict. If you re-push without `-d`, all previously-attached datasets are detached (a warning is printed). To preserve datasets across pushes, re-specify them each time. If any specified dataset is invalid, non-existent, or inaccessible, the push command will **fail** with an error: `Failed to push task: Failed to attach the following data sources (not found or inaccessible): <dataset>`.
+> [!NOTE]
+> **On dataset attachment:** When `--kaggle-dataset` / `-d` is specified, the listed datasets are attached to the task's underlying notebook kernel. During execution, they are accessible at `/kaggle/input/<dataset-slug>/` by default, falling back to `/kaggle/input/<owner>/<dataset-slug>/` in the event of a naming conflict. If you re-push without `-d`, all previously-attached datasets are detached (a warning is printed). To preserve datasets across pushes, re-specify them each time. If any specified dataset is invalid, non-existent, or inaccessible, the push command will **fail** with an error: `Failed to push task: Failed to attach the following data sources (not found or inaccessible): <dataset>`.
 
 ---
 
@@ -167,7 +267,7 @@ kaggle benchmarks tasks run <TASK> [options]
 
 **Arguments:**
 
-*   `<TASK>`: Task name (slug, e.g. `my-task`).
+*   `<TASK>`: Task name (slug, e.g. `my-task` or `owner/my-task`).
 
 **Options:**
 
@@ -249,7 +349,7 @@ kaggle benchmarks tasks status <TASK> [options]
 
 **Arguments:**
 
-*   `<TASK>`: Task name (slug, e.g. `my-task`).
+*   `<TASK>`: Task name (slug, e.g. `my-task` or `owner/my-task`).
 
 **Options:**
 
@@ -263,7 +363,13 @@ kaggle benchmarks tasks status <TASK> [options]
     kaggle b t status my-task
     ```
 
-2.  Show status for specific models only:
+2.  Show status for another user's task:
+
+    ```bash
+    kaggle b t status someuser/their-task
+    ```
+
+3.  Show status for specific models only:
 
     ```bash
     kaggle b t status my-task -m gemini-2.5-pro
@@ -289,7 +395,7 @@ kaggle benchmarks tasks download <TASK> [options]
 
 **Arguments:**
 
-*   `<TASK>`: Task name (slug, e.g. `my-task`).
+*   `<TASK>`: Task name (slug, e.g. `my-task` or `owner/my-task`).
 
 **Options:**
 
@@ -306,19 +412,25 @@ kaggle benchmarks tasks download <TASK> [options]
     kaggle b t download my-task
     ```
 
-2.  Download outputs for a specific model into a custom directory:
+2.  Download outputs from another user's public task:
+
+    ```bash
+    kaggle b t download someuser/their-task
+    ```
+
+3.  Download outputs for a specific model into a custom directory:
 
     ```bash
     kaggle b t download my-task -m gemini-2.5-pro -o ./results
     ```
 
-3.  Download outputs with source notebooks included:
+4.  Download outputs with source notebooks included:
 
     ```bash
     kaggle b t download my-task --include-source
     ```
 
-4.  Force re-download of previously downloaded runs:
+5.  Force re-download of previously downloaded runs:
 
     ```bash
     kaggle b t download my-task --force
@@ -370,7 +482,7 @@ kaggle benchmarks tasks log <TASK> [options]
 
 **Arguments:**
 
-*   `<TASK>`: Task name (slug, e.g. `my-task`).
+*   `<TASK>`: Task name (slug, e.g. `my-task` or `owner/my-task`).
 
 **Options:**
 
@@ -386,13 +498,19 @@ kaggle benchmarks tasks log <TASK> [options]
     kaggle b t log my-task
     ```
 
-2.  Show logs for a specific model's run(s):
+2.  Show logs for another user's task:
+
+    ```bash
+    kaggle b t log someuser/their-task
+    ```
+
+3.  Show logs for a specific model's run(s):
 
     ```bash
     kaggle b t log my-task -m gemini-2.5-pro
     ```
 
-3.  Show logs for multiple models:
+4.  Show logs for multiple models:
 
     ```bash
     kaggle b t logs my-task -m gemini-2.5-pro -m claude-sonnet-4
@@ -480,7 +598,7 @@ kaggle benchmarks tasks delete <TASK> [options]
 
 **Arguments:**
 
-*   `<TASK>`: Task name (slug, e.g. `my-task`).
+*   `<TASK>`: Task name (slug, e.g. `my-task` or `owner/my-task`).
 
 **Options:**
 
@@ -510,7 +628,7 @@ kaggle benchmarks tasks publish <TASK> [options]
  
 **Arguments:**
  
-*   `<TASK>`: Task name (slug, e.g. `my-task`).
+*   `<TASK>`: Task name (slug, e.g. `my-task` or `owner/my-task`).
  
 **Options:**