Hi — flow --once --json is already useful for scripts and dashboards.
Current output tested on macOS:
{
"download_bps": 0,
"interface": "en0",
"peak_down_bps": 0,
"peak_up_bps": 0,
"unit_display": "B/s",
"upload_bps": 0
}
Feature request: enrich the existing JSON snapshot output with a few self-contained fields:
{
"status": "ok",
"timestamp": "2026-07-08T08:13:00+10:00",
"interface": "en0",
"download_bps": 710,
"upload_bps": 0,
"download_human": "710 B/s",
"upload_human": "0 B/s",
"peak_down_bps": 0,
"peak_up_bps": 0,
"unit_display": "B/s"
}
Why this helps:
- timestamp makes each snapshot self-contained.
- status avoids consumers needing to infer success from missing/error fields.
- download_human and upload_human let simple dashboards display values directly.
- Existing numeric fields remain machine-friendly.
- No daemon/history/database behavior needed.
Non-goals:
- no change to TUI behavior
- no database/history tracking
- no new dependency required
- no need to add today totals unless they become available cleanly later
This would make the existing one-shot JSON mode more useful while keeping the current architecture intact.
Hi —
flow --once --jsonis already useful for scripts and dashboards.Current output tested on macOS:
{
"download_bps": 0,
"interface": "en0",
"peak_down_bps": 0,
"peak_up_bps": 0,
"unit_display": "B/s",
"upload_bps": 0
}
Feature request: enrich the existing JSON snapshot output with a few self-contained fields:
{
"status": "ok",
"timestamp": "2026-07-08T08:13:00+10:00",
"interface": "en0",
"download_bps": 710,
"upload_bps": 0,
"download_human": "710 B/s",
"upload_human": "0 B/s",
"peak_down_bps": 0,
"peak_up_bps": 0,
"unit_display": "B/s"
}
Why this helps:
Non-goals:
This would make the existing one-shot JSON mode more useful while keeping the current architecture intact.