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

Bug: namespace prefix confused with provider name when executing a plan #11254

New Issue
Closed
opened 2026-05-21 17:09:55 +00:00 by CoreRasurae · 0 comments
CoreRasurae commented 2026-05-21 17:09:55 +00:00
Member
Copy Link
Copy Source

Metadata

  • Branch: bugfix/m3-namespace-provider-name-collision

Background and Context

When an action YAML references actors using namespace/name format (e.g., strategy_actor: local/strategist), the plan execution flow incorrectly interprets the namespace prefix (local) as a provider name. This causes a ValueError: Unknown provider type: local when trying to execute the plan.

The root cause is that / is used as a separator in two incompatible conventions with no disambiguation:

  1. Provider/model format: openai/gpt-4 — used in actor YAML config files
  2. Namespace/name format: local/strategist — used in action YAML config files for strategy_actor and execution_actor fields

The _parse_actor_name() functions (present in both src/cleveragents/application/services/strategy_resolution.py and src/cleveragents/application/services/llm_actors.py) assume everything containing a / is provider/model. When action YAML uses strategy_actor: local/strategist, the namespace local is mistaken for a provider name.

Steps to Reproduce

  1. Create an action YAML with namespace-prefixed actors: 
    name: local/my-action
description: Test action
definition_of_done: Done
strategy_actor: local/my-strategist
execution_actor: local/my-executor
  2. Create an actor YAML with a valid provider: 
    name: local/my-strategist
type: llm
config:
  actor: openai/gpt-4
  3. Register both, create a project, and use the action to create a plan
  4. Attempt agents plan execute <PLAN_ID>

Expected Behavior

The namespace local/strategist should be resolved through the Actor Registry to find the actual actor configuration, which would then provide the correct provider (e.g., openai) and model (e.g., gpt-4).

Actual Behavior

ValueError: Unknown provider type: local is raised.

Technical Details

Root cause chains

_parse_actor_name() — two copies, same bug:

  • src/cleveragents/application/services/strategy_resolution.py:102-133 — splits on /, assumes provider/model
  • src/cleveragents/application/services/llm_actors.py:93-106 — splits on /, hardcodes openai as default

ValueError raised at:

  • src/cleveragents/providers/registry.py:656-660 — ProviderType("local") fails because local is not a valid provider enum value

Action model stores raw namespace/name values:

  • src/cleveragents/domain/models/core/action.py:373-376 — strategy_actor field documented as "namespaced name" but not resolved to provider/model
  • src/cleveragents/domain/models/core/action.py:638-644 — from_config() passes strategy_actor and execution_actor through without resolution

Plan propagates the raw value:

  • src/cleveragents/application/services/plan_lifecycle_service.py:1104-1105 — plan.strategy_actor = action.strategy_actor (still local/strategist)

All affected call sites:

Call Site File Actor Field Used
StrategyActor._execute_with_llm() strategy_actor.py:454-467 action.strategy_actor
LLMStrategizeActor.execute() llm_actors.py:147-161 action.strategy_actor
LLMExecuteActor.execute() llm_actors.py:376-393 action.execution_actor
SessionWorkflow._resolve_llm() session_workflow.py:383-391 any actor_name

Additionally, validate_namespaced_actor() at src/cleveragents/cli/commands/plan.py:119-137 conflates the two conventions by accepting openai/gpt-4 as a valid namespace/name format in its docstring.

Code flow

1. Action YAML: strategy_actor: local/strategist  (namespace/name)
2. Action.from_config() stores "local/strategist"
3. Plan created with plan.strategy_actor = "local/strategist"
4. agents plan execute <PLAN_ID>
5. StrategyActor._execute_with_llm() reads action.strategy_actor = "local/strategist"
6. _parse_actor_name("local/strategist") splits on "/" -> ("local", "strategist")
7. registry.create_llm(provider_type="local") -> ValueError: Unknown provider type: local

Suggested Fix

The _parse_actor_name() functions need to distinguish between the two / conventions. Approaches:

A) Check if the first segment is a known provider (in ProviderType enum) — if not, treat it as namespace/actor-name and resolve through the Actor Registry to get the actual provider/model

B) Change the action YAML convention to use a different separator for namespace/name (e.g., ::), breaking the ambiguity at the syntax level

Option (A) is preferred as it is backward-compatible and follows the spec, which defines actor references in action YAML as namespaced names.

