Overview
Orbits are the top-level orchestration constructs in OrbitAI that bring together agents, tasks, and processes into cohesive, executable workflows. An orbit manages the complete lifecycle of multi-agent execution, from initialization through task distribution to result aggregation.Orchestration
Coordinates multiple agents and tasks
Lifecycle Management
Manages execution from start to finish
LLM Integration
Automatic LLM provider setup
Memory Systems
Shared and agent-specific memory
Context Flow
Manages data flow between tasks
Telemetry
Comprehensive metrics and monitoring
What is an Orbit?
An Orbit is a complete workflow system that:- Manages agents: Configures and coordinates AI agents
- Executes tasks: Runs tasks according to process type
- Handles state: Tracks execution progress and results
- Provides infrastructure: LLM providers, memory, tools, knowledge bases
- Monitors performance: Collects metrics and usage data
- Ensures reliability: Error handling and recovery mechanisms
Think of an Orbit as a “project” or “workflow instance” that contains everything needed to execute a multi-agent system.
Key Characteristics
Self-Contained
Self-Contained
Orbits encapsulate all necessary components—agents, tasks, LLM providers, memory, and tools—making them portable and reusable.
Process-Driven
Process-Driven
Execution follows one of three process types (Sequential, Hierarchical, Flow-Based), providing predictable orchestration patterns.
Context-Aware
Context-Aware
Maintains execution context that flows through tasks, enabling agents to build upon previous work and share information.
Observable
Observable
Provides comprehensive visibility into execution through verbose logging, metrics, and telemetry integration.
Orbit Lifecycle
Understanding the orbit lifecycle helps you manage execution and handle edge cases effectively.Lifecycle States
- Initialization
- Ready
- Running
- Completing
- Completed/Failed
Phase: Orbit construction and setupActivities:Common Errors:
- Validate required parameters
- Create internal components
- Setup LLM manager
- Initialize memory systems
- Register tools with ToolsHandler
- Prepare knowledge bases
- Validate agent configurations
- Validate task configurations
- Missing required parameters
- Invalid agent configurations
- LLM provider setup failures
- Tool registration issues
Parameters and Configuration
Core Parameters
- Required
- Process & Execution
- Memory & Knowledge
- Monitoring & Output
- Additional Config
These three parameters are the minimum required to create a functioning orbit.
Creating and Configuring Orbits
Basic Creation
1
Define Agents
Create agents with appropriate roles and capabilities:
2
Define Tasks
Create tasks with clear descriptions and expected outputs:
3
Create Orbit
Bring agents and tasks together:
4
Execute
Start the orbit and get results:
Advanced Configuration
- Custom LLM Setup
- Memory Configuration
- Knowledge Sources
- Tool Registration
Configure specific LLM providers:
Execution Process
Execution Flow
- Sequential
- Hierarchical
- Flow-Based
- Strict linear execution
- Each task waits for previous
- Context builds sequentially
- Predictable timing
Execution Context
The execution context flows through tasks:Inputs and Interpolation
OrbitInput
Provide dynamic inputs to orbits:- Basic Usage
- Typed Inputs
- Complex Inputs
- Default Values
Variable Interpolation
Task Output References
Task Output References
Reference previous task outputs:Variable Format:
{task_0_output}- First task{task_1_output}- Second task{task_N_output}- Nth task
Orbit Inputs
Orbit Inputs
Reference orbit-level inputs:
Conditional Interpolation
Conditional Interpolation
Use conditional values:
Conditional interpolation is processed before task execution.
Outputs
OrbitOutput Structure
Accessing Results
- Basic Access
- Structured Outputs
- Error Results
- Exporting Results
Monitoring and Telemetry
Real-Time Monitoring
- Execution Status
- Agent Metrics
- Task Progress
- Custom Telemetry
Metrics Collection
Usage Metrics
Usage Metrics
Performance Metrics
Performance Metrics
Tool Usage Metrics
Tool Usage Metrics
Error Handling
Error Types
Configuration Errors
When: During orbit creationCommon Causes:
- Missing required parameters
- Invalid agent configurations
- Empty agents or tasks arrays
Execution Errors
When: During orbit.start()Common Causes:
- Task execution failures
- Agent errors
- Tool failures
- Timeout exceeded
LLM Errors
When: LLM provider issuesCommon Causes:
- Rate limits
- API key issues
- Provider unavailability
- Token limits exceeded
Resource Errors
When: Resource constraintsCommon Causes:
- Memory constraints
- Timeout limits
- Disk space issues
Error Recovery Strategies
- Retry Logic
- Fallback Providers
- Partial Results
- Graceful Degradation
Best Practices
Orbit Design
Appropriate Scope
Do: Create focused orbits for specific workflowsDon’t: Create monolithic orbits
Agent Specialization
Do: Assign specialized agents to relevant tasksDon’t: Use generic agents for everything
Memory Management
Do: Enable memory only when needed
Error Boundaries
Do: Implement proper error handlingDon’t: Ignore errors
Performance Optimization
1
Choose Appropriate Process
2
Optimize Task Granularity
3
Configure Concurrency
4
Monitor and Tune
Troubleshooting
Orbit Fails to Initialize
Orbit Fails to Initialize
Symptoms: Errors during
Orbit.create()Common Causes:- Missing required parameters
- Invalid agent/task configurations
- LLM provider setup failure
Tasks Not Executing
Tasks Not Executing
Symptoms: Orbit starts but tasks don’t runCommon Causes:
- Agent assignment issues
- Missing tools
- LLM provider not configured
Context Variables Not Resolving
Context Variables Not Resolving
Symptoms:
{variable} appears literally in outputsCommon Causes:- Missing context declaration
- Wrong variable names
- Inputs not provided
High Memory Usage
High Memory Usage
Symptoms: Memory consumption growing excessivelyCommon Causes:
- Memory enabled unnecessarily
- Large outputs accumulating
- Knowledge bases loaded but not needed
Slow Execution
Slow Execution
Symptoms: Orbit takes much longer than expectedCommon Causes:
- Sequential execution when parallel possible
- Large context windows
- Inefficient tool usage
- No concurrency limits set
Inconsistent Results
Inconsistent Results
Symptoms: Different outputs for same inputsCommon Causes:
- High temperature settings
- Non-deterministic tools
- Memory state differences
- Random LLM sampling
Next Steps
Agents
Configure agents for orbits
Tasks
Define tasks for execution
Processes
Choose the right process type
Examples
See complete orbit examples
For additional support, consult the GitHub Discussions or check the Issue Tracker.