mammoth-cli 2.2.77__tar.gz → 2.2.79__tar.gz

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mammoth-cli
-Version: 2.2.77
+Version: 2.2.79
 Summary: Command-line interface for the Mammoth Analytics platform
 Project-URL: homepage, https://mammoth.io
 Project-URL: repository, https://github.com/EdgeMetric/mammothsdk
@@ -18,7 +18,7 @@ Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Requires-Python: <3.15,>=3.12
 Requires-Dist: jsonschema>=4.20
 Requires-Dist: keyring<26,>=25.7
-Requires-Dist: mammoth-io<0.9,>=0.8.41
+Requires-Dist: mammoth-io<0.9,>=0.8.42
 Requires-Dist: platformdirs<5,>=4.10
 Requires-Dist: pydantic<3,>=2.12.5
 Requires-Dist: pyyaml<7,>=6
@@ -243,11 +243,14 @@ mammoth skill install --input '{"agents": ["codex"], "scope": "project"}'
 Use `mammoth skill update` after a CLI upgrade. It refreshes copies owned by the
 installer and reports modified copies instead of silently replacing them.
 
-The CLI checks PyPI for a newer release at most once an hour, after a command
-has finished: every JSON envelope carries `meta.update_available` and human
-output adds one stderr line. In a terminal it also upgrades itself before the
-next command; set `MAMMOTH_AUTO_UPGRADE=0` to stop that, or
-`MAMMOTH_NO_UPDATE_CHECK=1` to turn the check off (see
+The CLI keeps itself up to date. At most once a day, after a command has
+finished and written its output, a detached process asks PyPI and installs a
+newer release through the same package manager as `mammoth upgrade`. It never
+delays or fails a command, prints nothing, and writes any failure to the run
+log. `meta.update_available` (and the stderr line in human output) appears only
+when a newer release exists and will not be installed by itself. Set
+`MAMMOTH_NO_AUTO_UPDATE=1` to keep the check but never install (CI, containers,
+pinned environments), or `MAMMOTH_NO_UPDATE_CHECK=1` to turn the check off (see
 [Upgrade](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/upgrade.md)).
 
 ## What you can do

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/README.md

@@ -214,11 +214,14 @@ mammoth skill install --input '{"agents": ["codex"], "scope": "project"}'
 Use `mammoth skill update` after a CLI upgrade. It refreshes copies owned by the
 installer and reports modified copies instead of silently replacing them.
 
-The CLI checks PyPI for a newer release at most once an hour, after a command
-has finished: every JSON envelope carries `meta.update_available` and human
-output adds one stderr line. In a terminal it also upgrades itself before the
-next command; set `MAMMOTH_AUTO_UPGRADE=0` to stop that, or
-`MAMMOTH_NO_UPDATE_CHECK=1` to turn the check off (see
+The CLI keeps itself up to date. At most once a day, after a command has
+finished and written its output, a detached process asks PyPI and installs a
+newer release through the same package manager as `mammoth upgrade`. It never
+delays or fails a command, prints nothing, and writes any failure to the run
+log. `meta.update_available` (and the stderr line in human output) appears only
+when a newer release exists and will not be installed by itself. Set
+`MAMMOTH_NO_AUTO_UPDATE=1` to keep the check but never install (CI, containers,
+pinned environments), or `MAMMOTH_NO_UPDATE_CHECK=1` to turn the check off (see
 [Upgrade](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/upgrade.md)).
 
 ## What you can do

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/mammoth_cli/__init__.py

@@ -6,7 +6,7 @@ not implement a second HTTP client and does not call private SDK members.
 
 from __future__ import annotations
 
-__version__ = "2.2.77"
+__version__ = "2.2.79"
 
 # The versioned machine output envelope contract.
 SCHEMA_VERSION = 1

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/mammoth_cli/app.py

@@ -114,7 +114,7 @@ _AGENT_SUBGROUP_DESCRIPTIONS = {
     "goldens": "Manage and run the golden cases an agent definition is proven against.",
     "memory": "Manage the facts an agent definition has learned, per project.",
     "message": "Correct the request kind of a reply in an agent chat.",
-    "plan": "Edit the waiting workflow proposal of an agent chat plan.",
+    "plan": "Approve, skip or discard the plan of an agent chat, or edit its workflow proposal.",
     "projects": "Set or clear the projects an agent definition works in.",
     "run": "Inspect and control an agent's runs.",
     "scratch": "Read, write and clear an agent definition's scratchpad notes per project.",

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/mammoth_cli/bundled_skill/mammoth-cli/references/capabilities.md

@@ -1,7 +1,7 @@
 # What is proven on release
 
 Generated from `docs/release-capability-matrix.json`; do not edit by hand.
-The CLI publishes 747 commands. 516 of them bind one of the 545 API operations in the matrix; the remainder are local commands (`schema`, `auth`, `doctor`, `log`, ...) or typed variants that share an operation (`view transform *` commands submit through `view.task.add`, except `rename-columns` and `sort`, which set view display properties through `view.update`). 262 bound commands ran once successfully on release, 1 are not supported there, and the rest are untried. Untried is not broken: discover the contract with `mammoth schema get COMMAND_ID`, run it, and treat the structured error envelope as the answer. Use an untried command normally: confirm a write with the user first, check its result with a read afterwards, and never refuse a command only because it is untried.
+The CLI publishes 753 commands. 516 of them bind one of the 545 API operations in the matrix; the remainder are local commands (`schema`, `auth`, `doctor`, `log`, ...) or typed variants that share an operation (`view transform *` commands submit through `view.task.add`, except `rename-columns` and `sort`, which set view display properties through `view.update`). 262 bound commands ran once successfully on release, 1 are not supported there, and the rest are untried. Untried is not broken: discover the contract with `mammoth schema get COMMAND_ID`, run it, and treat the structured error envelope as the answer. Use an untried command normally: confirm a write with the user first, check its result with a read afterwards, and never refuse a command only because it is untried.
 
 Status meanings:
 

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/mammoth_cli/bundled_skill/mammoth-cli/references/command-index.md

@@ -1,12 +1,12 @@
 # Published CLI command catalog
 
-This generated catalog is a lookup table for every command in the published CLI manifest, currently 747; each entry carries its release status line. It is a command-contract index, not an assertion that every backend/OpenAPI operation has a CLI binding. For an exact local CLI contract, run `mammoth schema get COMMAND_ID`; `mammoth capability list` is an API-binding inventory and can omit typed/local CLI routes. For focused workflows, read the [recipes index](recipes/index.md). Sensitive structured input must come from a private file or pipe; never put secrets in literal argv.
+This generated catalog is a lookup table for every command in the published CLI manifest, currently 753; each entry carries its release status line. It is a command-contract index, not an assertion that every backend/OpenAPI operation has a CLI binding. For an exact local CLI contract, run `mammoth schema get COMMAND_ID`; `mammoth capability list` is an API-binding inventory and can omit typed/local CLI routes. For focused workflows, read the [recipes index](recipes/index.md). Sensitive structured input must come from a private file or pipe; never put secrets in literal argv.
 
 Load only the applicable domain file:
 
 - [activity](commands/activity.md) — 2 published commands
 - [addon](commands/addon.md) — 7 published commands
-- [agent](commands/agent.md) — 51 published commands
+- [agent](commands/agent.md) — 54 published commands
 - [ai](commands/ai.md) — 5 published commands
 - [annotation](commands/annotation.md) — 5 published commands
 - [auth](commands/auth.md) — 5 published commands
@@ -20,8 +20,8 @@ Load only the applicable domain file:
 - [collection](commands/collection.md) — 16 published commands
 - [completion](commands/completion.md) — 2 published commands
 - [config](commands/config.md) — 4 published commands
-- [connector](commands/connector.md) — 22 published commands
-- [context](commands/context.md) — 3 published commands
+- [connector](commands/connector.md) — 23 published commands
+- [context](commands/context.md) — 4 published commands
 - [dashboard-qa](commands/dashboard-qa.md) — 14 published commands
 - [dashboard-template](commands/dashboard-template.md) — 12 published commands
 - [dashboard-style](commands/dashboard-style.md) — 10 published commands
@@ -51,7 +51,7 @@ Load only the applicable domain file:
 - [upgrade](commands/upgrade.md) — 1 published commands
 - [user](commands/user.md) — 8 published commands
 - [version](commands/version.md) — 1 published commands
-- [view-transform](commands/view-transform.md) — 34 published commands
+- [view-transform](commands/view-transform.md) — 35 published commands
 - [view](commands/view.md) — 103 published commands
 - [webhook](commands/webhook.md) — 7 published commands
 - [workflow](commands/workflow.md) — 20 published commands

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/agent.md

@@ -76,7 +76,7 @@ Status on release: untried; no live run recorded.
 
 Run: `mammoth agent chat`. Exact input fields: `mammoth schema get agent.chat`.
 
-Example: `mammoth agent chat --input '{"message": "Summarize revenue by region", "scope": {"sample_key": "Status"}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+Example: `mammoth agent chat --input '{"message": "Summarize revenue by region", "scope": {"type": "workspace", "workspace_id": 123}, "client_context": {"project_id": 456}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
 Result: `AgentChatResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
 
@@ -232,6 +232,26 @@ Result: `AgentMessageSetRequestKindResult`; mutation `benign_mutation`, confirma
 
 Status on release: untried; no live run recorded.
 
+### `agent.plan.approve`
+
+Run: `mammoth agent plan approve`. Exact input fields: `mammoth schema get agent.plan.approve`.
+
+Example: `mammoth agent plan approve resource-123`. Illustrative only: append `--yes` after observing an owned target.
+
+Result: `AgentPlanApproveResult`; mutation `benign_mutation`, confirmation `prompt_or_yes`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `agent.plan.discard`
+
+Run: `mammoth agent plan discard`. Exact input fields: `mammoth schema get agent.plan.discard`.
+
+Example: `mammoth agent plan discard resource-123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `AgentPlanDiscardResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `agent.plan.edit-proposal`
 
 Run: `mammoth agent plan edit-proposal`. Exact input fields: `mammoth schema get agent.plan.edit-proposal`.
@@ -242,6 +262,16 @@ Result: `AgentPlanEditProposalResult`; mutation `benign_mutation`, confirmation
 
 Status on release: untried; no live run recorded.
 
+### `agent.plan.skip`
+
+Run: `mammoth agent plan skip`. Exact input fields: `mammoth schema get agent.plan.skip`.
+
+Example: `mammoth agent plan skip resource-123 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `AgentPlanSkipResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `agent.projects.clear`
 
 Run: `mammoth agent projects clear`. Exact input fields: `mammoth schema get agent.projects.clear`.

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/batch.md

@@ -66,7 +66,7 @@ Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit
 
 Run: `mammoth batch update`. Exact input fields: `mammoth schema get batch.update`.
 
-Example: `mammoth batch update 123 --input '{"patch": [{"sample_key": "Status"}]}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+Example: `mammoth batch update 123 --input '{"patch": {"sample_key": "Status"}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
 Result: `BatchUpdateResult`; mutation `benign_mutation`, confirmation `none`, wait policy `returns_job`.
 

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/connector.md

@@ -114,6 +114,16 @@ Result: `ConnectorConnectionListResult`; mutation `read`, confirmation `none`, w
 
 Status on release: observed blocker — server_error: see sweep report. Re-check before relying on it.
 
+### `connector.connection.query`
+
+Run: `mammoth connector connection query`. Exact input fields: `mammoth schema get connector.connection.query`.
+
+Example: `mammoth connector connection query sample sample --input '{"query": "SELECT region, SUM(revenue) FROM data GROUP BY region"}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `ConnectorConnectionQueryResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `connector.connection.update`
 
 Run: `mammoth connector connection update`. Exact input fields: `mammoth schema get connector.connection.update`.

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/context.md

@@ -31,3 +31,13 @@ Example: `mammoth context project use 123`. Placeholders are illustrative; resol
 Result: `ContextProjectUseResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
 
 Status on release: untried; no live run recorded.
+
+### `context.show`
+
+Run: `mammoth context show`. Exact input fields: `mammoth schema get context.show`.
+
+Example: `mammoth context show`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `ContextShowResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/view-transform.md

@@ -32,6 +32,16 @@ Result: `ViewTransformAiResult`; mutation `reversible_pipeline`, confirmation `n
 
 Status on release: ran once on CLI 2.0.40 through `view.task.add` and was read back with `view data get`; other inputs for this transform are untried.
 
+### `view.transform.batch`
+
+Run: `mammoth view transform batch`. Exact input fields: `mammoth schema get view.transform.batch`.
+
+Example: `mammoth view transform batch 123 --input '{"steps": [{"op": "filter", "input": {"condition": {"column": "Cost", "operator": "GTE", "value": 20}}}, {"op": "sort", "input": {"order_by": [["Cost", "DESC"]]}}, {"op": "limit-rows", "input": {"n": 2}}], "dataset_id": 456}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `ViewTransformBatchResult`; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`.
+
+Status on release: untried; it submits through `view.task.add`, but this transform was not among those run.
+
 ### `view.transform.bulk-replace`
 
 Run: `mammoth view transform bulk-replace`. Exact input fields: `mammoth schema get view.transform.bulk-replace`.

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/mammoth_cli/bundled_skill/mammoth-cli/references/operations.md

@@ -94,6 +94,14 @@ task submission does not prove that the task removed duplicates.
 For deduplication, discover and use `view.transform.discard-duplicates`; see
 recipes/transforms.md for the full procedure.
 
+When several transforms go on the same view in a row (for example filter, sort, then
+limit-rows), send them in one `view transform batch VIEW_ID --input '{"steps": [{"op":
+"filter", "input": {...}}, ...]}'` instead of one command each: the pipeline runs once and
+one verified outcome comes back (`row_check`, and `tasks` with each new task's status).
+Each `input` is what that `view transform` command takes. A step cannot use a column an
+earlier step of the batch creates: run those steps first. If a task fails, the batch's tasks
+are removed and the error names `steps[i]`.
+
 Prefer a typed `view transform <operation>` command. Its schema is the
 discoverable request contract. A job status or pipeline/task definition only
 proves that the task ran. For a value-changing step, the proof is the

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/database-import.md

@@ -25,8 +25,19 @@ mammoth connector connection get mssql CONNECTION_KEY     # read it back; config
 ```
 
 There is no table-browse command. Ask the user for the table (and schema), or
-draft the SQL with `connector query generate`. Then import it as a dataset
-(a write: confirm first). `query` is required; `validate` is on by default:
+draft the SQL with `connector query generate`. Try the SELECT first: it shows
+sample rows and saves nothing (no dataset, no data source), so it needs no
+`--yes`. The CLI accepts only one SELECT (or WITH ... SELECT); the connection's
+database user decides what the database allows, and the sample is limited to
+the first rows, so add your own LIMIT for a large table:
+
+```bash
+mammoth connector connection query mssql CONNECTION_KEY \
+  --input '{"query": "SELECT TOP 5 * FROM dbo.Orders"}'
+```
+
+Then import it as a dataset (a write: confirm first). `query` is required;
+`validate` is on by default:
 
 ```bash
 mammoth connector ds-config create mssql CONNECTION_KEY \

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/exports.md

@@ -108,6 +108,14 @@ mammoth view export postgres VIEW_ID DATASET_ID --project PROJECT_ID \
 mammoth view export list VIEW_ID DATASET_ID --project PROJECT_ID
 ```
 
+The command returns after the export has run. The result carries
+`export: {id, status, error, ran_at, result}`: `status` `ok` means the run
+finished, so there is nothing to poll or read back to confirm it. A run that
+failed is an `export_failed` error naming the destination's error. With
+`"run_immediately": false` nothing runs now and `export.status` is `scheduled`.
+`mammoth job wait JOB_ID` on the add job (`add_action`) returns the same
+`export` block.
+
 If the operator has not supplied such a file, stop and ask for it; do not
 compose the body yourself from values seen in chat.
 

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/rest-api-import.md

@@ -31,6 +31,9 @@ does not include this connector (or its paid addon is not active).
 
 ## 2. Try the data-source config (creates no dataset)
 
+`mammoth connector connection query generic_rest_api CONNECTION_KEY --input
+sample.json` runs the same sample read-only (no `--yes`, nothing saved).
+
 `query` is a **JSON string** (not an object) of the data-source config:
 `endpoint_path`, `http_method` (`GET|POST`), `request_body`, `query_params`,
 `data_root_path` (JSONPath to the records; `[*]` is supported), `pagination`,

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/mammoth_cli/commands/__init__.py

@@ -21,6 +21,7 @@ _TARGETS: dict[str, str] = {
     "config.set": "mammoth_cli.commands.config:config_set",
     "config.list": "mammoth_cli.commands.config:config_list",
     "config.path": "mammoth_cli.commands.config:config_path",
+    "context.show": "mammoth_cli.commands.context:context_show",
     "context.project.status": "mammoth_cli.commands.context:context_project_status",
     "context.project.use": "mammoth_cli.commands.context:context_project_use",
     "context.project.clear": "mammoth_cli.commands.context:context_project_clear",

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/mammoth_cli/commands/agent.py

@@ -15,6 +15,7 @@ from dataclasses import replace
 from typing import Any
 
 from mammoth_cli.errors.envelope import (
+    CODE_INVALID_ARGUMENT,
     CODE_MISSING_ARGUMENT,
     CODE_MISSING_FIELD,
     CODE_RESOURCE_NOT_FOUND,
@@ -156,14 +157,25 @@ def _meta(invocation: Invocation, workspace_id: int, project_id: int | None) ->
     }
 
 
+#: Seconds ``agent chat`` waits for the reply when the input gives no ``wait``.
+CHAT_WAIT_SECONDS = 120
+
+
 def agent_chat(invocation: Invocation) -> HandlerResult:
-    """Send a chat message to an agent. ``message``/``scope`` are required."""
+    """Send a chat message to an agent and wait for its reply.
+
+    ``message``/``scope`` are required. The request key the server needs is made
+    here, never asked of the user. ``wait`` (seconds, default 120) bounds how long
+    the command waits for the reply; ``0`` returns as soon as the turn starts.
+    """
     document = _bound_document(invocation)
     message = _require_field(document, "message")
     scope = _require_field(document, "scope")
     assert document is not None
     kwargs: dict[str, Any] = {"message": message, "scope": scope}
     _forward_optional(document, kwargs, ("agent_key", "session_id", "client_context", "selection"))
+    wait = document.get("wait", CHAT_WAIT_SECONDS)
+    kwargs["wait"] = wait or None
     with open_service(invocation) as (service, auth):
         data = service.call(_symbol(invocation), **kwargs)
     return data, _meta(invocation, auth.workspace_id, resolved_project(invocation))
@@ -199,9 +211,31 @@ def agent_session_messages(invocation: Invocation) -> HandlerResult:
     session_id = _require_string_positional(invocation, "session id")
     with open_service(invocation) as (service, auth):
         data = service.call(_symbol(invocation), session_id=session_id)
+    waiting = _awaiting_plan_approval(session_id, data.get("plan"))
+    if waiting is not None:
+        data = {**data, "awaiting_plan_approval": waiting}
     return data, _meta(invocation, auth.workspace_id, resolved_project(invocation))
 
 
+def _awaiting_plan_approval(session_id: str, plan: dict[str, Any] | None) -> dict[str, Any] | None:
+    """The proposed steps and the commands that decide them, or None when none wait."""
+    proposed = [
+        {"n": step["n"], "title": step.get("title")}
+        for step in (plan or {}).get("steps", [])
+        if step.get("status") == "proposed"
+    ]
+    if not proposed:
+        return None
+    return {
+        "plan_id": plan["plan_id"] if plan else None,
+        "proposed_steps": proposed,
+        "approve": f"mammoth agent plan approve {session_id} --yes",
+        "skip": f"mammoth agent plan skip {session_id} N",
+        "discard": f"mammoth agent plan discard {session_id}",
+        "note": "Typing 'Run it' as a chat message does not approve the plan.",
+    }
+
+
 def agent_session_set_visibility(invocation: Invocation) -> HandlerResult:
     """Set an agent session's visibility. ``visibility`` comes from ``--input``."""
     session_id = _require_string_positional(invocation, "session id")
@@ -363,6 +397,64 @@ def agent_plan_edit_proposal(invocation: Invocation) -> HandlerResult:
     return _session_call(invocation, **kwargs)
 
 
+def _plan_decision(invocation: Invocation, **extra: Any) -> HandlerResult:
+    """Run an approve, skip or discard on the chat named by the positional session id.
+
+    The chat's agent, scope and project are read from the session; ``--input`` may give
+    ``scope`` to override it and ``wait`` (seconds to wait for the turn, default 120, ``0``
+    returns at once).
+    """
+    _refuse_embedded_run_control()
+    session_id = _require_string_positional(invocation, "session id")
+    document = _bound_document(invocation)
+    with open_service(invocation) as (service, auth):
+        wait = document.get("wait", CHAT_WAIT_SECONDS) or None
+        data = service.call(
+            _symbol(invocation),
+            session_id=session_id,
+            scope=document.get("scope"),
+            wait=wait,
+            **extra,
+        )
+    return data, _meta(invocation, auth.workspace_id, resolved_project(invocation))
+
+
+def agent_plan_approve(invocation: Invocation) -> HandlerResult:
+    """Approve (Run it) the chat's current plan. Prompt or ``--yes`` required."""
+    session_id = _require_string_positional(invocation, "session id")
+    enforce_confirmation(
+        invocation,
+        policy=POLICY_PROMPT_OR_YES,
+        action=f"approve the plan of agent session {session_id} and start the work",
+    )
+    return _plan_decision(invocation)
+
+
+def agent_plan_skip(invocation: Invocation) -> HandlerResult:
+    """Skip one proposed step of the chat's current plan."""
+    if len(invocation.extra_args) < 2:
+        raise CliError(
+            code=CODE_MISSING_ARGUMENT,
+            message="This command requires a step number argument.",
+            exit_status=EXIT_USAGE,
+            hint="Pass the plan step number after the session id.",
+        )
+    raw = str(invocation.extra_args[1])
+    if not raw.isdigit() or int(raw) < 1:
+        raise CliError(
+            code=CODE_INVALID_ARGUMENT,
+            message=f"The step number must be a positive whole number, got {raw!r}.",
+            exit_status=EXIT_USAGE,
+            hint="Use the n of a proposed step shown by 'mammoth agent session messages'.",
+        )
+    return _plan_decision(invocation, n=int(raw))
+
+
+def agent_plan_discard(invocation: Invocation) -> HandlerResult:
+    """Skip every proposed step of the chat's current plan."""
+    return _plan_decision(invocation)
+
+
 def _definition_call(invocation: Invocation, **kwargs: Any) -> HandlerResult:
     """Call this command's SDK method on the agent key positional plus ``kwargs``."""
     agent_key = _require_string_positional(invocation, "agent key")

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/mammoth_cli/commands/batch.py

@@ -381,8 +381,9 @@ def batch_update(invocation: Invocation) -> HandlerResult:
     patch = _require_field(document, "patch")
     # A ``remove`` op deletes batches, so gate any patch containing one behind a
     # prompt/``--yes``; pure ``replace``/``add`` patches stay unconfirmed.
-    if isinstance(patch, list) and any(
-        isinstance(op, dict) and op.get("op") == "remove" for op in patch
+    operations = [patch] if isinstance(patch, dict) else patch
+    if isinstance(operations, list) and any(
+        isinstance(op, dict) and op.get("op") == "remove" for op in operations
     ):
         enforce_confirmation(
             invocation,

{mammoth_cli-2.2.77 → mammoth_cli-2.2.79}/mammoth_cli/commands/connector.py

@@ -24,6 +24,7 @@ SDK method named by the command's reviewed manifest ``sdk_symbol``.
 
 from __future__ import annotations
 
+import re
 from typing import Any
 
 from mammoth_cli.errors.envelope import (
@@ -46,6 +47,17 @@ from mammoth_cli.runtime.session import open_service, require_project, resolved_
 HandlerResult = tuple[Any, dict[str, Any]]
 
 _DS_CONFIG_CREATE_OPTIONAL = ("query", "file_source", "table", "profile", "validate", "data_sample")
+_QUERY_OPTIONAL = ("table", "profile")
+
+_SQL_STRING = re.compile(r"'(?:[^']|'')*'|\"(?:[^\"]|\"\")*\"|--[^\n]*|/\*.*?\*/", re.DOTALL)
+_SQL_READ_START = re.compile(r"^\s*\(*\s*(select|with|show|values)\b", re.IGNORECASE)
+_SQL_WRITE_WORD = re.compile(
+    r"\b(insert|update|delete|merge|drop|alter|truncate|create|grant|revoke|call|copy|" r"into)\b",
+    re.IGNORECASE,
+)
+
+
+_ACTIVE_CONNECTORS_SYMBOL = "mammoth.api.connectors.ConnectorsAPI.active_connectors"
 
 
 def _symbol(invocation: Invocation) -> str:
@@ -307,31 +319,31 @@ def connector_connection_get(invocation: Invocation) -> HandlerResult:
     return data, _meta(invocation, auth.workspace_id, project_id)
 
 
-def _require_connector_key_for_connection_list(invocation: Invocation) -> str:
-    """Return the connector key, or raise a usage error that says how to find one."""
-    connector_key = _string_positional_at(invocation, 0, "connector key")
-    if connector_key:
-        return connector_key
-    raise CliError(
-        code=CODE_MISSING_ARGUMENT,
-        message=(
-            "This command requires a connector key argument. "
-            "Run `mammoth connector active` to list the connectors that have saved connections."
-        ),
-        exit_status=EXIT_USAGE,
-        hint="Pass the connector key as a positional argument.",
-    )
-
-
 def connector_connection_list(invocation: Invocation) -> HandlerResult:
-    """List connections for a connector type; find its key with `mammoth connector active`."""
+    """List connections for one connector type, or for every connector with a saved one."""
     project_id = require_project(invocation)
-    connector_key = _require_connector_key_for_connection_list(invocation)
+    connector_key = _string_positional_at(invocation, 0, "connector key")
     with open_service(invocation) as (service, auth):
-        data = service.call(_symbol(invocation), connector_key=connector_key, project_id=project_id)
+        if connector_key:
+            data = service.call(
+                _symbol(invocation), connector_key=connector_key, project_id=project_id
+            )
+        else:
+            data = _connections_of_every_connector(service, invocation, project_id)
     return data, _meta(invocation, auth.workspace_id, project_id)
 
 
+def _connections_of_every_connector(
+    service: Any, invocation: Invocation, project_id: int
+) -> list[dict[str, Any]]:
+    """Each active connector's connections, every row carrying its ``connector_key``."""
+    rows: list[dict[str, Any]] = []
+    for key in service.call(_ACTIVE_CONNECTORS_SYMBOL):
+        listed = service.call(_symbol(invocation), connector_key=key, project_id=project_id)
+        rows.extend({"connector_key": key, **connection} for connection in listed)
+    return rows
+
+
 def connector_connection_update(invocation: Invocation) -> HandlerResult:
     """Update a connection's credentials. ``--yes`` is always required.
 
@@ -359,6 +371,51 @@ def connector_connection_update(invocation: Invocation) -> HandlerResult:
     return data, _meta(invocation, auth.workspace_id, project_id)
 
 
+def _require_read_only_sql(query: Any) -> str:
+    """Return ``query`` when it is one SELECT-style statement, or raise usage.
+
+    A first line of defence only: Mammoth runs the SQL as the connection's
+    database user, so that user's grants are what finally stop a write.
+    """
+    if not isinstance(query, str) or not query.strip():
+        raise CliError(
+            code=CODE_INVALID_ARGUMENT,
+            message="The 'query' input field must be a non-empty SQL string.",
+            exit_status=EXIT_USAGE,
+        )
+    bare = _SQL_STRING.sub(" ", query).strip().rstrip(";").strip()
+    if ";" in bare or not _SQL_READ_START.match(bare) or _SQL_WRITE_WORD.search(bare):
+        raise CliError(
+            code=CODE_INVALID_ARGUMENT,
+            message="connector connection query runs one read-only SELECT statement.",
+            exit_status=EXIT_USAGE,
+            hint=(
+                "Send a single SELECT (or WITH ... SELECT) without INSERT, UPDATE, DELETE or "
+                "DDL. To import rows as a dataset use 'dataset create'."
+            ),
+        )
+    return query
+
+
+def connector_connection_query(invocation: Invocation) -> HandlerResult:
+    """Run one SELECT on a connection and return sample rows; saves nothing, no ``--yes``."""
+    project_id = require_project(invocation)
+    connector_key = _require_string_positional_at(invocation, 0, "connector key")
+    connection_key = _require_string_positional_at(invocation, 1, "connection key")
+    document = invocation.load_input()
+    kwargs: dict[str, Any] = {
+        "connector_key": connector_key,
+        "connection_key": connection_key,
+        "query": _require_read_only_sql(_require_field(document, "query")),
+        "project_id": project_id,
+    }
+    assert document is not None
+    _forward_optional(document, kwargs, _QUERY_OPTIONAL)
+    with open_service(invocation) as (service, auth):
+        data = service.call(_symbol(invocation), **kwargs)
+    return data, _meta(invocation, auth.workspace_id, project_id)
+
+
 def connector_ds_config_create(invocation: Invocation) -> HandlerResult:
     """Sample a data source config; REST ``query`` is a JSON string. ``--yes`` always needed."""
     project_id = require_project(invocation)