Autonomous AI agent orchestrator — Claude, Codex, Cursor-family CLIs, and the Responses API. Part of the Enact OS product line; replaced OMX-era surfaces with enact-factory naming so the pipeline is a Executor/Reviewer/Tester/Documenter assembly line, not a factory.

Enact Factory orchestrates multiple AI agents as autonomous code executors. It picks up workItems (from Azdo, GitHub, or a local workItem directory), runs Executor/Reviewer pair pipelines, reports to Discord, and retains long-term memory via LanceDB. Today the HTTP provider seam is the Responses API; CLI-backed agent surfaces remain the reference for full agent behavior until the Responses loop contract in docs/a_proposed/RESPONSES_AGENT_LOOP_SEMANTICS.md is implemented end to end.

Three nouns keep the system's concepts distinct. New readers should learn these before anything else:

Operator lanes (allowlisted values for operatorLane):

• manual — operator explicitly opted out of automation
• none — no operator assigned
• autopilot — operator lane with durable state, phases, transitions, resume, and stop-policy parity
• ralph — generic loop operator (durable state, stop policy)
• ultrawork — WorkItem-aware loop operator (durable state, stop policy)
• team — collective operator (durable state, started via factory_team_init)

Pipeline stages (values in autonomous.defaultStages):

• coder — LLM generates code (was executor in config; the packaged skill named executor stays unchanged)
• critic — LLM reviews code (was reviewer in config; the packaged skill named reviewer stays unchanged)
• tester, documenter, auditor, stage-documenter — remaining pipeline stages (was skill-documenter)

Important: pipeline, swarm, ultrapilot, executor, and reviewer are NOT operator lane values. executor and reviewer are pipeline stages (and packaged skill names), not lanes.

This repo is internal-only (no npm publish). Build from source:

git clone <azure-devops-url>/enact-factory
cd enact-factory
npm install
npm run build
node dist/cli.js

That's it. enact-factory with no arguments launches the TUI chat interface immediately.

Status bar shows: provider · model · message count · cumulative cost

enact-factory                        # TUI chat (default)
enact-factory chat [session]         # Simple readline chat
enact-factory dash                   # Open dashboard only (UI + AzDO sync, no autonomous runner)
enact-factory start                  # Start full daemon (reads the root config.toml)
enact-factory run "Fix the bug" -p ~/my-project   # Run a single task
enact-factory exec "Run tests" --local --pipeline # Execute via daemon
enact-factory init                   # Generate config.toml scaffold
enact-factory validate               # Validate the active config.toml

# Code Registry & BS Detector
enact-factory check --scan           # Scan repo → register all entities
enact-factory check src/foo.ts       # File brief (entities, tests, risk)
enact-factory check --bs             # BS pattern scan (bad code smells)
enact-factory check --stats          # Registry statistics
enact-factory check --high-risk      # High-risk entities
enact-factory check --search "name"  # Full-text search
enact-factory annotate "funcName" --deprecate "reason"
enact-factory annotate "funcName" --tag "needs-refactor"
enact-factory annotate "funcName" --warn "error/security: SQL injection"

enact-factory setup                    # Prompts project vs ~/.enact, then installs layout + Factory docs only
enact-factory setup --scope project    # Skip prompt; install to <repo>/.enact/
enact-factory setup --no-ask           # Skip prompt; use saved delivery scope
enact-factory doctor                   # Read readiness + ownership checks
enact-factory hud                      # Render text HUD from .enact/factory state
enact-factory task list                # List mirrored Factory tasks
enact-factory session status           # Show current Factory session
enact-factory team init                # Initialize tmux/mock team state
enact-factory team status              # Inspect team + tmux readiness
enact-factory plugins status           # Inspect plugin marketplace/install state
enact-factory plugins list             # List repo-local plugin scaffolds under <root>/extensions
enact-factory agents install           # Install Factory AGENTS.md template into a target repo
enact-factory audit provider-boundary  # Check memory/knowledge/provider narrowing
enact-factory uninstall                # Remove Factory-owned Codex-facing setup

