Storage tables is single-project, inconsistent with other read commands

[ondrej-lorenc]

Context

Discovered while auditing 14 Keboola projects for a single question: "Which Snowflake writers are active, part of a scheduled flow, and load a source table larger than 1 GB in full-load mode?" The audit should be answerable end-to-end from the CLI / MCP tools, but several gaps forced manual workarounds. This issue covers one of them; the audit uncovered three more, filed separately.

Problem

The skill documentation states: "Multi-project by default: read commands query ALL connected projects in parallel -- no need to loop." This is true for config list, config search, job list, component list, etc. But storage tables requires --project and errors out without it.

Steps to reproduce

kbagent --json storage tables
# -> requires --project

Workaround used

Looped over 12 projects, one kbagent storage tables --project X each, writing to per-project JSON files.

Use case

Any cross-project storage audit: total data size per organization, finding tables >1 GB, finding orphan tables, cross-project dependency/lineage questions. Same pattern as other multi-project reads.

[ondrej-lorenc]

Root cause: the model didn't use the locally synced data

After filing these issues, I discovered that the originating audit could have been probably answered entirely from the kbagent sync pull output on disk, without any of the API workarounds that motivated the issues.

So the four issues are not CLI bugs — they are symptoms of the model never reaching for the right tool.

What would actually help: skill guidance

The underlying problem is that the kbagent skill does not steer the model toward the synced filesystem for read-heavy, cross-project audits. The main skill page lists reading-synced-data.md as one of many references, but there is no strong signal that says:

For cross-project read/audit tasks ("find all X where Y", "inventory Z", "which configs have property P"), prefer the synced directory over API commands.

[padak]

Fixed in v0.21.2 via #212 — kbagent storage tables now accepts zero-or-more --project flags and queries all connected projects in parallel, matching the multi-project behaviour of storage buckets, config list, job list. No more 12-project shell loops.

JSON envelope follows the existing multi-project shape: {"tables": [...], "errors": [...]} with project_alias on each row; per-project failures accumulate without aborting the batch. --branch still requires exactly one --project (branches are per-project state).

Thanks again for the precise audit write-up — the 14-project use case directly informed the JSON envelope shape.

Release: https://github.com/padak/keboola_agent_cli/releases/tag/v0.21.2