cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.0k Pull Requests 115 Actions Packages Projects Releases Wiki Activity

fix(cli): add missing --depth-gradient flag to project context set #889

New Issue
Closed
opened 2026-03-13 23:27:26 +00:00 by freemo · 1 comment
freemo commented 2026-03-13 23:27:26 +00:00
Owner
Copy Link
Copy Source

Metadata

  • Commit Message: fix(cli): add --depth-gradient flag to project context set
  • Branch: feature/m4-context-depth-gradient

Background and Context

The specification defines agents project context set with a --depth-gradient <HOP:INT_OR_NAME> repeatable flag (CLI Synopsis line 253). This flag controls how context detail depth degrades with graph distance from focus nodes — a key ACMS feature for managing context budget across related resources.

The current implementation in src/cleveragents/cli/commands/project_context.py includes 22 flags but does not include --depth-gradient. The underlying _default_acms_config() function at line 179 includes a "depth_gradient": {} default, confirming the domain model supports it, but the CLI does not expose it.

Spec reference: [--depth-gradient <HOP:INT_OR_NAME>]... on agents project context set

Expected Behavior

agents project context set --depth-gradient 1:summary --depth-gradient 2:outline --depth-gradient 3:title myproject should configure per-hop depth degradation for the project's context policy.

Acceptance Criteria

  • --depth-gradient flag is added to project context set (repeatable)
  • Flag accepts HOP:INT_OR_NAME format (e.g., 1:summary, 2:5, 3:title)
  • Values are parsed and stored in the project's ContextConfig.depth_gradient field
  • Invalid formats produce clear error messages
  • project context show displays configured depth gradients
  • Multiple --depth-gradient flags in one command are all applied

