fix(cli): agents info output missing spec-required sections and fields #3907

New issue

Open

opened 2026-04-06 07:20:25 +00:00 by hurui200320 · 1 comment

hurui200320 commented

2026-04-06 07:20:25 +00:00

Member

Metadata

Commit Message: fix(cli): agents info output missing spec-required sections and fields
Branch: fix/info-missing-sections

Background

The specification (lines 692-850) defines the expected output of agents info with four sections: Environment, Runtime, Storage, and Indexing. The current implementation is missing several fields and entire sections compared to the spec.

Current Behavior

Running agents info produces:

╭── Environment ──╮
│ Data Dir: ...    │
│ Config: ...      │
│ Database: ...    │
│ Server Mode: ... │
│ Platform: ...    │
╰─────────────────╯
╭── Runtime ──────╮
│ Automation:      │  ← blank, should show default profile name
│ Providers: 6     │
│ Debug Mode: False│  ← not in spec
╰─────────────────╯
╭── Storage ──╮
│ db_size: 0  │
│ logs: 0     │
╰─────────────╯

Expected Behavior

Per the specification, agents info should also display:

Runtime section: Sessions: N active, Active Plans: N, Actors: N (all missing)
Runtime section: Automation: should show the default automation profile name (e.g., "supervised"), not be blank
Storage section: Cache: N MB, Backups: N (missing)
Indexing section (entirely missing): Text Index: ready/disabled, Vector Index: ready/disabled, Graph Store: ready/disabled, Indexed Files: N
Debug Mode: False field is not in the spec and should be removed (or moved to a --verbose view)

Subtasks

Add session count to Runtime section
Add active plans count to Runtime section
Add actor count to Runtime section
Fix Automation field to show default profile name instead of blank
Add Cache and Backups to Storage section
Add Indexing section with text/vector/graph store status
Remove or hide the non-spec Debug Mode field
Update JSON/YAML format output to match spec envelope structure
Tests (Behave): Add/update scenarios verifying all info output fields
Tests (Robot): Add integration test for info command completeness
Verify coverage >=97% via nox -s coverage_report
Run nox (all default sessions), fix any errors

Definition of Done

This issue is complete when:

All subtasks above are completed and checked off.
A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation.
The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.

## Metadata - **Commit Message**: `fix(cli): agents info output missing spec-required sections and fields` - **Branch**: `fix/info-missing-sections` ## Background The specification (lines 692-850) defines the expected output of `agents info` with four sections: Environment, Runtime, Storage, and Indexing. The current implementation is missing several fields and entire sections compared to the spec. ## Current Behavior Running `agents info` produces: ``` ╭── Environment ──╮ │ Data Dir: ... │ │ Config: ... │ │ Database: ... │ │ Server Mode: ... │ │ Platform: ... │ ╰─────────────────╯ ╭── Runtime ──────╮ │ Automation: │ ← blank, should show default profile name │ Providers: 6 │ │ Debug Mode: False│ ← not in spec ╰─────────────────╯ ╭── Storage ──╮ │ db_size: 0 │ │ logs: 0 │ ╰─────────────╯ ``` ## Expected Behavior Per the specification, `agents info` should also display: - **Runtime section**: `Sessions: N active`, `Active Plans: N`, `Actors: N` (all missing) - **Runtime section**: `Automation:` should show the default automation profile name (e.g., "supervised"), not be blank - **Storage section**: `Cache: N MB`, `Backups: N` (missing) - **Indexing section** (entirely missing): `Text Index: ready/disabled`, `Vector Index: ready/disabled`, `Graph Store: ready/disabled`, `Indexed Files: N` - **Debug Mode: False** field is not in the spec and should be removed (or moved to a `--verbose` view) ## Subtasks - [ ] Add session count to Runtime section - [ ] Add active plans count to Runtime section - [ ] Add actor count to Runtime section - [ ] Fix Automation field to show default profile name instead of blank - [ ] Add Cache and Backups to Storage section - [ ] Add Indexing section with text/vector/graph store status - [ ] Remove or hide the non-spec Debug Mode field - [ ] Update JSON/YAML format output to match spec envelope structure - [ ] Tests (Behave): Add/update scenarios verifying all info output fields - [ ] Tests (Robot): Add integration test for info command completeness - [ ] Verify coverage >=97% via `nox -s coverage_report` - [ ] Run `nox` (all default sessions), fix any errors ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done.

freemo commented

2026-04-06 07:21:06 +00:00

Owner

Thank you for filing this issue, @hurui200320. The spec reference (lines 692-850) and the comparison between current and expected output are clear and actionable.

Triage assessment:

This issue is well-formed with clear acceptance criteria. It currently has State/Unverified, Priority/Low, and Type/Bug labels.

Completeness check per CONTRIBUTING.md:

✅ Clear title
✅ Background/context with spec references
✅ Current vs expected behavior
✅ Subtasks checklist
✅ Definition of Done
✅ Metadata (commit message, branch name)
⚠️ Missing: Parent Epic link — this should be linked to an appropriate CLI or info-command epic.

Priority assessment: The Priority/Low label seems appropriate — this is a cosmetic/completeness issue rather than a functional blocker. The missing Indexing section is the most significant gap since it affects users trying to understand their index status.

Story Points estimate: S (2 points) — straightforward field additions to the info command output, though the Indexing section may require wiring up index status queries.

This issue is ready for verification and implementation once a parent epic is identified.

Automated by CleverAgents Bot
Supervisor: Human Liaison | Agent: ca-human-liaison

Thank you for filing this issue, @hurui200320. The spec reference (lines 692-850) and the comparison between current and expected output are clear and actionable. **Triage assessment:** This issue is well-formed with clear acceptance criteria. It currently has `State/Unverified`, `Priority/Low`, and `Type/Bug` labels. **Completeness check per CONTRIBUTING.md:** - ✅ Clear title - ✅ Background/context with spec references - ✅ Current vs expected behavior - ✅ Subtasks checklist - ✅ Definition of Done - ✅ Metadata (commit message, branch name) - ⚠️ Missing: Parent Epic link — this should be linked to an appropriate CLI or info-command epic. **Priority assessment**: The `Priority/Low` label seems appropriate — this is a cosmetic/completeness issue rather than a functional blocker. The missing Indexing section is the most significant gap since it affects users trying to understand their index status. **Story Points estimate**: S (2 points) — straightforward field additions to the info command output, though the Indexing section may require wiring up index status queries. This issue is ready for verification and implementation once a parent epic is identified. --- **Automated by CleverAgents Bot** Supervisor: Human Liaison | Agent: ca-human-liaison

Rows
Columns