## Metadata - **Branch**: `bugfix/m3-namespace-provider-name-collision` ## Background and Context When an action YAML references actors using namespace/name format (e.g., `strategy_actor: local/strategist`), the plan execution flow incorrectly interprets the namespace prefix (`local`) as a provider name. This causes a `ValueError: Unknown provider type: local` when trying to execute the plan. The root cause is that `/` is used as a separator in **two incompatible conventions** with no disambiguation: 1. **Provider/model format**: `openai/gpt-4` — used in actor YAML config files 2. **Namespace/name format**: `local/strategist` — used in action YAML config files for `strategy_actor` and `execution_actor` fields The `_parse_actor_name()` functions (present in both `src/cleveragents/application/services/strategy_resolution.py` and `src/cleveragents/application/services/llm_actors.py`) assume **everything** containing a `/` is `provider/model`. When action YAML uses `strategy_actor: local/strategist`, the namespace `local` is mistaken for a provider name. ## Steps to Reproduce 1. Create an action YAML with namespace-prefixed actors: ```yaml name: local/my-action description: Test action definition_of_done: Done strategy_actor: local/my-strategist execution_actor: local/my-executor ``` 2. Create an actor YAML with a valid provider: ```yaml name: local/my-strategist type: llm config: actor: openai/gpt-4 ``` 3. Register both, create a project, and use the action to create a plan 4. Attempt `agents plan execute <PLAN_ID>` ## Expected Behavior The namespace `local/strategist` should be resolved through the Actor Registry to find the actual actor configuration, which would then provide the correct provider (e.g., `openai`) and model (e.g., `gpt-4`). ## Actual Behavior `ValueError: Unknown provider type: local` is raised. ## Technical Details ### Root cause chains **`_parse_actor_name()` — two copies, same bug:** - `src/cleveragents/application/services/strategy_resolution.py:102-133` — splits on `/`, assumes `provider/model` - `src/cleveragents/application/services/llm_actors.py:93-106` — splits on `/`, hardcodes `openai` as default **ValueError raised at:** - `src/cleveragents/providers/registry.py:656-660` — `ProviderType("local")` fails because `local` is not a valid provider enum value **Action model stores raw namespace/name values:** - `src/cleveragents/domain/models/core/action.py:373-376` — `strategy_actor` field documented as "namespaced name" but not resolved to provider/model - `src/cleveragents/domain/models/core/action.py:638-644` — `from_config()` passes `strategy_actor` and `execution_actor` through without resolution **Plan propagates the raw value:** - `src/cleveragents/application/services/plan_lifecycle_service.py:1104-1105` — `plan.strategy_actor = action.strategy_actor` (still `local/strategist`) **All affected call sites:** | Call Site | File | Actor Field Used | |---|---|---| | `StrategyActor._execute_with_llm()` | `strategy_actor.py:454-467` | `action.strategy_actor` | | `LLMStrategizeActor.execute()` | `llm_actors.py:147-161` | `action.strategy_actor` | | `LLMExecuteActor.execute()` | `llm_actors.py:376-393` | `action.execution_actor` | | `SessionWorkflow._resolve_llm()` | `session_workflow.py:383-391` | any actor_name | Additionally, `validate_namespaced_actor()` at `src/cleveragents/cli/commands/plan.py:119-137` conflates the two conventions by accepting `openai/gpt-4` as a valid namespace/name format in its docstring. ### Code flow ``` 1. Action YAML: strategy_actor: local/strategist (namespace/name) 2. Action.from_config() stores "local/strategist" 3. Plan created with plan.strategy_actor = "local/strategist" 4. agents plan execute <PLAN_ID> 5. StrategyActor._execute_with_llm() reads action.strategy_actor = "local/strategist" 6. _parse_actor_name("local/strategist") splits on "/" -> ("local", "strategist") 7. registry.create_llm(provider_type="local") -> ValueError: Unknown provider type: local ``` ## Suggested Fix The `_parse_actor_name()` functions need to distinguish between the two `/` conventions. Approaches: A) Check if the first segment is a known provider (in `ProviderType` enum) — if not, treat it as namespace/actor-name and resolve through the Actor Registry to get the actual provider/model B) Change the action YAML convention to use a different separator for namespace/name (e.g., `::`), breaking the ambiguity at the syntax level Option (A) is preferred as it is backward-compatible and follows the spec, which defines actor references in action YAML as namespaced names.
CoreRasurae added this to the v3.2.0 milestone 2026-05-21 17:09:55 +00:00
CoreRasurae added the
Type
Bug
Priority
Critical
State
Verified
 labels 2026-05-21 18:40:18 +00:00
HAL9000 was assigned by CoreRasurae 2026-05-21 18:40:24 +00:00
CoreRasurae removed the
State
Verified
 label 2026-05-22 14:47:08 +00:00
CoreRasurae added the
State
In Review
 label 2026-05-22 14:48:20 +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
Priority
Critical
State
In Review
Type
Bug
Milestone
No items
No Milestone v3.2.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 HAL9000
1 Participants
Notifications
Due Date
No due date set.
Depends on
#11255 fix(actors): distinguish namespace/name from provider/model in actor name parsing
cleveragents/cleveragents-core
Reference: cleveragents/cleveragents-core#11254
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?