Summary
DevClaw should support project-level orchestrator prompt files the same way it supports other prompt types, with winner-takes-all resolution and correct refresh behavior when a fresh orchestrator session is bootstrapped again on the same topic-bound session key.
Problem
Worker prompts already support project-specific prompt files with clear precedence. Orchestrator prompts were lagging behind that model.
In the failing behavior:
- project-level orchestrator prompt resolution for real topic-bound orchestrator sessions was incomplete
- fallback behavior could be wrong for chat/topic-shaped session keys
- fresh bootstrap on the same logical topic session could keep older orchestrator prompt content instead of replacing it with the newly resolved winner
That made orchestrator prompt behavior inconsistent with other prompt types and made live validation misleading.
Expected behavior
- support project-level orchestrator prompts for real chat/topic-backed orchestrator sessions
- keep winner-takes-all precedence between project, workspace/default, and package-default orchestrator prompt sources
- replace stale synthetic
orchestrator.md content when bootstrap runs again for the same logical topic session
Notes
This is not only a /new issue. The broader fix is to make orchestrator prompt loading behave like the rest of the prompt system while also replacing stale bootstrap material on repeated fresh session bootstrap.
Summary
DevClaw should support project-level orchestrator prompt files the same way it supports other prompt types, with winner-takes-all resolution and correct refresh behavior when a fresh orchestrator session is bootstrapped again on the same topic-bound session key.
Problem
Worker prompts already support project-specific prompt files with clear precedence. Orchestrator prompts were lagging behind that model.
In the failing behavior:
That made orchestrator prompt behavior inconsistent with other prompt types and made live validation misleading.
Expected behavior
orchestrator.mdcontent when bootstrap runs again for the same logical topic sessionNotes
This is not only a
/newissue. The broader fix is to make orchestrator prompt loading behave like the rest of the prompt system while also replacing stale bootstrap material on repeated fresh session bootstrap.