Subtasks

  • Add --depth-gradient Typer option to project_context.py set command
  • Implement parsing logic for HOP:INT_OR_NAME format
  • Store parsed values in ProjectContextPolicy
  • Display depth gradient in project context show output
  • Tests (Behave): Scenarios for valid gradients, invalid formats, multiple values
  • 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): add --depth-gradient flag to project context set` - **Branch**: `feature/m4-context-depth-gradient` ## Background and Context The specification defines `agents project context set` with a `--depth-gradient <HOP:INT_OR_NAME>` repeatable flag (CLI Synopsis line 253). This flag controls how context detail depth degrades with graph distance from focus nodes — a key ACMS feature for managing context budget across related resources. The current implementation in `src/cleveragents/cli/commands/project_context.py` includes 22 flags but does **not** include `--depth-gradient`. The underlying `_default_acms_config()` function at line 179 includes a `"depth_gradient": {}` default, confirming the domain model supports it, but the CLI does not expose it. **Spec reference**: `[--depth-gradient <HOP:INT_OR_NAME>]...` on `agents project context set` ## Expected Behavior `agents project context set --depth-gradient 1:summary --depth-gradient 2:outline --depth-gradient 3:title myproject` should configure per-hop depth degradation for the project's context policy. ## Acceptance Criteria - [ ] `--depth-gradient` flag is added to `project context set` (repeatable) - [ ] Flag accepts `HOP:INT_OR_NAME` format (e.g., `1:summary`, `2:5`, `3:title`) - [ ] Values are parsed and stored in the project's `ContextConfig.depth_gradient` field - [ ] Invalid formats produce clear error messages - [ ] `project context show` displays configured depth gradients - [ ] Multiple `--depth-gradient` flags in one command are all applied ## Subtasks - [ ] Add `--depth-gradient` Typer option to `project_context.py` `set` command - [ ] Implement parsing logic for `HOP:INT_OR_NAME` format - [ ] Store parsed values in `ProjectContextPolicy` - [ ] Display depth gradient in `project context show` output - [ ] Tests (Behave): Scenarios for valid gradients, invalid formats, multiple values - [ ] 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 added the
Points
2
Priority
Medium
State
Verified
Type
Task
 labels 2026-03-13 23:30:23 +00:00
freemo added this to the v3.4.0 milestone 2026-03-13 23:30:32 +00:00
hurui200320 was assigned by freemo 2026-03-14 04:26:58 +00:00
hurui200320 was unassigned by freemo 2026-03-29 02:30:30 +00:00
freemo self-assigned this 2026-03-29 02:30:30 +00:00
freemo added
State
In Progress
 and removed
State
Verified
 labels 2026-03-29 02:30:40 +00:00
freemo commented 2026-03-29 03:36:26 +00:00
Author
Owner
Copy Link
Copy Source

Implementation Notes

PR: #1186 | Branch: feature/m4-context-depth-gradient | Commit: 4a48e4f2

Changes

src/cleveragents/cli/commands/project_context.py

  • Added --depth-gradient as a repeatable List[str] Typer option to the context_set command (inserted between --skeleton-ratio and --auto-refresh)
  • Parsing logic: splits on first :, validates hop is non-negative integer, value parsed as int or kept as named level string
  • Stores parsed gradient as dict[str, int | str] in acms["depth_gradient"]
  • Updated context_show rich output to display depth gradient (sorted by hop number)

features/project_context_depth_gradient.feature (6 scenarios)

  • Single integer gradient (0:9)
  • Single named level gradient (1:SIGNATURES)
  • Multiple gradients (0:9,1:4,2:MODULE_LISTING)
  • Invalid format (missing colon) → exit 1
  • Invalid hop (non-integer) → exit 1
  • Display in context show output

Nox Results

  • lint: pass
  • format: pass (1705 files unchanged)
  • typecheck: 0 errors, 0 warnings, 0 informations
  • unit_tests (context features): 56 scenarios passed, 0 failed across 4 feature files
## Implementation Notes PR: #1186 | Branch: `feature/m4-context-depth-gradient` | Commit: `4a48e4f2` ### Changes **`src/cleveragents/cli/commands/project_context.py`** - Added `--depth-gradient` as a repeatable `List[str]` Typer option to the `context_set` command (inserted between `--skeleton-ratio` and `--auto-refresh`) - Parsing logic: splits on first `:`, validates hop is non-negative integer, value parsed as int or kept as named level string - Stores parsed gradient as `dict[str, int | str]` in `acms["depth_gradient"]` - Updated `context_show` rich output to display depth gradient (sorted by hop number) **`features/project_context_depth_gradient.feature`** (6 scenarios) - Single integer gradient (`0:9`) - Single named level gradient (`1:SIGNATURES`) - Multiple gradients (`0:9,1:4,2:MODULE_LISTING`) - Invalid format (missing colon) → exit 1 - Invalid hop (non-integer) → exit 1 - Display in `context show` output ### Nox Results - `lint`: pass - `format`: pass (1705 files unchanged) - `typecheck`: 0 errors, 0 warnings, 0 informations - `unit_tests` (context features): 56 scenarios passed, 0 failed across 4 feature files
freemo added
State
In Review
 and removed
State
In Progress
 labels 2026-03-29 09:31:00 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.
 controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.
 overdue
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.
 auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.
 auto/claimed-implementer
Currently being processed by an implementer worker.
 auto/claimed-merge
Currently being processed by the merge driver.
 auto/claimed-reviewer
Currently being processed by a reviewer worker.
 auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.
 auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.
 auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.
 auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.
 auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.
 auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.
 Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.
 auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.
 auto/needs-implementer
Failing CI needs implementer attention.
 auto/postmortem
Documenting a driver incident or rollback.
 auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.
 auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.
 auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.
 auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.
 auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.
 auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.
 Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.
Bounty
$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue
Bounty
$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue
Bounty
$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue
Bounty
$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue
Bounty
$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue
Bounty
$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue
Bounty
$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue
Bounty
$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue
Bounty
$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue
Bounty
$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue
MoSCoW
Could have
Could have feature in order to satisfy the epic/legendary.
MoSCoW
Must have
Must have feature in order to satisfy the epic/legendary.
MoSCoW
Should have
Should have feature in order to satisfy the epic/legendary.
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.
Points
1
1 man-hours worth of work for an expert with no learning curve.
Points
13
13 man-hours worth of work for an expert with no learning curve.
Points
2
2 man-hours worth of work for an expert with no learning curve.
Points
21
21 man-hours worth of work for an expert with no learning curve.
Points
3
3 man-hours worth of work for an expert with no learning curve.
Points
34
34 man-hours worth of work for an expert with no learning curve.
Points
5
5 man-hours worth of work for an expert with no learning curve.
Points
55
55 man-hours worth of work for an expert with no learning curve.
Points
8
8 man-hours worth of work for an expert with no learning curve.
Points
88
88 man-hours worth of work for an expert with no learning curve.
Priority
Backlog
This ticket has backlogged priority and is not to be worked on yet
Priority
CI Blocker
Critical priority issue that blocks CI/CD pipeline and prevents PR merges
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.
State
Completed
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.
State
Duplicate
A ticket that represents the same content as an existing ticket.
State
In Progress
A ticket that is actively being developed.
State
In Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.
State
Paused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.
State
Unverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.
State
Verified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.
State
Wont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.
Type
Automation
Any edits or discussion about the AI automated coding system.
Type
Bug
Something that doesnt work as intended.
Type
Discussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.
Type
Documentation
An error or improvement needed in the documentation.
Type
Epic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.
Type
Feature
Some new functionality not present.
Type
Legendary
A type of Epic which will contain other Epics.
Type
Refactor
A code change that restructures existing code without changing its external behavior.
Type
Support
Someone needs help using the project.
Type
Task
A generic task that doesnt fit into the other type categories.
Type
Testing
Work exclusively focusing on fixing or expanding testing.
No Label
Points
2
Priority
Medium
State
In Review
Type
Task
Milestone
No items
No Milestone v3.4.0
Projects
Clear projects
No project
Assignees
Clear assignees
aditya (Aditya Chhabra) aleenaumair (Aleena Umair) brent.edwards (Brent Edwards) CoreRasurae (Luis Mendes) drew (Drew Morris) eugen.thaci (Eugen Thaci) freemo (Jeffrey Phillips Freeman) HAL9000 (HAL 9000) HAL9001 (HAL9001) hamza.khyari (Hamza Khyari) hurui200320 (Rui Hu) justin.morris khird (Kyle Hird) org.cleveragents
No Assignees freemo
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cleveragents/cleveragents-core#889
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?