Skip to main content

​
Overview

The OpsHub Orchestrator is the central intelligence system of OpsHub, serving as the primary coordinator for all user interactions. It evaluates incoming requests, understands workspace context (active spreadsheets, dashboards, workflows, and reports), and intelligently routes work to one or more specialized agents. The Orchestrator maintains conversation continuity while ensuring each task reaches the most appropriate domain expert. Think of the Orchestrator as the intelligent receptionist of OpsHub—it listens to what you need, understands where you’re working, and connects you to the right specialist agent for optimal results.

​
Core Capabilities

Intelligent Routing

Analyzes user requests and workspace context to determine which specialized agent should handle the task. Uses request semantics and current workspace state to make routing decisions.

Workspace Awareness

Maintains real-time understanding of your current context—which spreadsheet is open, which dashboard you’re viewing, which workflow you’re executing, and what you’re working on.

Context Preservation

Remembers conversation history, user preferences, and past decisions throughout your session. Enables seamless multi-turn conversations with consistent context across agent handoffs.

Request Decomposition

Breaks complex multi-step requests into subtasks, delegating to multiple specialized agents in parallel or sequence as needed, then synthesizing results into coherent responses.

Delegation Tracking

Maintains full audit trail of which agents were involved in fulfilling your request, why each was delegated to, and what each contributed to the final result.

Validation Coordination

Orchestrates validation workflows across multiple agents, collecting validation status and ensuring compliance checks complete before proceeding to next steps.

​
How the Orchestrator Works

  • Request Flow
  • State Management
  • Workspace Context
1. Request Reception
  • You submit a natural language request in the OpsHub interface
  • Workspace context is automatically captured (active sheet, dashboard, etc.)
2. Request Analysis
  • Orchestrator analyzes your request semantics
  • Evaluates workspace context and recent conversation history
  • Determines if request needs single or multi-agent coordination
3. Agent Selection
  • Routes to most appropriate specialized agent(s):
    • Dashboard Architect for visualization requests
    • Workbook Engineer for spreadsheet automation
    • Fund Accountant Assistant for NAV operations
    • Compliance Sentinel for regulatory checks
    • And 6 other domain specialists
4. Task Execution
  • Selected agent(s) execute their specialized tools
  • Orchestrator monitors progress and collects results
  • Handles agent-to-agent delegation if needed
5. Result Synthesis
  • Combines outputs from all agents involved
  • Formats response in context of your workspace
  • Provides explanation of actions taken and reasoning

​
Available Specialized Agents

The Orchestrator coordinates with these 9 specialized agents:
AgentFocusExample Requests
Dashboard ArchitectMetrics & visualization”Create a NAV variance dashboard”
Workbook EngineerSpreadsheet automation”Add formula to calculate fund positions”
Investment Analytics StrategistPerformance analysis”Show attribution for Q3 underperformance”
Workflow DirectorProcess automation”Automate NAV certification process”
Integration SpecialistData connectivity”Sync custodian positions”
Data Quality AnalystException handling”Find data quality issues in holdings”
Fund Accountant AssistantNAV operations”Investigate this 4bp NAV break”
Portfolio Manager CopilotPortfolio insights”Which funds had highest market exposure?”
Compliance SentinelRegulatory oversight”Generate RG94 compliance report”

​
Use Cases & Examples

​
Use Case 1: Daily NAV Validation

User Request: “I see a 3.5bp break in the growth fund. What’s causing it?” Orchestrator Actions:
  1. Identifies you’re working in the NAV validation spreadsheet
  2. Routes to Fund Accountant Assistant (NAV expert)
  3. Coordinates with Data Quality Analyst for holdings comparison
  4. May invoke Integration Specialist if custodian data needs refresh
Result: “The break is caused by a $2.3M dividend accrual recognized by administrator but not yet by custodian. Status: expected, resolves EOD. I’ve flagged this as normal variance.”

​
Use Case 2: Month-End Compliance Report

User Request: “I need the RG94 compliance report for investor presentation next week.” Orchestrator Actions:
  1. Routes to Compliance Sentinel (regulatory expert)
  2. Coordinates with Dashboard Architect for visual summaries
  3. Delegates to Report Generation system for formatting
  4. Orchestrates approval workflow integration
Result: Generates executive summary, breach status matrix, fund performance vs. limits, and audit evidence—ready for presentation with full compliance documentation.

​
Use Case 3: Performance Analysis Across Fund-of-Funds

