Originally published at orquesta.live/blog/mastering-orquesta-choosing-right-execution-mode
Orquesta has revolutionized the way teams interact with AI-driven coding and deployment processes by offering a flexible and secure platform. A core part of this flexibility comes from its four distinct execution modes: Auto, SSH, Agent, and Batuta. Each mode serves a unique purpose, optimizing various stages of the development and operations lifecycle. Understanding which mode to use when can significantly streamline your workflows.
Auto Mode: Let the AI Decide
Auto mode is the go-to option when you're looking to simplify decision-making. The AI intelligently selects the most appropriate execution method based on the task at hand, saving you the need to manually choose between modes. This is particularly useful in scenarios where:
- Quick Turnaround: You need a rapid solution without deliberating over the best execution path.
- Uncertain Requirements: You're not entirely sure which execution mode best suits your needs.
The Auto mode is powered by a sophisticated decision engine that evaluates parameters such as complexity, urgency, and context to automate the mode selection process.
# Example of invoking Auto mode in Orquesta CLI
orquesta execute --mode auto --task deploy_feature
SSH Mode: Direct and Simple Commands
SSH mode is ideal for executing straightforward, singular commands on remote servers. It’s particularly effective when:
- Quick Fixes: You need to make a one-off change or troubleshoot an issue directly.
- Command Simplicity: The task involves a simple command that doesn’t require the overhead of a full AI agent.
Using SSH mode ensures minimal overhead and quick execution, leveraging Orquesta’s secure infrastructure to maintain your system’s integrity.
# Example of using SSH mode
orquesta execute --mode ssh --command "sudo systemctl restart nginx"
Agent Mode: Harness the Power of Claude CLI
Agent mode leverages the full capabilities of the Claude CLI, making it an excellent choice for comprehensive coding tasks. This mode is tailored for:
- Complex Operations: When your task involves multiple steps that require AI guidance.
- Detailed Code Execution: Tasks that benefit from the Claude CLI’s robust toolset and capabilities.
Agent mode provides a balance between automated intelligence and controlled execution, enabling you to undertake sophisticated projects with precision.
# YAML configuration for deploying with Agent mode
execute:
mode: agent
script: deploy_script.claude
Batuta Mode: Autonomous Execution
Batuta mode represents Orquesta’s most autonomous execution path. It engages the system in a Think > Act > Observe > Repeat loop, making it perfect for:
- Complex Automation: Scenarios requiring continuous adaptation and learning.
- Hands-off Management: When you need the AI to manage the process end-to-end without intervention.
Batuta mode is powered by our ReAct framework, autonomously iterating over tasks to achieve the best possible outcome.
{
"execute": {
"mode": "batuta",
"script": "optimize_infrastructure.batuta"
}
}
Decision Framework: Choosing the Right Mode
Selecting the right execution mode boils down to understanding the task requirements and operational context:
- Use Auto when you want the system to optimize the execution path for general tasks.
- Opt for SSH when dealing with straightforward commands that require minimal overhead.
- Select Agent when engaging in complex coding tasks requiring the Claude CLI’s capabilities.
- Go with Batuta for fully autonomous, adaptive processes that benefit from iterative learning.
By aligning your task with the appropriate execution mode, you can enhance efficiency and maintain control over your development and deployment processes. Orquesta’s flexibility is designed to fit the unique needs of any team, allowing for seamless integration and execution.
Ultimately, the power of Orquesta’s execution modes lies in their ability to adapt to your workflow, ensuring that every project runs smoothly and efficiently.
Top comments (0)