{
  "_meta": {
    "publication": "Agent Techniques Weekly",
    "schemaVersion": "2026.05.02",
    "generatedAt": "2026-09-08T22:45:09.011Z",
    "canonicalUrl": "https://brianletort.ai/industry/agents/2026-W26",
    "markdownUrl": "https://brianletort.ai/industry/agents/2026-W26/llm.md",
    "sourceFile": "src/data/industry/agents/2026-W26.ts"
  },
  "issue": {
    "slug": "2026-W26",
    "isoYear": 2026,
    "isoWeek": 26,
    "issueNumber": 10,
    "publishedAt": "2026-06-27",
    "cadence": "weekly",
    "periodLabel": "Week 26 of 2026",
    "bigRead": {
      "headline": "Background agents crossed from novelty to operations: the hard part is the control loop.",
      "body": "W26's agent-technique signal is Scheduled Agent Operations. Codex Automations, Cursor Automations, and ServiceNow Build Agent all point to the same shift: agents are no longer only interactive copilots waiting in a chat pane. They can wake up on a cron, a PR event, a Slack message, a webhook, or a platform build request; enter a sandbox or governed runtime; use connectors and skills; produce a diff, app, finding, or triage item; and either archive, escalate, or ask for approval. The transferable technique is to design the operating loop before delegating work. Every scheduled agent needs a trigger contract, source-of-truth context, least-privilege tool access, a deterministic verifier, a budget/stop rule, and an escalation lane. Boards should ask whether background agents are inventoried like non-human workers; architects should standardize worktrees, Triage queues, and run logs; operators should start with bounded maintenance jobs before unattended production changes."
    },
    "technique": {
      "name": "Scheduled Agent Operations",
      "mode": "automate",
      "summary": "Run agents as bounded recurring or event-triggered jobs with explicit context, sandboxing, verification, budgets, and escalation.",
      "whyItMatters": "Once agents run without a human prompt, the unit of management changes from conversation quality to operational reliability. The control loop determines whether automation saves time or creates hidden risk and spend.",
      "anatomy": [
        {
          "label": "Trigger",
          "detail": "Define the exact schedule or event: cron, PR opened, CI completed, Slack message, webhook, incident, or manual dispatch."
        },
        {
          "label": "Context",
          "detail": "Attach the repo, branch, thread, docs, issue, system-of-record context, and durable rules the agent needs to operate without guessing."
        },
        {
          "label": "Tools",
          "detail": "Grant only the MCP tools, connectors, shell commands, and write permissions required for that workflow."
        },
        {
          "label": "Verifier",
          "detail": "Require tests, schema checks, source trails, screenshots, policy checks, or human approval before output becomes trusted."
        },
        {
          "label": "Escalation",
          "detail": "Route findings to Triage, PR comments, Slack, a draft PR, or an approval queue; archive only when the run finds nothing material."
        }
      ],
      "examples": [
        "Weekly dependency and CI triage",
        "Scheduled content freshness checks",
        "PR review and autofix attempts",
        "Governed ServiceNow app generation"
      ],
      "source": "OpenAI Codex Automations; Cursor Automations; ServiceNow Build Agent",
      "sourceUrl": "https://developers.openai.com/codex/app/automations"
    },
    "agentCapabilities": [
      {
        "vendor": "OpenAI",
        "product": "Codex Automations",
        "mode": "automate",
        "date": "2026-06",
        "capability": "Recurring background tasks can run on a schedule, report findings to a Triage inbox, and execute in local projects or dedicated worktrees.",
        "meaning": "The important capability is not just autonomous coding; it is an inspectable recurring run with an output lane. Teams should use this for bounded maintenance before allowing unattended production writes.",
        "source": "OpenAI Developers",
        "sourceUrl": "https://developers.openai.com/codex/app/automations"
      },
      {
        "vendor": "Cursor",
        "product": "Automations",
        "mode": "automate",
        "date": "2026-06",
        "capability": "Cloud Agents can run in the background on schedules or events from GitHub, GitLab, Slack, webhooks, Linear, PagerDuty, and related systems.",
        "meaning": "Event-triggered agents turn development and operations events into work queues. The control gap is trigger governance: who can create automations, which tools they can call, and where outputs are reviewed.",
        "source": "Cursor Docs",
        "sourceUrl": "https://cursor.com/help/ai-features/automations"
      },
      {
        "vendor": "ServiceNow",
        "product": "Build Agent",
        "mode": "build",
        "date": "2026-06",
        "capability": "Build Agent extends into Cursor, Windsurf, Claude Code, and GitHub Copilot while keeping application deployment under ServiceNow platform context and governance.",
        "meaning": "This is the enterprise build-agent pattern: let creation happen in many tools, but make deployment inherit roles, policies, approvals, and audit trails from the system of record.",
        "source": "ServiceNow Newsroom",
        "sourceUrl": "https://newsroom.servicenow.com/press-releases/details/2026/ServiceNow-Build-Agent-now-works-inside-every-major-AI-coding-tool-governed-by-default/default.aspx"
      }
    ],
    "skillsAndConnectors": [
      {
        "ecosystem": "Codex",
        "name": "Automation plus skills",
        "type": "skill",
        "date": "2026-06",
        "signal": "Codex Automations documentation explicitly says automations can combine with skills for more complex recurring tasks.",
        "why": "Skills make a scheduled agent maintainable: the schedule defines when to run, while the skill defines the method and guardrails.",
        "source": "OpenAI Developers",
        "sourceUrl": "https://developers.openai.com/codex/app/automations"
      },
      {
        "ecosystem": "Cursor",
        "name": "MCP-backed background agents",
        "type": "connector",
        "date": "2026-06",
        "signal": "Cursor Automations can connect external tools through MCP and trigger from GitHub, GitLab, Slack, Linear, PagerDuty, and webhooks.",
        "why": "MCP makes the scheduled agent useful beyond the repo, but it also expands the blast radius. Permission scope and tool allowlists should be reviewed like production integrations.",
        "source": "Cursor Docs",
        "sourceUrl": "https://cursor.com/help/ai-features/automations"
      },
      {
        "ecosystem": "ServiceNow",
        "name": "Build Agent SDK skills",
        "type": "skill",
        "date": "2026-06",
        "signal": "ServiceNow describes SDK skills that teach external coding agents how to create platform-native applications.",
        "why": "Domain-specific skills turn a general coding agent into a platform-aware builder. The repeatable pattern is to package metadata, best practices, and deployment constraints as reusable agent context.",
        "source": "ServiceNow Community",
        "sourceUrl": "https://www.servicenow.com/community/developer-advocate-blog/building-servicenow-apps-via-claude-code-and-the-servicenow-sdk/ba-p/3525677"
      }
    ],
    "proofOfValue": [
      {
        "actor": "Groq",
        "workflow": "High-volume inference serving for agentic applications",
        "evidence": "confirmed",
        "claim": "Groq reports more than five million developers, thousands of AI-native companies, and trillions of tokens processed each week across 13 data centers.",
        "read": "This is a serving-capacity proof point for agentic systems: background agents need fast, cheap inference paths, not only stronger models.",
        "source": "Groq newsroom",
        "sourceUrl": "https://groq.com/newsroom/groq-raises-usd650m-to-scale-its-ai-inference-cloud-business"
      },
      {
        "actor": "ServiceNow",
        "workflow": "Governed app generation from external agentic IDEs",
        "evidence": "vendor_claim",
        "claim": "Build Agent-generated applications can inherit ServiceNow platform context, deployment approvals, lifecycle governance, and AI Control Tower oversight.",
        "read": "This is the right enterprise pattern even if buyers still need proof in their own environments: external creation surface, governed runtime, and auditable deployment.",
        "source": "ServiceNow Newsroom",
        "sourceUrl": "https://newsroom.servicenow.com/press-releases/details/2026/ServiceNow-Build-Agent-now-works-inside-every-major-AI-coding-tool-governed-by-default/default.aspx"
      }
    ],
    "enterpriseReadiness": [
      {
        "dimension": "permissioning",
        "note": "Scheduled agents should use least-privilege tool scopes and branch/worktree isolation, not broad user-equivalent permissions."
      },
      {
        "dimension": "verification",
        "note": "Every automation needs a defined verifier: tests, lint, schema checks, evals, source trails, screenshots, or human approval."
      },
      {
        "dimension": "auditability",
        "note": "Run logs should capture trigger, prompt, tools, files changed, validation output, and escalation decision."
      },
      {
        "dimension": "cost",
        "note": "Recurring agents need budgets, stop conditions, and alerting because failed loops can silently burn tokens and cloud time."
      },
      {
        "dimension": "human_approval",
        "note": "Production-impacting changes should land as draft PRs, review comments, or approval queue items unless the verifier is deterministic and low risk."
      }
    ],
    "scorecard": {
      "asOf": "2026-06-27",
      "rows": [
        {
          "mode": "chat",
          "leadingPattern": "Prompted expert assistance",
          "representativeTools": [
            "ChatGPT",
            "Claude",
            "Gemini"
          ],
          "controlGap": "Still weak on workflow state, repeatability, and source-of-truth permissions."
        },
        {
          "mode": "cowork",
          "leadingPattern": "Threaded agent with memory, files, and review",
          "representativeTools": [
            "Claude Code",
            "Cursor",
            "Codex"
          ],
          "controlGap": "Humans still need to define done, review changes, and maintain durable instructions."
        },
        {
          "mode": "build",
          "leadingPattern": "Platform-aware builder agent",
          "representativeTools": [
            "ServiceNow Build Agent",
            "Codex",
            "Cursor"
          ],
          "controlGap": "Generated artifacts need deployment approvals, policy checks, and runtime ownership."
        },
        {
          "mode": "automate",
          "leadingPattern": "Scheduled/event-triggered work loop",
          "representativeTools": [
            "Codex Automations",
            "Cursor Automations"
          ],
          "controlGap": "Inventory, budget, permissions, run logs, and escalation paths are immature in most teams."
        }
      ]
    },
    "tryThis": {
      "title": "Create one low-risk scheduled-agent runbook",
      "steps": [
        "Pick a recurring task that already has a deterministic check, such as dependency drift, stale links, lint failures, or weekly content freshness.",
        "Write a loop contract with trigger, repo/branch, allowed tools, verifier command, budget, output destination, and escalation rule.",
        "Run it once manually in an isolated worktree, inspect the diff/log, then decide whether it is safe to schedule."
      ],
      "expectedOutcome": "You learn whether the task is automation-ready and produce a reviewable template for higher-risk background agents."
    },
    "watchlist": [
      {
        "window": "July 2026",
        "title": "Admin controls for background coding agents",
        "why": "The next enterprise differentiator is who gives admins inventory, budgets, approvals, and run logs across scheduled agents."
      },
      {
        "window": "Q3 2026",
        "title": "MCP permission failures",
        "why": "As scheduled agents gain connector access, the first visible failures will likely come from overbroad tool scopes or poisoned persistent memory."
      },
      {
        "window": "Q3 2026",
        "title": "From draft PR to auto-merge",
        "why": "Watch whether low-risk agent loops begin moving from 'create review artifact' to 'apply automatically after deterministic checks'."
      }
    ],
    "changelog": [
      "W26 spotlights Scheduled Agent Operations: recurring/event-triggered agents with explicit trigger, sandbox, verifier, budget, and escalation contracts."
    ]
  }
}