Skip to content

Commit 0930130

Browse files
rldyourmndclaude
andcommitted
refactor(flow): drop orchestrator env switch from role resolution
Orchestrator activation is declarative (the user states the role during ry-init), so auto role resolution no longer reads RLDYOUR_ORCHESTRATOR; only workers stay machine-identified through RLDYOUR_WORKER and RLDYOUR_WORKER_ID. Explicit RLDYOUR_AGENT_ROLE and project policy keep working unchanged. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1 parent 8cf5895 commit 0930130

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

plugins/rldyour-flow/scripts/flow_post_task_state.py

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -244,9 +244,9 @@ def _runtime_execution(effective_policy: dict[str, Any]) -> dict[str, Any]:
244244
if role not in {"auto", "standalone", "orchestrator", "worker"}:
245245
role = "auto"
246246
if role == "auto":
247-
if mode == "orchestrator" and os.environ.get("RLDYOUR_ORCHESTRATOR") == "1":
248-
role = "orchestrator"
249-
elif mode == "orchestrator" and (
247+
# Orchestrator activation is declarative (the user states the role in
248+
# /ry-init); only workers stay machine-identified through env.
249+
if mode == "orchestrator" and (
250250
os.environ.get("RLDYOUR_WORKER") == "1" or os.environ.get("RLDYOUR_WORKER_ID")
251251
):
252252
role = "worker"

0 commit comments

Comments
 (0)