cleveragents/cleveragents-core

Fork 3

`agents actor context add` is missing from documentation #1580

New issue

Open

opened 2026-04-02 22:22:00 +00:00 by brent.edwards · 3 comments

brent.edwards commented

2026-04-02 22:22:00 +00:00

Member

agents actor context remove [--yes|-y] (--all|-a|<NAME>)
agents actor context list [<REGEX>]
agents actor context show <NAME>
agents actor context export (--output|-o) <FILE> <NAME>
agents actor context import [--update] (--input|-i) <FILE> [<NAME>]
agents actor context clear [--yes|-y] (--all|-a|<NAME>)

This list is missing

agents actor context add
agents actor context load
agents actor context delete

(I was very surprised when I could not find any way to add an actor context in the documentation.)

According to http://localhost:8000/cleveragents/specification/#agents-actor-context and http://localhost:8000/cleveragents/specification/#command-synopsis , the list of commands for `agents actor context` are: ``` agents actor context remove [--yes|-y] (--all|-a|<NAME>) agents actor context list [<REGEX>] agents actor context show <NAME> agents actor context export (--output|-o) <FILE> <NAME> agents actor context import [--update] (--input|-i) <FILE> [<NAME>] agents actor context clear [--yes|-y] (--all|-a|<NAME>) ``` This list is missing ``` agents actor context add agents actor context load agents actor context delete ``` (I was very surprised when I could not find any way to add an actor context in the documentation.)

brent.edwards added this to the v3.2.0 milestone

2026-04-02 22:22:00 +00:00

brent.edwards added the

labels

2026-04-02 22:22:00 +00:00

freemo commented

2026-04-02 22:59:05 +00:00

Owner

Thank you for filing this issue, Brent. You're right that the documentation gap here is significant — users should be able to discover all available subcommands for agents actor context from the specification.

Triage Assessment:

The issue is clearly actionable: the specification's command synopsis and the agents actor context section are missing entries for add, load, and delete subcommands. This is a documentation deficiency that could confuse users trying to manage actor contexts.

Items needed to fully conform to CONTRIBUTING.md format:

Metadata section: Please add a commit message first line (e.g., docs(spec): add missing actor context add/load/delete commands to specification) and branch name (e.g., docs/actor-context-missing-commands).
Subtasks checklist: Suggest breaking this into:
1. Add agents actor context add to the command synopsis and detailed section
2. Add agents actor context load to the command synopsis and detailed section
3. Add agents actor context delete to the command synopsis and detailed section
4. Verify all three commands are documented with their full flag/argument signatures
Definition of Done: e.g., "All three missing commands appear in both the command synopsis and the detailed agents actor context section of the specification, with correct argument signatures matching the implementation."

Label observation: This issue currently has both State/In progress and State/Unverified, which is contradictory. It should be one or the other. I will not change labels without human confirmation, but this should be resolved — if work has already started, State/Unverified should be removed; if it hasn't, State/In progress should be removed.

Once the metadata and subtasks are added, this can be verified and scheduled for implementation.

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

Thank you for filing this issue, Brent. You're right that the documentation gap here is significant — users should be able to discover all available subcommands for `agents actor context` from the specification. **Triage Assessment:** The issue is clearly actionable: the specification's command synopsis and the `agents actor context` section are missing entries for `add`, `load`, and `delete` subcommands. This is a documentation deficiency that could confuse users trying to manage actor contexts. **Items needed to fully conform to CONTRIBUTING.md format:** - [ ] **Metadata section**: Please add a commit message first line (e.g., `docs(spec): add missing actor context add/load/delete commands to specification`) and branch name (e.g., `docs/actor-context-missing-commands`). - [ ] **Subtasks checklist**: Suggest breaking this into: 1. Add `agents actor context add` to the command synopsis and detailed section 2. Add `agents actor context load` to the command synopsis and detailed section 3. Add `agents actor context delete` to the command synopsis and detailed section 4. Verify all three commands are documented with their full flag/argument signatures - [ ] **Definition of Done**: e.g., "All three missing commands appear in both the command synopsis and the detailed `agents actor context` section of the specification, with correct argument signatures matching the implementation." **Label observation**: This issue currently has both `State/In progress` and `State/Unverified`, which is contradictory. It should be one or the other. I will not change labels without human confirmation, but this should be resolved — if work has already started, `State/Unverified` should be removed; if it hasn't, `State/In progress` should be removed. Once the metadata and subtasks are added, this can be verified and scheduled for implementation. --- **Automated by CleverAgents Bot** Supervisor: Human Liaison | Agent: ca-human-liaison

freemo removed the

State

Unverified

label

2026-04-02 23:00:09 +00:00

freemo commented

2026-04-02 23:00:14 +00:00

Owner

Label compliance fix applied:

Removed conflicting label: State/Unverified
Reason: Issue had both State/In progress and State/Unverified. Per CONTRIBUTING.md, each issue must have exactly one State/* label. State/In progress is the more advanced state and was retained.

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

Label compliance fix applied: - Removed conflicting label: `State/Unverified` - Reason: Issue had both `State/In progress` and `State/Unverified`. Per CONTRIBUTING.md, each issue must have exactly one `State/*` label. `State/In progress` is the more advanced state and was retained. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

freemo referenced this issue

2026-04-02 23:24:09 +00:00

[Automated] Backlog Groomer Session State — v3.7.0 #1463

freemo commented

2026-04-05 03:02:07 +00:00

Owner

⚠️ Stale issue detected

This issue has been in State/In progress with no activity for 3+ days (last updated: 2026-04-02).

Current state: State/In progress

Is this blocked? Please consider:

Updating the status if work is ongoing
Moving to State/Paused if work has been temporarily halted
Adding a comment explaining the current situation

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

⚠️ **Stale issue detected** This issue has been in `State/In progress` with no activity for **3+ days** (last updated: 2026-04-02). Current state: `State/In progress` Is this blocked? Please consider: 1. Updating the status if work is ongoing 2. Moving to `State/Paused` if work has been temporarily halted 3. Adding a comment explaining the current situation --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

freemo referenced this issue

2026-04-05 03:02:27 +00:00

[CA-AUTO] Backlog Groomer — groomer-1 — Session Tracker #2771