UAT: `agents resource add fs-mount` uses `--path` flag but spec requires `--mount-path` #4625

New issue

Open

opened 2026-04-08 17:39:45 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-08 17:39:45 +00:00

Owner

Bug Report

Feature Area: Resource registry — fs-mount resource type CLI argument
Severity: High — users following the spec cannot register fs-mount resources with the documented flag
Discovered by: UAT worker uat-worker-resource-registry-001

What Was Tested

The CLI argument name for the fs-mount resource type's path parameter.

Expected Behavior (from spec)

Per the specification (lines 10643, 10775, 24950), the fs-mount resource type uses --mount-path as the CLI argument:

$ agents resource add fs-mount local/docs --mount-path /docs/api-reference

The spec output also shows the field as Mount Path: (not Path:):

Resource
  Name: local/docs
  Type: fs-mount
  Mount Path: /docs/api-reference

Actual Behavior

The fs-mount built-in type definition in src/cleveragents/application/services/_resource_registry_data.py (lines 76–99) declares the CLI argument as path (not mount-path):

"cli_args": [
    {
        "name": "path",          # ← should be "mount-path"
        "type": "path",
        "required": True,
        "description": "Path to the mount point.",
    },
],

This means the CLI flag is --path (same as git-checkout and fs-directory), not --mount-path as the spec requires. Users following the spec's examples will get:

Error: No such option: --mount-path

Code Location

src/cleveragents/application/services/_resource_registry_data.py, lines 76–99 (the fs-mount type definition in _GIT_FS_CONTAINER_TYPES)

Fix Required

Change the fs-mount CLI arg name from "path" to "mount-path" in the built-in type definition:

"cli_args": [
    {
        "name": "mount-path",   # ← fix: was "path"
        "type": "path",
        "required": True,
        "description": "Path to the mount point.",
    },
],

Also update the resource add command's --path flag handling to pass the value as mount-path for fs-mount resources, or update the display to show Mount Path: instead of Path:.

Impact

All spec examples using agents resource add fs-mount ... --mount-path will fail
The spec's Example 1 (lines 24950) and the agents resource add reference (lines 10643, 10775) are broken

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: uat-tester

## Bug Report **Feature Area:** Resource registry — `fs-mount` resource type CLI argument **Severity:** High — users following the spec cannot register `fs-mount` resources with the documented flag **Discovered by:** UAT worker uat-worker-resource-registry-001 --- ## What Was Tested The CLI argument name for the `fs-mount` resource type's path parameter. ## Expected Behavior (from spec) Per the specification (lines 10643, 10775, 24950), the `fs-mount` resource type uses `--mount-path` as the CLI argument: ```bash $ agents resource add fs-mount local/docs --mount-path /docs/api-reference ``` The spec output also shows the field as `Mount Path:` (not `Path:`): ``` Resource Name: local/docs Type: fs-mount Mount Path: /docs/api-reference ``` ## Actual Behavior The `fs-mount` built-in type definition in `src/cleveragents/application/services/_resource_registry_data.py` (lines 76–99) declares the CLI argument as `path` (not `mount-path`): ```python "cli_args": [ { "name": "path", # ← should be "mount-path" "type": "path", "required": True, "description": "Path to the mount point.", }, ], ``` This means the CLI flag is `--path` (same as `git-checkout` and `fs-directory`), not `--mount-path` as the spec requires. Users following the spec's examples will get: ``` Error: No such option: --mount-path ``` ## Code Location `src/cleveragents/application/services/_resource_registry_data.py`, lines 76–99 (the `fs-mount` type definition in `_GIT_FS_CONTAINER_TYPES`) ## Fix Required Change the `fs-mount` CLI arg name from `"path"` to `"mount-path"` in the built-in type definition: ```python "cli_args": [ { "name": "mount-path", # ← fix: was "path" "type": "path", "required": True, "description": "Path to the mount point.", }, ], ``` Also update the `resource add` command's `--path` flag handling to pass the value as `mount-path` for `fs-mount` resources, or update the display to show `Mount Path:` instead of `Path:`. ## Impact - All spec examples using `agents resource add fs-mount ... --mount-path` will fail - The spec's Example 1 (lines 24950) and the `agents resource add` reference (lines 10643, 10775) are broken --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added this to the v3.5.0 milestone

2026-04-08 17:41:18 +00:00