feat: transform orchestrator into conversational AI coordinator#84
Open
sujayjayjay wants to merge 1 commit intomainfrom
Open
feat: transform orchestrator into conversational AI coordinator#84sujayjayjay wants to merge 1 commit intomainfrom
sujayjayjay wants to merge 1 commit intomainfrom
Conversation
Transform the orchestrator from documentation-focused to behavior-focused: - Issue creation from descriptions: "fix the config bug" creates issue + spawns agent - Agent monitoring: peek at tmux sessions and summarize progress - Dependency coordination: "spawn 8 after 5,6,7 merge" watches and acts - Proactive behaviors: report progress, suggest cleanup, coordinate automatically The orchestrator now acts as an intelligent assistant that handles all the ao spawn / gh issue create plumbing so users can describe work conversationally. Closes #78 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| gh pr list --repo ${project.repo} --state open | ||
| gh pr view <number> --repo ${project.repo} --json state,reviews,statusCheckRollup | ||
| gh pr merge <number> --repo ${project.repo} --squash | ||
| \`\`\``); |
There was a problem hiding this comment.
Command reference shows GitHub issue commands unconditionally
Medium Severity
The "Creating issues from descriptions" section correctly checks isGitHub and provides either gh issue commands or Linear-specific instructions. However, the "Command reference" section unconditionally includes gh issue create, gh issue list, and gh issue view commands regardless of the tracker type. For Linear projects, the orchestrator receives contradictory instructions — one section says "Use the Linear CLI" while the reference section lists gh issue commands.
Additional Locations (1)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Summary
The key insight from #78 is that the orchestrator already runs Claude Code with full CLI access - the issue was that the prompt didn't teach it to act autonomously. This PR gives the orchestrator clear behavioral instructions for:
tmux capture-paneCloses #78
Test plan
pnpm build)pnpm lint)pnpm test)ao startand verify the generatedCLAUDE.orchestrator.mdhas the new conversational format🤖 Generated with Claude Code