User Request: “Why did our tech-heavy funds underperform the benchmark last quarter?” Orchestrator Actions:
  1. Routes to Investment Analytics Strategist (analysis expert)
  2. Coordinates with Portfolio Manager Copilot for positioning data
  3. Engages Data Quality Analyst to validate underlying fund data
  4. Synthesizes attribution across your fund-of-funds structure
Result: “Tech holdings underperformed by 210bps due to: (1) 3x overweight to software vs. benchmark (+150bps drag), (2) individual stock selection (-60bps). Detailed attribution and fund-level breakdown attached.”

​
Code Examples

  • Natural Language Request
  • API Call
  • Multi-Agent Coordination
// User: Fund Accountant working with NAV validation spreadsheet

"I see a 2bp break in Fund A. The custodian sent updated
positions this morning. Can you reconcile with our books
and tell me if this is normal?"

// Orchestrator interprets:
// - You're in the NAV validation context
// - Seeking variance root cause
// - Requesting data reconciliation
// - Expecting expert guidance on normality

// Routes to: Fund Accountant Assistant
// Coordinates with: Integration Specialist (if custodian refresh needed),
//                   Data Quality Analyst (reconciliation validation)

​
Configuration

The Orchestrator works automatically without configuration, but you can customize behavior via these settings:
Workspace Awareness Mode - Set how aggressively the Orchestrator uses workspace context to inform routing decisions (Conservative, Balanced, Aggressive). Default: Balanced.
Delegation Chain Visibility - Show/hide the agents involved in fulfilling your request in the response. Default: Show summary.
Approval Gates - Require user confirmation before delegating to high-impact agents (Compliance Sentinel, Workflow Director). Default: Enabled.
Context Retention - How many previous messages the Orchestrator remembers (impacts token usage and accuracy). Default: Last 20 messages.

​
Best Practices

1. Be Specific About Context Instead of “analyze this,” say “analyze the growth fund’s holdings vs. benchmark” so the Orchestrator can route to the most precise specialist. Mention your current workspace when context isn’t obvious. 2. Leverage Multi-Turn Conversations The Orchestrator maintains conversation context across messages. You can ask follow-up questions, request modifications, and the agents will understand the broader discussion. No need to repeat context. 3. Review Agent Delegations for Complex Tasks When you ask for something that involves multiple agents (like compliance reporting), glance at which agents were delegated to. This helps you understand the thinking and builds confidence in the result. 4. Use Draft Approval for High-Impact Changes When the Orchestrator proposes significant changes (new dashboard structures, workflow modifications), review the draft first. This gives you control and creates an audit trail. 5. Provide Feedback on Results If an agent misunderstands your request, provide corrective feedback. The Orchestrator learns from this and improves future routing and agent behavior for similar requests.

Specialized Agents

Learn about the 9 specialized agents that the Orchestrator coordinates

Tools Reference

Explore the 62+ tools available across all agents

API Integration

Integrate OpsHub Agent Backend with your systems

Workspace Context

Deep dive into how workspace context drives intelligent routing

AG-UI Protocol

Understand the state synchronization protocol powering real-time coordination

Multi-Agent Workflows

See examples of complex multi-agent coordination in action

​
Troubleshooting

“The Orchestrator routed my request to the wrong agent” The Orchestrator uses request semantics and workspace context to determine routing. To improve accuracy:
  • Be more specific in your request (mention which fund, which metric, etc.)
  • Ensure your workspace context is correct (you’re viewing the right spreadsheet/dashboard)
  • Provide feedback on the misdirection so the system learns from it
“I expected a different result from what the agent provided” Complex requests sometimes benefit from different agent perspectives. You can ask the Orchestrator to route to a different agent: “Can the Portfolio Manager Copilot also analyze this?” The Orchestrator will coordinate multiple perspectives. “The response took too long” Multi-agent coordination adds latency vs. single-agent responses. Simple requests typically complete in 2-5 seconds. Complex requests involving 3+ agents may take 10-15 seconds. This includes database queries and tool execution time. “I want to prevent certain agents from being delegated to my request” You can specify preferred agents in your request: “Without involving the Compliance Sentinel, what’s driving this fund underperformance?” The Orchestrator will exclude specified agents from its delegation chain. “Tool execution failed but Orchestrator didn’t retry” The Orchestrator implements smart retry logic for transient failures (network timeouts, temporary database unavailability). If a tool fails due to invalid parameters or data issues, it won’t retry. Check the tool error message for guidance on what went wrong.
Last Updated: October 2025 Version: 1.0 Status: Production