Agents

​

Questions This Page Answers

• Which OrgX agents are real and supported right now?
• What each agent is best at, and when it should be selected
• Why specialist routing beats a single generic assistant
• How autonomy, trust, and budget controls affect agent execution

​

Why Specialist Agents Win

• Higher quality per domain: Engineering, product, design, sales, marketing, and operations have different success criteria.
• Less rework: The orchestrator routes tasks to the right specialist first instead of letting one model guess.
• Faster review loops: Decision cards are easier to approve when the right agent produced the artifact.
• Safer autonomy: Trust and budget controls are applied per agent capability, not as one global “on/off.”

​

Canonical Agent Domains

​

How Selection Works

​

Multi-Agent Patterns (Common)

• product-agent → engineering-agent: plan first, then implement.
• design-agent → engineering-agent: spec clarity before code.
• marketing-agent + sales-agent: aligned narrative from top funnel to close.
• operations-agent + orchestrator-agent: unblock and stabilize stalled execution.

​

Governance: Trust, Autonomy, Budget

{
  "tool": "get_my_trust_context",
  "args": { "workspace_id": "ws_...", "agent_type": "engineering-agent" }
}

{
  "tool": "start_autonomous_session",
  "args": {
    "max_cost_usd": 5.0,
    "max_receipts": 50,
    "scope": ["workstream_123"]
  }
}

​

What Agents Do Not Do

• They do not access tools you have not connected.
• They do not bypass your decision policy unless you explicitly allow it.
• They do not spend beyond configured guardrails.
• They do not cross workspace boundaries.

​

Next Steps