Sub-Agent Workbenches

Execution environments used by sub-agents and crews to perform deep specialist work.

AgentSub-AgentCrewWorkbenchValidatorHuman Approval

Agent Nexus workforce model

Agents are digital employees. Sub-agents are specialist employees. Crews are specialist teams. Workbenches are their tools, checklists, playbooks, and operating dashboards. Validators are independent reviewers. Humans remain final approvers for high-risk decisions.

Agent
Owns a business function
Sub-Agent
Handles a specialist track
Crew
Executes as a specialist team
Workbench
Provides tools and playbooks
Validator
Checks quality and risk
Approval
Keeps humans accountable

Agent → Sub-Agent → Crew → Workbench

A workbench is not an agent. It is the execution environment used by a sub-agent and its crew.

Workforce hierarchy
Coordinator
Selects workflow and routing
Primary Agent
Owns business outcome
Sub-Agent
Handles specialist track
Crew
Executes as expert team
Workbench
Tools, playbooks, checklists
Validators
Independent quality gates
Approval
Human accountability
Example
Pre-Sales Agent
Cisco Sub-Agent
Cisco Crew
Cisco Workbench
Cisco RAG + BoM + Licensing Validator
Cisco Recommendation
Finance / Legal / Operations / MD Approval
A workbench is not an agent. It is the workspace used by a sub-agent or crew to complete specialist work with tools, checklists, validators, evidence and approval gates.

Cisco Workbench

Workbench
Used by
Cisco Sub-Agent + Cisco Crew
Used for
Cisco architecture, SD-WAN, LAN/WLAN, BoM assumptions, licensing, security dependencies, delivery handoff.
Primary outputs
Cisco recommendation, budgetary BoM assumptions, licensing assumptions, risk notes, validation points.
Vendor / human validation required for final BoM and pricing.
Open Cisco Workbench

Cloud Workbench

Workbench
Used by
Cloud Sub-Agent + Cloud Crew
Used for
AWS / Azure / GCP architecture, landing zone, migration, FinOps, DR, reliability, Cloud-Ops.
Primary outputs
Cloud architecture, landing zone assumptions, migration plan, cost estimate, DR and operations handoff.
Human validation required for final pricing, SLA, production architecture, and cutover.
Open Cloud Workbench

Application / AI / Security Workbench

Workbench
Used by
Application, AI/Data, Security Sub-Agents + IT-Security Review Crew
Used for
Application architecture, API integration, RAG, model selection, guardrails, evaluation, compliance, security review.
Primary outputs
Application architecture, API plan, RAG design, data map, security findings, guardrails, approval requirements.
Human validation required for security risk acceptance, data privacy, legal compliance, and production approvals.
Open Application / AI / Security Workbench

How they fit into the enterprise workflow

  1. LangGraph Coordinator selects the relevant primary agent and workflow.
  2. The primary agent delegates specialist work to sub-agents.
  3. Sub-agents invoke crews when deeper domain execution is required.
  4. Crews use workbenches for tools, checklists, validators and evidence.
  5. Validators independently verify outputs before approval or final synthesis.

Design principle

Use the minimum required sub-agents and crews for a task. Cisco runs only when networking is in scope. Cloud, Application, AI/Data and Security run only when their domain is required. IT-Security Review runs independently when customer data, production systems or compliance risk is involved.