The Factory runtime assets ship from this repo, while host plugin delivery is owned by enact-extensions:

• Install host surfaces with enact-extensions install enact-factory --platform <surface> or --platform all.
• The canonical host plugin bundle lives in /Users/tarunrana/Documents/Repos/enact-extensions/extensions/enact-factory.
• .agents/plugins/marketplace.json provides the local marketplace surface.
• Provider-boundary and replacement-readiness are enforced by the in-repo audit and doctor surfaces.

Exit codes: 0 success · 1 failure · 2 timeout

For autonomous operation (Azdo workItem processing, Discord control, PR auto-improvement), you need a full config:

• Node.js >= 22
• Claude Code CLI authenticated (claude -p) — default provider
• OpenAI Codex CLI (codex exec) — optional alternative provider
• Discord Bot token with message content intent
• Azdo API key and team ID
• GitHub CLI (gh) for CI monitoring (optional)

git clone https://github.com/unohee/Enact-Factory.git
cd Enact-Factory
npm install
edit ../config.toml

Create a .env file:

DISCORD_TOKEN=your-discord-bot-token
DISCORD_CHANNEL_ID=your-channel-id

# AzDo — all four required for live WorkItem round-tripping
AZDO_ORG=your-azdo-org
AZDO_PROJECT=your-azdo-project
AZDO_PAT=your-azdo-personal-access-token
AZDO_TEAM_ID=your-azdo-team-id
# AZDO_API_KEY is a legacy alias for AZDO_PAT (some surfaces still read it)
AZDO_API_KEY=${AZDO_PAT}

The root config.toml supports ${VAR} / ${VAR:-default} substitution and is validated with Zod schemas.

Run these in order. Each step has a clear failure mode if skipped.

1. Build the dist tree. Factory runtime and MCP surfaces read compiled JS from dist/. On a fresh clone before build, governance behavior is incomplete.

   pnpm build

2. Postgres reachable. WorkItem store backend is postgres per the root config.toml (default localhost:45432, db enact_factory_dev, user/pw enact:enact). The daemon won't start without it.

   pg_isready -h localhost -p 45432

3. AzDo env vars present. All four are required for the sync service and the manual drain MCP tool. Missing vars throw a clear error.

   grep -E '^AZDO_(ORG|PROJECT|PAT|TEAM_ID)=' .env
   # expect 4 lines

4. Tests green. Sanity check the bridge before pointing it at production AzDo.

   pnpm test
   # expect: Tests <N> passed | 6 skipped, 0 failed

5. Operator installed. Enact Operator owns hooks, operator skills, and Codex-facing lifecycle behavior.

   enact-operator doctor

adapter: claude   # "claude" | "codex" | "responses" | "cursor" | "hermes" | "opencode"

Switch at runtime via Discord: !provider codex / !provider claude

Per-stage adapter overrides:

autonomous:
  defaultStages:
    coder:
      adapter: codex
      model: o4-mini
    critic:
      adapter: claude
      model: claude-sonnet-4-20250514

autonomous:
  defaultStages:
    coder:
      model: claude-haiku-4-5-20251001
      escalateModel: claude-sonnet-4-20250514
      escalateAfterIteration: 3
      timeoutMs: 1800000
    critic:
      model: claude-haiku-4-5-20251001
      timeoutMs: 600000
    tester:
      enabled: false
    documenter:
      enabled: false
    auditor:
      enabled: false

npm run service:install    # Build and install as system service
npm run service:start      # Start
npm run service:stop       # Stop
npm run service:restart    # Restart
npm run service:status     # Status and recent logs
npm run service:logs       # stdout (follow mode)
npm run service:errors     # stderr (follow mode)
npm run service:uninstall  # Uninstall

