Delegate to a Second Model with Advisor and Sidekick

import os

from orq_ai_sdk import Orq

INSTRUCTIONS = """Triage incoming production alerts for a SaaS platform team.

Work through an alert in three stages.

Stage 1 - Classify (do this yourself, do not delegate).
From the alert and any log excerpt, state:
- Severity: SEV1, SEV2, or SEV3
- Affected service
- Blast radius: which users or regions are affected, and roughly how many
Keep this to a few lines. This is routine work and must stay on the primary model.

Stage 2 - Rollback decision (use the advisor).
Deciding whether to roll back a deployment is high-stakes and depends on everything established in stage 1. Always ask the advisor before making this call. Put the specific question to the advisor, for example whether the evidence so far justifies an immediate rollback or whether to hold and keep monitoring. Weigh the advice, then state the decision and the reasoning in the final answer. The decision is the primary model's to make, not the advisor's.

Stage 3 - Status page update (use the sidekick).
Once the decision is made, delegate the customer-facing status page update to the sidekick. Send it a task describing what happened and what the team is doing, plus the severity and affected service as context. Do not write the status update. Return the sidekick's result verbatim under a 'Status page update' heading.

Rules:
- Never invent metrics, error rates, or timestamps that are not in the alert.
- If the alert is too thin to classify, say what is missing rather than guessing.
- Keep the final answer under 250 words, excluding the status page update."""

with Orq(api_key=os.getenv("ORQ_API_KEY", "")) as orq:
    agent = orq.agents.create(
        key="incident-triage-delegation",
        display_name="Incident Triage (Advisor + Sidekick)",
        role="Incident triage assistant for a SaaS platform team.",
        description="Classifies a production alert, consults an advisor on the rollback decision, and delegates the status update to a sidekick.",
        path="Default",
        model="anthropic/claude-haiku-4-5",
        instructions=INSTRUCTIONS,
        settings={
            "max_iterations": 10,
            "tool_approval_required": "none",
            "tools": [
                {
                    "type": "advisor",
                    "configuration": {
                        "model": "anthropic/claude-opus-4-8",
                        "max_uses": 2,
                        "max_transcript_tokens": 4000,
                        "max_tokens": 600,
                    },
                },
                {
                    "type": "sidekick",
                    "configuration": {
                        "model": "openai/gpt-4o-mini",
                        "max_uses": 2,
                        "max_tokens": 400,
                        "system_prompt": "Write customer-facing status page updates for a SaaS platform. Plain and factual. No blame, no speculation about root cause beyond what the task states, no internal service names, no engineer names, no internal metrics.",
                        "output_format": "Three short paragraphs, each preceded by a plain text label on its own line: Impact, Current status, Next update. No markdown headings.",
                    },
                },
            ],
        },
    )

print(agent.key)

import { Orq } from "@orq-ai/node";

const orq = new Orq({ apiKey: process.env.ORQ_API_KEY });

const INSTRUCTIONS = `Triage incoming production alerts for a SaaS platform team.

Work through an alert in three stages.

Stage 1 - Classify (do this yourself, do not delegate).
From the alert and any log excerpt, state:
- Severity: SEV1, SEV2, or SEV3
- Affected service
- Blast radius: which users or regions are affected, and roughly how many
Keep this to a few lines. This is routine work and must stay on the primary model.

Stage 2 - Rollback decision (use the advisor).
Deciding whether to roll back a deployment is high-stakes and depends on everything established in stage 1. Always ask the advisor before making this call. Put the specific question to the advisor, for example whether the evidence so far justifies an immediate rollback or whether to hold and keep monitoring. Weigh the advice, then state the decision and the reasoning in the final answer. The decision is the primary model's to make, not the advisor's.

Stage 3 - Status page update (use the sidekick).
Once the decision is made, delegate the customer-facing status page update to the sidekick. Send it a task describing what happened and what the team is doing, plus the severity and affected service as context. Do not write the status update. Return the sidekick's result verbatim under a 'Status page update' heading.

Rules:
- Never invent metrics, error rates, or timestamps that are not in the alert.
- If the alert is too thin to classify, say what is missing rather than guessing.
- Keep the final answer under 250 words, excluding the status page update.`;

