LearnNewsExamplesServices
Frontmatter
id11081
titleRename Orchestrator.mjs to AgentOrchestrator.mjs
stateClosed
labels
airefactoringarchitecture
assigneesneo-gemini-3-1-pro
createdAtMay 10, 2026, 2:03 AM
updatedAtMay 10, 2026, 4:26 AM
githubUrlhttps://github.com/neomjs/neo/issues/11081
authorneo-gemini-3-1-pro
commentsCount0
parentIssue11077
subIssues[]
subIssuesCompleted0
subIssuesTotal0
blockedBy[]
blocking[]
closedAtMay 10, 2026, 4:26 AM

Rename Orchestrator.mjs to AgentOrchestrator.mjs

Closedairefactoringarchitecture
neo-gemini-3-1-pro
neo-gemini-3-1-pro commented on May 10, 2026, 2:03 AM

Context

The ai/agent/Orchestrator.mjs is colliding conceptually and nominally with the daemon orchestrator (ai/daemons/Orchestrator.mjs).

The Problem

Namespace collision creates confusion between the agent-side coordination layer and the daemon-side maintenance supervisor, especially as we elevate the daemon orchestrator in Epic #11077.

The Architectural Reality

The agent-side orchestrator manages agent lifecycle and routing, while the daemon-side manages background tasks. They exist in different substrates (ai/agent/ vs ai/daemons/).

The Fix

Rename ai/agent/Orchestrator.mjs to ai/agent/AgentOrchestrator.mjs. Update all references, imports, and tests accordingly.

Acceptance Criteria

  • ai/agent/Orchestrator.mjs renamed to AgentOrchestrator.mjs.
  • All internal references and imports updated.
  • Unit tests updated to reflect the new class name.

Out of Scope

  • Refactoring the internal logic of AgentOrchestrator.

Related

tobiu closed this issue on May 10, 2026, 4:26 AM
tobiu referenced in commit e0d2c2e - "refactor(agent): rename Orchestrator to AgentOrchestrator (#11081) (#11088) on May 10, 2026, 4:26 AM