npm run build && npm start   # Production
npm run dev                  # Development (tsx watch)
docker compose up -d         # Docker

                         ┌──────────────────────────┐
                         │       Azdo API          │
                         │   (workItems, state, memory) │
                         └─────────────┬────────────┘
                                       │
                 ┌─────────────────────┼─────────────────────┐
                 │                     │                     │
                 v                     v                     v
  ┌──────────────────┐  ┌──────────────────┐  ┌──────────────────┐
  │ AutonomousRunner │  │  DecisionEngine  │  │  TaskScheduler   │
  │ (heartbeat loop) │─>│  (scope guard)   │─>│  (queue + slots) │
  └────────┬─────────┘  └──────────────────┘  └────────┬─────────┘
           │                                            │
           v                                            v
  ┌──────────────────────────────────────────────────────────────┐
  │                      PairPipeline                            │
  │  ┌────────┐   ┌──────────┐   ┌────────┐   ┌─────────────┐  │
  │  │ Executor │──>│ Reviewer │──>│ Tester │──>│ Documenter  │  │
  │  │(Adapter│<──│(Adapter) │   │(Adapter│   │  (Adapter)  │  │
  │  └───┬────┘   └──────────┘   └────────┘   └─────────────┘  │
  │      │  ↕ StuckDetector                                      │
  │  ┌───┴────────────────────────────────────────────────────┐  │
  │  │ Adapters: Claude | Codex | Responses | Cursor | Hermes | Opencode │  │
  │  └────────────────────────────────────────────────────────┘  │
  └──────────────────────────────────────────────────────────────┘
           │                     │                     │
           v                     v                     v
  ┌──────────────┐  ┌──────────────────┐  ┌──────────────────┐
  │  Discord Bot │  │  Memory (LanceDB │  │  Knowledge Graph │
  │  (commands)  │  │  + Xenova E5)    │  │  (code analysis) │
  └──────────────┘  └──────────────────┘  └────────┬─────────┘
                                                    │
                                           ┌────────┴─────────┐
                                           │  Code Registry   │
                                           │  (SQLite + FTS5) │
                                           │  + BS Detector   │
                                           └──────────────────┘

• Multi-Provider Adapters — Pluggable adapter system: Claude Code, Codex, Responses API, Cursor, Hermes, and Opencode
• Code Registry — SQLite-backed entity registry tracking every function/class/type across 8 languages, with complexity scoring, test mapping, and risk assessment
• WorkItem Store — PostgreSQL-backed work-item persistence and Kanban UI, with SQLite kept only as a legacy fallback path
• BS Detector — Built-in static analysis engine that detects bad code patterns (empty catch, hardcoded secrets, as any, etc.) with pipeline guard integration
• Autonomous Pipeline — Cron-driven heartbeat fetches Azdo workItems, runs Executor/Reviewer pair loops, and updates workItem state automatically
• Executor/Reviewer Pairs — Multi-iteration code generation with automated review, testing, and documentation stages
• Decision Engine — Scope validation, rate limiting, priority-based task selection, and workflow mapping
• Cognitive Memory — LanceDB vector store with Xenova/multilingual-e5-base embeddings for long-term recall across sessions
• Knowledge Graph — Static code analysis, dependency mapping, impact analysis, and file-level conflict detection across concurrent tasks
• Discord Control — Full command interface for monitoring, task dispatch, scheduling, provider switching, and pair session management
• Rich TUI Chat — Claude Code inspired terminal interface with tabs, streaming responses, and geek-themed loading messages
• Dynamic Scheduling — Cron-based job scheduler with Discord management commands
• PR Auto-Improvement — Monitors open PRs, auto-fixes CI failures, auto-resolves merge conflicts, and retries until all checks pass
• Long-Running Monitors — Track external processes (training jobs, batch tasks) and report completion
• Web Dashboard — Real-time pipeline stages, cost tracking, worktree status, and live logs on port 3847
• Pace Control — 5-hour rolling window task caps, per-project limits, turbo mode, exponential backoff on failures
• i18n — English and Korean locale support

Azdo (Todo/In Progress)
  → Fetch assigned workItems
  → DecisionEngine filters & prioritizes
  → Resolve project path via projectMapper
  → PairPipeline.run()
    → Executor generates code (Claude CLI)
    → Reviewer evaluates (APPROVE/REVISE/REJECT)
    → Loop up to N iterations
    → Optional: Tester → Documenter stages
  → Update Azdo workItem state (Done/Blocked)
  → Report to Discord
  → Save to cognitive memory

Hybrid retrieval: 0.55 × similarity + 0.20 × importance + 0.15 × recency + 0.10 × frequency

Memory types: belief · strategy · user_model · system_pattern · constraint

Background: decay, consolidation, contradiction detection, distillation.

src/
├── index.ts                 # Entry point
├── cli.ts                   # CLI entry point (run, exec, chat, init, validate, start)
├── cli/                     # CLI subcommand handlers
│   └── promptHandler.ts     # exec command: daemon submit, auto-start, polling
├── core/                    # Config, service lifecycle, types, event hub
├── adapters/                # CLI/provider adapters (claude, codex, responses), process registry
├── agents/                  # Executor, reviewer, tester, documenter, auditor
│   ├── pairPipeline.ts      # Executor → Reviewer → Tester → Documenter pipeline
│   ├── agentBus.ts          # Inter-agent message bus
│   └── cliStreamParser.ts   # Claude CLI output parser
├── orchestration/           # Decision engine, task parser, scheduler, workflow
├── automation/              # Autonomous runner, cron scheduler, PR processor
├── memory/                  # LanceDB + Xenova embeddings cognitive memory
├── knowledge/               # Code knowledge graph (scanner, analyzer, graph)
├── registry/                # Code entity registry, BS detector, entity scanner
├── workItems/                  # Postgres-first workItem tracker (GraphQL + Kanban UI)
├── discord/                 # Bot core, command handlers, pair session UI
├── azdo/                  # Azdo SDK wrapper, project updater
├── github/                  # GitHub CLI wrapper for CI monitoring
├── support/                 # Web dashboard, planner, rollback, git tools
├── locale/                  # i18n (en/ko) with prompt templates
└── __tests__/               # Vitest test suite

• Code Registry: enact-factory check --scan scans repo, registers 1000+ entities across 8 languages (TS, Python, Go, Rust, Java, C, C++, C#) with test mapping, complexity scoring, and risk assessment
• BS Detector: enact-factory check --bs — built-in static analysis for bad code patterns, pipeline guard integration
• Responses Adapter: Gateway-backed /v1/responses execution with env-based bearer auth
• Responses Status: Transport works today, but full agent parity is deferred until the loop semantics in docs/a_proposed/RESPONSES_AGENT_LOOP_SEMANTICS.md land
• WorkItem Tracker: PostgreSQL + GraphQL + Kanban web UI at :3847/workItems
• CLI: enact-factory check, enact-factory annotate commands

• enact-factory without arguments now launches TUI chat directly

• Security: patched lodash, picomatch, rollup, undici, yaml vulnerabilities

• Multi-project orchestration via Azdo ticket routing
• Standalone driver module extracted for reuse
• Autonomous runner hardening and multi-project orchestration
• Task-state rehydration from Azdo comments
• --verbose flag for detailed execution logging
• Codex adapter: dropped o-series model override

• Initial release
• Executor/Reviewer pair pipeline
• Claude Code CLI, Codex, Cursor-family adapters, and a Responses API seam
• Discord bot control
• Azdo integration
• LanceDB cognitive memory
• Web dashboard (port 3847)
• Rich TUI chat interface

This project is licensed under the proprietary Agent Development License (ADL).
See LICENSE for full terms.

© Enact Factory. All rights reserved.