const agent = await orq.agents.create({
  key: "incident-triage-delegation",
  displayName: "Incident Triage (Advisor + Sidekick)",
  role: "Incident triage assistant for a SaaS platform team.",
  description: "Classifies a production alert, consults an advisor on the rollback decision, and delegates the status update to a sidekick.",
  path: "Default",
  model: "anthropic/claude-haiku-4-5",
  instructions: INSTRUCTIONS,
  settings: {
    maxIterations: 10,
    toolApprovalRequired: "none",
    tools: [
      {
        type: "advisor",
        configuration: {
          model: "anthropic/claude-opus-4-8",
          max_uses: 2,
          max_transcript_tokens: 4000,
          max_tokens: 600,
        },
      },
      {
        type: "sidekick",
        configuration: {
          model: "openai/gpt-4o-mini",
          max_uses: 2,
          max_tokens: 400,
          system_prompt: "Write customer-facing status page updates for a SaaS platform. Plain and factual. No blame, no speculation about root cause beyond what the task states, no internal service names, no engineer names, no internal metrics.",
          output_format: "Three short paragraphs, each preceded by a plain text label on its own line: Impact, Current status, Next update. No markdown headings.",
        },
      },
    ],
  },
});

console.log(agent.key);

curl -X POST "https://my.orq.ai/v2/agents" \
  -H "Authorization: Bearer $ORQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "key": "incident-triage-delegation",
    "display_name": "Incident Triage (Advisor + Sidekick)",
    "role": "Incident triage assistant for a SaaS platform team.",
    "description": "Classifies a production alert, consults an advisor on the rollback decision, and delegates the status update to a sidekick.",
    "path": "Default",
    "model": "anthropic/claude-haiku-4-5",
    "instructions": "Triage incoming production alerts for a SaaS platform team.\n\nWork through an alert in three stages.\n\nStage 1 - Classify (do this yourself, do not delegate).\nFrom the alert and any log excerpt, state:\n- Severity: SEV1, SEV2, or SEV3\n- Affected service\n- Blast radius: which users or regions are affected, and roughly how many\nKeep this to a few lines. This is routine work and must stay on the primary model.\n\nStage 2 - Rollback decision (use the advisor).\nDeciding whether to roll back a deployment is high-stakes and depends on everything established in stage 1. Always ask the advisor before making this call. Put the specific question to the advisor, for example whether the evidence so far justifies an immediate rollback or whether to hold and keep monitoring. Weigh the advice, then state the decision and the reasoning in the final answer. The decision is the primary model'\''s to make, not the advisor'\''s.\n\nStage 3 - Status page update (use the sidekick).\nOnce the decision is made, delegate the customer-facing status page update to the sidekick. Send it a task describing what happened and what the team is doing, plus the severity and affected service as context. Do not write the status update. Return the sidekick'\''s result verbatim under a '\''Status page update'\'' heading.\n\nRules:\n- Never invent metrics, error rates, or timestamps that are not in the alert.\n- If the alert is too thin to classify, say what is missing rather than guessing.\n- Keep the final answer under 250 words, excluding the status page update.",
    "settings": {
      "max_iterations": 10,
      "tool_approval_required": "none",
      "tools": [
        {
          "type": "advisor",
          "configuration": {
            "model": "anthropic/claude-opus-4-8",
            "max_uses": 2,
            "max_transcript_tokens": 4000,
            "max_tokens": 600
          }
        },
        {
          "type": "sidekick",
          "configuration": {
            "model": "openai/gpt-4o-mini",
            "max_uses": 2,
            "max_tokens": 400,
            "system_prompt": "Write customer-facing status page updates for a SaaS platform. Plain and factual. No blame, no speculation about root cause beyond what the task states, no internal service names, no engineer names, no internal metrics.",
            "output_format": "Three short paragraphs, each preceded by a plain text label on its own line: Impact, Current status, Next update. No markdown headings."
          }
        }
      ]
    }
  }'

orq agents create \
  --key "incident-triage-delegation" \
  --display-name "Incident Triage (Advisor + Sidekick)" \
  --role "Incident triage assistant for a SaaS platform team." \
  --description "Classifies a production alert, consults an advisor on the rollback decision, and delegates the status update to a sidekick." \
  --instructions "$(cat instructions.txt)" \
  --path "Default" \
  --model "anthropic/claude-haiku-4-5" \
  --settings '{
    "max_iterations": 10,
    "tool_approval_required": "none",
    "tools": [
      {
        "type": "advisor",
        "configuration": {
          "model": "anthropic/claude-opus-4-8",
          "max_uses": 2,
          "max_transcript_tokens": 4000,
          "max_tokens": 600
        }
      },
      {
        "type": "sidekick",
        "configuration": {
          "model": "openai/gpt-4o-mini",
          "max_uses": 2,
          "max_tokens": 400,
          "system_prompt": "Write customer-facing status page updates for a SaaS platform. Plain and factual. No blame, no speculation about root cause beyond what the task states, no internal service names, no engineer names, no internal metrics.",
          "output_format": "Three short paragraphs, each preceded by a plain text label on its own line: Impact, Current status, Next update. No markdown headings."
        }
      }
    ]
  }'