Agents & Workflows
25 customer-facing AI agents organized into 6 capability domains. Each agent follows the RIGOR verification framework and can be orchestrated together into end-to-end workflows.
Shared Agents: debug-ai and review-ai
Two agents serve both BUILD and OPERATE with different roles. In BUILD, debug-ai handles development debugging; in OPERATE, it performs production root cause analysis. In BUILD, review-ai does code review and PR gates; in OPERATE, it validates fixes before deployment. Learned patterns in one capability improve performance in the other.
BUILD — Software Development Lifecycle
7 agents (includes shared agents)
req-aiRequirements
Analyzes requirements, creates specifications, generates user stories from natural language descriptions
autonoma req-ai analyze --file ./requirements.mdautonoma req-ai validate --file ./spec.yamlplanner-aiPlanning
Project planning, task breakdown, sprint organization, effort estimation, and dependency identification
autonoma planner-ai plan --file ./requirements.mdautonoma planner-ai estimate --scope ./spec.yamlarchitect-aiArchitecture
System design, architecture modeling, technology selection, and design pattern recommendations
autonoma architect-ai design --file ./requirements.mdautonoma architect-ai validate --architecture ./arch.yamlcoder-aiCode Generation
Code generation, feature implementation, refactoring, and multi-language support from specifications
autonoma coder-ai generate --file ./spec.yaml --language typescriptautonoma coder-ai refactor --file ./src/service.tsreview-aiCode Review
Code review, PR quality gates, coding standards enforcement, and security pattern verification
autonoma review-ai review --pr 123autonoma review-ai style --path ./srctester-aiTesting
Test generation, quality assurance, coverage analysis, and test suite optimization
autonoma tester-ai run --suite integrationautonoma tester-ai coverage --path ./srcdebug-aiDebugging
Development debugging, issue resolution, error tracing, and fix suggestions
autonoma debug-ai analyze --error "Connection timeout"autonoma debug-ai troubleshoot --service apiBUILD Workflow (Orchestrated)
req-ai → planner-ai → architect-ai → coder-ai → review-ai → tester-ai → debug-ai (as needed)
The BUILD workflow follows the software development lifecycle. Requirements are analyzed, planned into tasks, architected, implemented, reviewed, tested, and debugged. Each phase runs through RIGOR verification before handing off to the next agent.
OPERATE — Operations & Incident Management
8 agents (includes shared agents)
deploy-aiDeployment
Deployment automation, canary releases, blue-green deployments, and rollback management
autonoma deploy-ai deploy --env production --strategy canaryautonoma deploy-ai rollback --deployment dep-123maintain-aiMaintenance
Routine maintenance, self-healing operations, dependency updates, and system health management
autonoma maintain-ai health --service apiautonoma maintain-ai maintenance --type scheduledobserve-aiObservability
Monitoring, metrics collection, alerting, anomaly detection, and CloudWatch integration
autonoma observe-ai metrics --service apiautonoma observe-ai alerts --severity criticalincident-aiIncident Response
Incident triage, severity classification, escalation coordination, and postmortem generation
autonoma incident-ai triage --incident INC-456autonoma incident-ai escalate --incident INC-456debug-aiRoot Cause Analysis
Production root cause analysis, distributed tracing, and incident diagnosis
autonoma debug-ai analyze --error "Connection timeout"autonoma debug-ai logs --service api --tail 100review-aiPre-Deploy Verification
Validates fixes and changes before deployment to production, verifies remediation quality
autonoma review-ai review --pr 456autonoma review-ai security --path ./srccapacity-aiCapacity Planning
Capacity forecasting, auto-scaling recommendations, resource optimization, and load planning
autonoma capacity-ai forecast --service api --period 30dautonoma capacity-ai recommend --cluster productionbackup-aiBackup & Recovery
Backup management, disaster recovery planning, snapshot scheduling, and restore verification
autonoma backup-ai create --target databaseautonoma backup-ai verify --backup bak-789OPERATE Workflow (Orchestrated)
observe-ai (detect) → debug-ai (diagnose) → incident-ai (coordinate) → maintain-ai (fix) → review-ai (verify) → deploy-ai (ship) capacity-ai + backup-ai run as continuous background operations
The OPERATE workflow is event-driven. Observability agents detect issues, diagnosis agents find root causes, incident response coordinates remediation, maintenance agents apply fixes, review verifies quality, and deployment ships the fix. Capacity planning and backup operations run continuously in the background.
SECURE — Security Scanning & Threat Detection
2 agents
security-aiSecurity Scanning
Container scanning, dependency analysis, code scanning, secrets detection, IaC validation, and compliance checks
autonoma security-ai scan --path ./project --type allautonoma security-ai scan --type dependencies --severity criticalthreathunter-aiThreat Hunting
Proactive threat hunting, IOC matching, attack path analysis, MITRE ATT&CK mapping, and ML-based anomaly detection
autonoma "hunt for threats in infrastructure"POST /api/workflows/invoke { capability: "SECURE" }SECURE Workflow (Orchestrated)
security-ai (scan & prevent) → threathunter-ai (hunt & detect) → correlate findings
SECURE combines prevention and detection. security-ai focuses on finding vulnerabilities before exploitation (shift-left scanning). threathunter-ai focuses on detecting active threats and attack patterns. Together they provide a complete security lifecycle from prevention to detection.
GOVERN — Compliance & Policy Management
3 agents
govern-aiGovernance
Organization-wide governance audits, compliance framework validation (SOC2, HIPAA, PCI-DSS), and regulatory reporting
autonoma govern-ai audit-trail --scope allautonoma govern-ai approval --request req-123policy-aiPolicy Management
Policy definition, enforcement, validation against deployment configurations, and automated remediation
autonoma policy-ai check --config ./deployment.yamlautonoma policy-ai enforce --scope productiontenant-aiMulti-Tenant Isolation
Tenant provisioning, isolation verification, resource quota management, and cross-tenant security validation
autonoma tenant-ai check-isolation --tenant acme-corpautonoma tenant-ai quotas --tenant acme-corpGOVERN Workflow (Orchestrated)
govern-ai (audit) → policy-ai (enforce) → tenant-ai (isolate)
GOVERN ensures organizational compliance. Governance agents audit against frameworks, policy agents enforce rules on configurations and deployments, and tenant agents manage multi-tenant isolation boundaries.
OPTIMIZE — Performance & Cost Optimization
4 agents
optimize-aiPerformance
Performance analysis, bottleneck identification, latency optimization, and throughput recommendations
autonoma optimize-ai analyze --target ./apiautonoma optimize-ai benchmark --endpoint /api/userscost-aiCost Management
Cloud cost analysis, rightsizing recommendations, reserved instance planning, and waste identification
autonoma cost-ai report --period 30dautonoma cost-ai optimize --scope computedba-aiDatabase Administration
Database performance analysis, query optimization, index recommendations, and schema tuning
autonoma dba-ai analyze-queries --database productionautonoma dba-ai indexes --database productionbilling-aiBilling & Metering
Usage metering, billing report generation, customer billing management, and forecast modeling
autonoma billing-ai usage --period 30dautonoma billing-ai analytics --scope allOPTIMIZE Workflow (Orchestrated)
optimize-ai (analyze) → cost-ai (reduce spend) → dba-ai (tune queries) → billing-ai (report)
OPTIMIZE agents work together to improve efficiency. Performance agents identify bottlenecks, cost agents find savings, DBA agents tune database workloads, and billing agents track and report usage.
EVOLVE — Learning & Adaptation
3 agents
adapt-aiAdaptive Learning
Learns from user feedback, adapts agent behavior, improves recommendations based on patterns
autonoma adapt-ai feedback --model coder-ai --rating goodautonoma adapt-ai evaluate --model coder-aievolve-aiSystem Evolution
Analyzes system maturity, recommends architectural improvements, and tracks evolution metrics
autonoma evolve-ai assess --scope architectureautonoma evolve-ai plan --target microservicessuccess-aiCustomer Success
Customer health scoring, proactive recommendations, onboarding optimization, and retention analysis
autonoma success-ai health --customer acme-corpautonoma success-ai engagement --period 30dEVOLVE Workflow (Orchestrated)
adapt-ai (learn from feedback) → evolve-ai (recommend improvements) → success-ai (track outcomes)
EVOLVE agents continuously improve the platform. Adaptive learning incorporates user feedback, evolution agents recommend system improvements, and customer success agents ensure teams are getting maximum value.
Cross-Capability Workflows
Cross-capability workflows are goal-driven with defined workflow templates as the starting constraint. Each workflow type has a deterministic agent pipeline that ensures consistent RIGOR execution. The orchestrator holds the stated objective, follows the workflow template, and applies RIGOR verification at every phase — while adapting execution order within the template based on agent load and learned patterns.
Workflow-Constrained Goal Orchestration
Every cross-capability workflow starts from a defined template — a deterministic agent pipeline with known capabilities and RIGOR gates. This ensures consistency and rigor. The orchestrator is goal-aware within that workflow constraint, not free-form reasoning about which agents to involve.
Each workflow type maps to a defined agent pipeline and execution pattern (sequential, parallel, hierarchical). This is the deterministic starting point — not negotiable.
The orchestrator holds the stated objective through execution. Each agent in the pipeline receives the goal context, not just its isolated input. On failure, the orchestrator retries or escalates within the workflow — not by inventing a new plan.
Q-Learning from execution outcomes improves how the workflow executes (parallelization, load balancing, timeout tuning) — not which agents are involved. The workflow template is the constraint; optimization happens within it.
Full SDLC
End-to-end software delivery: requirements through deployment with security validation
req-ai → planner-ai → architect-ai → coder-ai → tester-ai → review-ai → security-ai → deploy-ai → observe-aiIncident Response
Detect issue in production, diagnose root cause, implement fix, validate security, deploy hotfix. Median MTTR drops from days to under 30 minutes.
observe-ai → incident-ai → debug-ai → coder-ai → tester-ai → review-ai → security-ai → deploy-aiSecurity-Driven Refactoring
Vulnerability discovered, code remediated, tested, and safely deployed. Average vulnerability takes 60-90 days to remediate manually — agents reduce this to hours.
security-ai → threathunter-ai → coder-ai → tester-ai → review-ai → deploy-aiDependency Update Cascade
Prioritize CVEs, assess architecture impact, update dependencies with compatibility fixes, test, and deploy via canary.
security-ai → architect-ai → coder-ai → tester-ai → review-ai → deploy-aiCompliance Audit Automation
Continuous compliance evidence collection across security posture, monitoring SLAs, backup verification, and tenant isolation — eliminates weeks of manual audit prep.
govern-ai → security-ai → policy-ai → observe-ai → backup-ai → tenant-ai → review-aiCost Anomaly Remediation
Detect cloud cost spikes, correlate with deployments, right-size resources, implement infrastructure changes, and track savings.
cost-ai → observe-ai → capacity-ai → optimize-ai → coder-ai → deploy-ai → billing-aiPerformance Regression Fix
Detect performance regression, bisect deployments, profile code, optimize queries, implement fix, and validate.
observe-ai → debug-ai → optimize-ai → dba-ai → coder-ai → tester-ai → deploy-aiTechnical Debt Prioritization
Continuously analyze codebase evolution, measure performance impact, prioritize debt by ROI, and generate refactoring plans.
evolve-ai → optimize-ai → security-ai → architect-ai → planner-ai → coder-ai → tester-aiThreat-to-Incident Correlation
Proactive threat detection triggers incident response workflow
threathunter-ai → incident-ai → observe-ai → debug-aiInvoking Workflows & Tracking Progress
Three ways to invoke agent workflows: natural language, CLI commands, or the REST API. All methods support real-time progress tracking via Server-Sent Events.
Natural Language
Describe what you want — the orchestrator selects the right agents automatically.
# The CLI routes to the right agents autonoma "review my staged changes for security" autonoma "deploy to production with canary" autonoma "analyze slow database queries" # Watch real-time RIGOR progress autonoma "refactor auth service" --watch
CLI Commands
Invoke specific agents directly for precise control over which agent handles your request.
# Direct agent invocation
autonoma security-ai scan --path ./src
autonoma tester-ai coverage --path ./src
autonoma deploy-ai deploy --env prod
# Orchestrated multi-agent workflow
autonoma orchestrator-ai execute \
--workflow full-sdlc \
--input '{"prompt":"Add auth"}'REST API
Programmatic access for CI/CD, dashboards, and custom integrations.
# Invoke a workflow
POST /api/workflows/invoke
{
"capability": "BUILD",
"workflow": "generate-code",
"input": {
"prompt": "Add OAuth2 auth",
"scope": "mvp"
}
}
# → 202 { workflowId, statusUrl }
# Check status
GET /api/workflows/{id}/status
# → { status, phases, output }Real-Time Progress Tracking
Every workflow execution streams RIGOR phase progress in real-time via Server-Sent Events (SSE). The CLI, Dashboard, and VS Code extension all connect to the same event stream.
CLI (--watch flag)
$ autonoma orchestrator-ai execute \
--task "review security" --watch
RIGOR Progress: review-ai
━━━━━━━━━━━━━━━━━━━━━━━━━━
Research ✅ Completed 92% 3.2s
Inspect ⏳ Running — —
Generate ⬜ Pending — —
Optimize ⬜ Pending — —
Review ⬜ Pending — —SSE Event Stream (API)
GET /api/admin/events/stream
?execution_id=exec-abc123
# Stream response:
event: phase_started
data: {"phase":"Research",
"agent_id":"review-ai"}
event: work_progress
data: {"phase":"Research",
"progress":92,
"confidence":0.92}
event: phase_completed
data: {"phase":"Research",
"duration_ms":3200}Live RIGOR phase progress bar with confidence scores
Animated terminal progress via --watch flag
Agent Orchestration sidebar with tree view
Auto-updating progress comment on pull requests
| Endpoint | Method | Purpose | Auth |
|---|---|---|---|
| /api/workflows/invoke | POST | Invoke a capability workflow | API Key |
| /api/workflows/{id}/status | GET | Check workflow execution status | API Key |
| /api/workflows | GET | List workflow executions | API Key |
| /api/workflows/cancel/{id} | POST | Cancel a running workflow | API Key |
| /api/agents/tasks | POST | Submit a development task | API Key |
| /api/agents/tasks/{taskId} | GET | Check task status and progress | API Key |
| /api/agents/{id}/{action} | POST/GET | Direct agent action invocation | Session |
Orchestration Architecture
Tier 1: Capability Orchestrator
Each capability domain has its own orchestrator that executes workflows using defined agent pipelines. The orchestrator holds the goal context and applies RIGOR verification at every phase.
- Deterministic workflow templates define which agents execute
- Goal-aware: passes objective context to each agent in the pipeline
- RIGOR phases enforce quality gates at every step
- Q-Learning optimizes execution within the template (parallelization, timeouts)
- ACMF mode enforcement with auto-regression on failure
Tier 2: Meta-Orchestrator
Coordinates cross-domain workflows using defined templates that specify which capabilities and agents participate. Ensures consistent RIGOR execution across domain boundaries.
- Cross-capability workflow templates (e.g., Full SDLC, Incident Response)
- GoalDispatcher routes to template-defined agents via deterministic mapping
- 5 execution patterns: sequential, parallel, hierarchical, group chat, debate
- Cross-agent knowledge graph for shared learning within templates
- V2 MARL optimization (planned) — multi-agent reinforcement learning for execution tuning
- V3 RAFT consensus (planned) — distributed decision-making across orchestrator replicas
- Meta-selector routing (planned) — automatic version selection based on task characteristics
Deterministic Templates. Elastic Execution.
Workflow templates are the what. The orchestrator's elasticity determines the how. RIGOR ensures the quality.
Think of it like a CI/CD pipeline: the pipeline definition is fixed — you don't want your deploy pipeline randomly deciding to skip testing. But execution is adaptive — steps parallelize when possible, retry on failure, scale runners up and down, and each step receives context-aware inputs.
- Which agents participate — defined by the workflow template, not negotiable
- Quality gates — RIGOR phases execute for every step, no shortcuts
- Goal-type routing — deterministic mapping from workflow type to agent pipeline
- Execution pattern — 5 patterns (sequential, parallel, hierarchical, group chat, debate) selected per workflow
- Parallelization — RIGOR Optimize phase identifies steps that can run concurrently within the template
- Load-aware scheduling — overloaded agents (>85% load) trigger backpressure, queueing, or timeout adjustment
- Fallback & retry — progressive timeouts, exponential backoff, circuit breakers — transient failures don't kill the workflow
- Agent auto-scaling — agents scale to zero when idle and wake on demand, elastic to actual workload
- Context enrichment — same template produces different inputs based on project knowledge graph, so execution adapts to your codebase
- MARL optimization (V2, planned) — cooperative Q-learning tunes agent selection and scheduling within templates
- RAFT consensus (V3, planned) — distributed orchestrator replicas achieve consensus on critical decisions
1. Template selected → Full SDLC pipeline: req-ai → planner-ai → architect-ai → coder-ai → review-ai → tester-ai
2. RIGOR Research → Evaluates hypotheses: sequential (0.65) vs parallel (0.88) vs conditional (0.72)
3. RIGOR Inspect → Checks agent load: architect-ai at 92% → flags for backpressure
4. RIGOR Optimize → Detects req-ai and planner-ai have no data dependency → parallelizes them
5. Knowledge enrichment → Injects project context (tech stack, past failures, codebase patterns) into each agent payload
6. Execution → Same template, different execution profile every time — optimized for current conditionsEvery Agent Follows RIGOR
All 25 customer-facing agents execute tasks through the 5-phase RIGOR verification framework. No agent takes action without completing Research, Inspect, Generate, Optimize, and Review phases.
Research
Gather context, validate assumptions, identify constraints
Inspect
Audit safety, verify constraints, check preconditions
Generate
Execute task, produce artifact with confidence scoring
Optimize
Tune performance, minimize cost, apply learnings
Review
Validate outcome, run quality gates, prepare rollback
RIGOR Optimize & Review Feedback Loop
The Optimize and Review phases of RIGOR are not just execution gates — they are a continuous feedback loop that improves every subsequent workflow execution. Patterns discovered by one agent improve all agents across the fleet.
Optimize Phase (Learning)
After generating output, agents analyze their own performance and publish patterns to the shared knowledge graph.
- Pattern detection: Agents publish learned patterns to
learning.pattern.detectedNATS topic - Cross-agent learning: All agents subscribe to patterns from other agents — a security pattern discovered by security-ai improves coder-ai's code generation
- Quality scoring: Each agent publishes quality metrics to agent-specific scoring topics for ACMF progression tracking
- Performance tuning: Execution time, confidence scores, and resource usage feed back into routing decisions
Review Phase (Validation)
Multi-dimensional quality gates validate output and trigger automatic workflow improvements on failure.
- Gate results: 21 quality gates across safety, correctness, performance, and compliance dimensions
- ACMF regression: Failed reviews automatically regress agents to lower autonomy levels, requiring human approval for subsequent executions
- Workflow refinement: Repeated failures in specific workflow steps trigger orchestrator re-routing — e.g., adding a security scan before deployment if security-ai finds recurring issues
- Audit trail: Every gate result is recorded for compliance and postmortem analysis
How the Feedback Loop Works
Execution N Execution N+1
┌──────────┐ ┌──────────┐
│ Research │ │ Research │ ← uses patterns from N
│ Inspect │ │ Inspect │ ← stricter if N failed gates
│ Generate │ │ Generate │ ← applies learned optimizations
│ Optimize │──→ Knowledge Graph ──→│ Optimize │ ← builds on prior patterns
│ Review │──→ ACMF Scores ──→│ Review │ ← adjusted gate thresholds
└──────────┘ Quality Metrics └──────────┘
│ │
└──→ learning.pattern.detected ──────┘
└──→ agent.{id}.quality.score ───────┘Products
Autonoma agents are available as separate capability products on AWS Marketplace.
Core Products
| Product | Agents | Description |
|---|---|---|
| BUILD | 7 agents (5 core + 2 shared): req-ai, planner-ai, architect-ai, coder-ai, review-ai, tester-ai, debug-ai | Software development lifecycle — requirements through code review |
| OPERATE | 8 agents (6 core + 2 shared): deploy-ai, maintain-ai, observe-ai, incident-ai, debug-ai, review-ai, capacity-ai, backup-ai | Operations and incident management — deployment through disaster recovery |
| SECURE | 2 agents: security-ai, threathunter-ai | Security scanning and threat detection |
| PLATFORM | 15 unique agents (BUILD + OPERATE + SECURE combined) | Full SDLC with cross-capability orchestration via MetaOrchestrator |
Additional Capability Products
These are separate products that can be added to any core product subscription.
| Product | Agents | Description |
|---|---|---|
| GOVERN | 3 agents: govern-ai, policy-ai, tenant-ai | Compliance, policy management, and multi-tenant isolation |
| OPTIMIZE | 4 agents: optimize-ai, cost-ai, dba-ai, billing-ai | Performance, cost, and database optimization |
| EVOLVE | 3 agents: adapt-ai, evolve-ai, success-ai | Adaptive learning, system evolution, and customer success |
Intelligence Tiers
Intelligence tiers control efficiency and security tooling within each product. They are orthogonal to which products you subscribe to — a BUILD customer on Core intelligence uses different security tools than a BUILD customer on Ultra intelligence.
| Tier | Efficiency | Security Tools |
|---|---|---|
| CORE | Standard efficiency | Trivy container scanning, basic threat hunting |
| PRO | 30% more efficient | + Snyk dependency scanning, advanced threat queries |
| ULTRA | 50% more efficient | + SAST code analysis, custom rules, attack path analysis |
IDE Integrations
Autonoma Code integrates with traditional IDEs — the editors where your team already works. All integrations connect to the same SSE event stream for real-time agent and RIGOR progress visibility.
VS Code
AvailableAgent orchestration sidebar, inline RIGOR progress, deployment readiness checks.
code --install-extension autonoma.autonoma-cloud-environmentJetBrains
PlannedSingle plugin for IntelliJ, WebStorm, GoLand, PyCharm. Tool Window for agent status, editor annotations, SSE streaming.
GitHub Codespaces
CompatibleVS Code extension works in Codespaces. Pre-configured via devcontainer.json for zero-friction onboarding.
Neovim
PlannedLua plugin via built-in LSP client. Connects to Autonoma LSP service for code intelligence and agent invocation.
Autonoma Code vs. AI-Native Editors
Autonoma Code is not a competitor to Cursor, Windsurf, or other AI-native editors. Those tools provide inline code completions and single-model chat within a forked editor. Autonoma Code is a governed autonomous SDLC platform — 25 specialized agents orchestrating your entire software lifecycle from requirements through production monitoring, with enterprise governance, audit trails, and progressive autonomy. Autonoma Code integrates with the IDEs your team already uses, not proprietary editor forks.
All IDEs can also use the CLI (autonoma) for agent invocation and the REST API for custom integrations.