sub-agents.directory
Meta Orchestration

Codebase Orchestrator vs It Ops Orchestrator

Compare these two Claude Code sub-agents to find the best fit for your project. Both are in the Meta Orchestration category.

Comparison Overview

Codebase Orchestrator

Use this agent when you need repository-wide refactor governance with explicit approval loops, weighted risk prioritization, diff previews, and deterministic fallback strategies.

View Full Prompt

It Ops Orchestrator

IT operations meta-orchestrator specializing in routing tasks across PowerShell, .NET, infrastructure, Azure, and M365 subagents. Prefers PowerShell-based automation as the default implementation language. Use when orchestrating IT operations or infrastructure workflows.

View Full Prompt

Tool Comparison

Shared Tools (6)

Read
Write
Edit
Bash
Glob
Grep

Only in Codebase Orchestrator (7)

WebFetch
airis-mcp-gateway
context-manager
error-coordinator
pied-piper
subagent-catalog:search
subagent-catalog:fetch

Only in It Ops Orchestrator (0)

No unique tools

When to Use Each

Use Codebase Orchestrator when:

  • • You need expertise in Read, Write, Edit
  • • Your project aligns with Meta Orchestration
  • • You prefer more comprehensive tool coverage

Use It Ops Orchestrator when:

  • • You need expertise in Read, Write, Edit
  • • Your project aligns with Meta Orchestration
  • • You prefer focused tool coverage

Frequently Asked Questions

What's the difference between Codebase Orchestrator and It Ops Orchestrator?

Codebase Orchestrator and It Ops Orchestrator are both Claude Code sub-agents, but they're optimized for different use cases. Codebase Orchestrator focuses on Use this agent when you need repository-wide refactor governance with explicit approval loops, weighted risk prioritization, diff previews, and deterministic fallback strategies., while It Ops Orchestrator is better suited for IT operations meta-orchestrator specializing in routing tasks across PowerShell, .NET, infrastructure, Azure, and M365 subagents. Prefers PowerShell-based automation as the default implementation language. Use when orchestrating IT operations or infrastructure workflows..

Which sub-agent should I use: Codebase Orchestrator or It Ops Orchestrator?

The best choice depends on your specific needs. Use Codebase Orchestrator when you need Use this agent when you need repository-wide refactor governance with explicit approval loops, weighted risk prioritization, diff previews, and deterministic fallback strategies.. Choose It Ops Orchestrator when your work requires IT operations meta-orchestrator specializing in routing tasks across PowerShell, .NET, infrastructure, Azure, and M365 subagents. Prefers PowerShell-based automation as the default implementation language. Use when orchestrating IT operations or infrastructure workflows..

Can I use both Codebase Orchestrator and It Ops Orchestrator together?

Yes! You can combine multiple sub-agents by including their prompts in your CLAUDE.md file. Many developers use different agents for different parts of their workflow or project.