You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All other status-type commands (info, repo-info, repo-list, list, diff, prune) already offer --json or --json-lines, so tooling can consume their output without scraping text. analyze is the odd one out, and its output is exactly the kind of data monitoring/agent tooling wants (e.g. a read-only MCP status server, see #9955).
Proposal: add --json to borg analyze, emitting the same numbers the text report is rendered from (raw byte values, not pre-formatted sizes), for both the default mode and --by-name.
borg analyzecurrently only produces human-readable text output:--by-namerepository decomposition table (per-name archives / source / stored / compression, shared, unreferenced).All other status-type commands (
info,repo-info,repo-list,list,diff,prune) already offer--jsonor--json-lines, so tooling can consume their output without scraping text.analyzeis the odd one out, and its output is exactly the kind of data monitoring/agent tooling wants (e.g. a read-only MCP status server, see #9955).Proposal: add
--jsontoborg analyze, emitting the same numbers the text report is rendered from (raw byte values, not pre-formatted sizes), for both the default mode and--by-name.