Skip to content

1.4.0

Latest
Latest

Choose a tag to compare

View all tags
@JBurlison JBurlison released this 19 Feb 00:55
1.4.0
50c1438

Full Changelog: 1.3.0...1.4.0

Release Notes — v1.4.0

Date: February 18, 2026
Previous: v1.3.0
Commits: 1 (50c1438)
Files changed: 2 (+186 / -108)

Highlights

  • Orchestrator + Sub-Agents pattern formalized as the default workflow architecture, replacing the previous "workflow manager with handoffs" model.
  • Handoffs are now opt-in only — orchestrators no longer include handoffs by default; they must be explicitly requested by the user.
  • Sub-agents prohibited from defining handoffs — handoff buttons are only rendered for user-facing agents.
  • Three distinct agent templates — documentation now provides separate format templates for user-facing agents, orchestrators, and sub-agents.

Breaking Changes

  • The term "workflow manager" has been replaced with "orchestrator" throughout all documentation and templates. Existing workflow manager agents remain functional but should be updated to follow the new naming convention.
  • Handoffs removed from default orchestrator template. Previously, workflow templates included handoff configuration by default. Handoffs are now only added when explicitly requested by the user.

Agent Changes: ai-builder

Orchestrator Pattern (renamed from "Workflow Manager")

  • All references to "workflow manager" updated to "orchestrator" across the agent definition, examples, templates, and validation checklist.
  • Workflow description updated: "An orchestrator + sub-agents pattern" is now the explicitly stated default.
  • New directive: "Do not add handoffs unless the user explicitly requests them."

Three Distinct Agent Format Templates

The single agent format template has been split into three role-specific templates:

Template File Pattern Key Characteristics
User-Facing Agent .agent.md user-invokable: true, standard interactive agent
Orchestrator .agent.md user-invokable: true, requires agent tool, defines agents list, manages sub-agent invocations
Sub-Agent .subagent.agent.md user-invokable: false, no handoffs, scoped instructions only

Orchestrator Template Details

  • Must include 'agent' in the tools list to enable #runSubagent invocations.
  • Defines agents: ['*'] (or specific list) to control which sub-agents it can call.
  • Instructions describe workflow order and sub-agent coordination (not direct code editing).
  • Handoffs section only included when user explicitly requests them.

Sub-Agent Restrictions Clarified

  • Sub-agents must not include handoffs — handoff buttons are only rendered for user-facing agents.
  • Sub-agents cannot communicate with the user directly; they return output (including questions) to the orchestrator.

Handoff Configuration Section Removed from Default

  • The previous "Handoff Configuration" section with send: true/false guidance has been removed from the default documentation flow.
  • Handoff design questions ("Where should humans review?", "send: true/false appropriateness") removed from the design considerations.

Updated Design Flow Diagram

[Orchestrator (Descriptive Name)] --#runSubagent--> [Sub-Agent A: Planning]
         │
         ▼  (receives output, relays questions if any)
[Orchestrator] --#runSubagent--> [Sub-Agent B: Implementation]
         │
         ▼
[Orchestrator] --#runSubagent--> [Sub-Agent C: Review]

Validation Checklist Updates

  • "Workflow manager" → "Orchestrator" in all checklist items
  • Removed: "Handoff points align with natural review/decision points"
  • Removed: "send: true/false is appropriate for each transition"
  • Added: "Handoffs are present only if explicitly requested by the user"
  • Added: Sub-agents must have no handoffs

Workflow Rules Updated

  • "ALWAYS create a descriptively named orchestrator agent (user-invokable)"
  • "All phase agents must be sub-agents with user-invokable: false and no handoffs"
  • "Do NOT add handoffs to the orchestrator unless the user explicitly requests them"

Minor Updates

  • agents field example reverted to ['*'] with cleaner comment syntax
  • Example description wording: "A multi-agent workflow with handoffs" → "An orchestrator + sub-agents workflow"

Skill Changes: agent-file-specs

references/AGENTS.md

  • Added three separate agent format sections: User-Facing Agent, Orchestrator / Workflow Manager Agent, and Sub-Agent — each with its own template and description.
  • Sub-agent guidance strengthened from "should" to "must": user-invokable: false is now mandatory, not recommended.
  • New callout block: "Sub-agents must not define handoffs. Handoff buttons are only rendered for user-facing agents."
  • Example agent renamed from "Planning Agent" to "Planning Agent (user-facing)" for clarity.
Assets 2
Loading