Choosing the Right Execution Mode in Orquesta

Originally published at orquesta.live/blog/choosing-the-right-execution-mode-in-orquesta

Understanding Orquesta's Execution Modes

The Orquesta platform provides four distinct execution modes: Auto, SSH, Agent, and Batuta. Each mode is designed to cater to specific scenarios and team needs. It's essential to understand the strengths of each mode to leverage Orquesta efficiently. Let's break down each mode and discuss when it's best to use them.

Auto Mode: Letting AI Decide

Auto mode is ideal for teams that trust the AI to choose the most efficient execution path. When a prompt is submitted, the Auto mode evaluates the context and selects one of the other three modes — SSH, Agent, or Batuta — based on the situation.

Use Auto Mode When:

• You want to optimize execution without manual intervention.
• The team is familiar with Orquesta's intelligence and trusts its decision-making.
• You are dealing with complex prompts where the optimal execution path isn't immediately clear.

Auto mode simplifies the decision process, letting the system analyze and execute in the most effective way possible. It's particularly useful in environments where rapid, context-sensitive decision-making is crucial.

SSH Mode: Direct and Simple

SSH mode is perfect for executing straightforward, single-command tasks directly on remote servers. This mode bypasses the layers of decision-making or AI analysis, executing exactly what you specify.

Use SSH Mode When:

• You need to run simple commands quickly without additional logic or overhead.
• The task requires direct interaction with a remote system through SSH.
• Minimal setup and immediate results are priorities.

SSH mode is the go-to for scenarios where you need precision without complexity. It's straightforward and efficient for tasks like server restarts, log checks, or deploying a single script.

Agent Mode: Full Claude CLI Capabilities

Agent mode employs the Claude CLI to execute tasks, providing a rich set of capabilities. This mode is suitable for complex operations that require the full breadth of Claude's functionalities.

Use Agent Mode When:

• You need to leverage Claude's advanced scripting and automation features.
• The task involves multiple steps or requires a detailed plan and execution.
• You want to utilize the local AI agent for tasks where data privacy is crucial.

Agent mode is powerful for executing sophisticated workflows that benefit from Claude's robust toolset, offering an expansive command interface directly on your infrastructure.

Batuta Mode: Autonomous Execution

Batuta mode is Orquesta's autonomous powerhouse. It operates on a ReAct loop (Think > Act > Observe > Repeat), allowing the system to execute complex tasks autonomously.

Use Batuta Mode When:

• The task involves multiple steps and requires adaptive decision-making.
• You need an autonomous system to manage tasks with minimal oversight.
• There is a need for operations that can dynamically adjust to changing conditions.

Batuta mode is incredibly effective in scenarios where continuous decision-making and adaptation are required. It's like having an intelligent assistant that can handle evolving tasks without constant input.

Decision Framework for Teams

Choosing the right execution mode depends on task requirements, team familiarity with the platform, and the level of autonomy desired. Here's a quick decision framework:

• Use Auto for general tasks where you're uncertain which mode fits best or when you want the system to optimize execution.
• Use SSH for simple, direct command executions where precision and speed are essential.
• Use Agent when you need the power of Claude's CLI for complex, multi-step operations within your infrastructure.
• Use Batuta for tasks that benefit from autonomous loops and require adaptive, continuous execution.

By understanding these modes, teams can choose the best option for their needs, ensuring efficient and effective task execution. This clarity in decision-making can significantly enhance productivity and accuracy in managing development workflows.

Conclusion

Each execution mode in Orquesta is designed to cater to specific needs, balancing simplicity, power, and autonomy. By selecting the right mode, teams can streamline their workflows, maximize efficiency, and maintain control over their operations. Understanding when and how to use each mode is crucial for leveraging the full potential of Orquesta's capabilities.