[GH-ISSUE #5483] [Feature] Provide machine-readable version and runtime information #3334

New issue

Closed

opened 2026-10-31 00:39:17 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-31 00:39:17 +00:00

Owner

Originally created by @jayykernel on GitHub (Oct 20, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/5483

Problem

When reporting an issue or diagnosing a CLI installation, users need the REA version and the runtime/platform context. Asking users to collect this information manually makes support reports inconsistent and harder to reproduce.

Proposed change

Add a stable machine-readable form such as rea --version --json that reports the package version, Node.js version, operating system, architecture, and supported runtime-range status. Keep the existing human-readable version output unchanged.

Acceptance criteria

The JSON output has a documented schema and stable field names.
It does not include usernames, home-directory paths, environment variables, credentials, or target paths.
It exits successfully without running providers or reading a target.
Tests cover supported Node versions and normal platform/architecture values.

This is a CLI usability request; it does not claim the current version command is broken.

Originally created by @jayykernel on GitHub (Oct 20, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/5483 ### Problem When reporting an issue or diagnosing a CLI installation, users need the REA version and the runtime/platform context. Asking users to collect this information manually makes support reports inconsistent and harder to reproduce. ### Proposed change Add a stable machine-readable form such as `rea --version --json` that reports the package version, Node.js version, operating system, architecture, and supported runtime-range status. Keep the existing human-readable version output unchanged. ### Acceptance criteria - The JSON output has a documented schema and stable field names. - It does not include usernames, home-directory paths, environment variables, credentials, or target paths. - It exits successfully without running providers or reading a target. - Tests cover supported Node versions and normal platform/architecture values. This is a CLI usability request; it does not claim the current version command is broken.

bsakaguchi closed this issue

2026-10-31 00:39:17 +00:00

bsakaguchi commented

2026-10-31 00:39:18 +00:00

Author

Owner

@mhamzasakhi commented on GitHub (Oct 23, 2026):

I'd like to take this one. I'm working on rea --version --json covering the acceptance criteria above (stable documented fields, no personal paths or environment data, no provider or target access) and will open a PR shortly.

@mhamzasakhi commented on GitHub (Oct 23, 2026): I'd like to take this one. I'm working on `rea --version --json` covering the acceptance criteria above (stable documented fields, no personal paths or environment data, no provider or target access) and will open a PR shortly.

bsakaguchi referenced this issue

2026-10-31 01:10:04 +00:00

[PR #3661] [MERGED] fix(mcp): keep a snapshot open ahead of later calls on the same connection #5869

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#3334

No description provided.

Rows
Columns