Home
Softono
Auto-agent-factory

Auto-agent-factory

Open source MIT JavaScript
30
Stars
2
Forks
1
Issues
0
Watchers
1 week
Last Commit

About Auto-agent-factory

A production-ready toolkit to accelerate and automate the end-to-end lifecycle of AI Agent development.

Platforms

Web Self-hosted

Languages

JavaScript

Links

Auto Agent Factory

A local-first AI Agent governance toolkit for goal-driven n8n workflows.

Auto Agent Factory helps developers prototype AI Agent workflows that are bounded, testable, auditable, and human-reviewable before any real write action is enabled. It turns an agent request into a structured control loop: define a goal, define success criteria, route execution safely, evaluate evidence, record an audit trail, and require human sign-off when risk appears.

This is not another “prompt goes in, automation happens” demo. It is a workflow governance skeleton for people who care about safety boundaries, reproducibility, and reviewable Agent execution.

Language: English | 简体中文

n8n workflow Node.js local-first mock-first dry-run human review status license

Why this exists

AI Agent systems fail less because the model cannot produce text, and more because the surrounding control plane is missing:

  • unclear goals
  • vague success criteria
  • no bounded execution loop
  • no evaluator contract
  • no error recovery path
  • no human approval boundary
  • no audit trail that is safe to review
  • no reproducible local demo path

Auto Agent Factory treats these as product and engineering problems, not prompt-writing problems.

What you can do with it today

This repository currently supports three practical usage paths:

Path Requires API key? Requires n8n runtime? What it proves
Local demo path No No replay a sanitized review cycle locally from sample data
n8n workflow path No Yes import and validate the GoalDriven workflow skeleton in n8n
Real provider sandbox path Yes, your own key in n8n Credentials Yes run a read-only provider sandbox that still returns needs_review

Current capabilities include:

  • four importable n8n workflow JSON files
  • mock, dry-run, real-readonly stub, and read-only provider sandbox modes
  • criteria checker alignment with criterion-indexed evidence
  • high-risk approval gate and forbidden action rejection
  • sanitized audit record schema and sanitizer
  • audit review report generator
  • human sign-off review package generator
  • dev-only human decision ledger
  • local end-to-end review cycle replay
  • draft-only action handoff generator for Codex, GitHub Issue, commit message, and test commands
  • verified real DeepSeek V4 Pro read-only provider contract with review-oriented output
  • verified V0.17 recovery policy for bounded retry / stop / review decisions from the Error Handler
  • verified V0.18 Human Approval Console Lite for local recovery and high-risk decision review
  • verified V0.19 draft-only Codex/GitHub handoff generation from human decision records
  • verified V1.0 local production workflow readiness runbook
  • one-command local demo

Current capability matrix

Capability Status Local check
Version and roadmap clarity V0.14 closeout docs/MILESTONE_SUMMARY.md
Safe local demo Supported npm run demo:local
Workflow JSON validation Supported npm run workflow:validate:all
Audit report Supported npm run audit:report
Human sign-off review Supported npm run audit:signoff
Decision ledger replay Dev-only npm run audit:cycle:replay
Action drafts V0.19 verified draft-only handoff npm run action:draft
Local n8n runtime health Offline/online checks npm run runtime:health:offline
DeepSeek provider run V0.16 real read-only contract verified npm run sandbox:deepseek:readonly
Recovery policy V0.17 runtime verified npm run recovery:policy
Human approval console V0.18 verified local console npm run approval:console
V1.0 readiness runbook Verified repo-side/local path docs/V1.0_LOCAL_PRODUCTION_WORKFLOW_READINESS_RUNBOOK.md
Production write execution Not enabled Safety boundary

Current stage: V1.0 Local Production Workflow Readiness Verified. The V1.0 runbook connects local runtime health, DeepSeek read-only execution, recovery policy, approval console, decision ledger, and action drafts without enabling automatic retry or workflow write actions.

Quick start

Install dependencies:

npm install

Run the safest local demo path:

npm run demo:local

That command is repo-side only. It does not connect to n8n runtime, does not call a real provider, and does not require an API key. It may create dev-only artifacts under .local-audit/, which is ignored by Git.

Run the core validation path:

npm test
npm run workflow:validate:all
npm run workflow:dry-run
npm run import:check

Generate local review artifacts from sanitized sample records:

npm run audit:report
npm run audit:signoff
npm run audit:cycle:replay

Generate a draft-only handoff package for Codex, GitHub Issue, commit message, and test commands:

npm run action:draft

Review a recovery decision in the local approval console:

npm run approval:console

Check local runtime readiness without requiring n8n to be running:

npm run runtime:health:offline

Prepare a DeepSeek read-only sandbox payload without sending it:

npm run sandbox:deepseek:readonly

Architecture snapshot

Layer Purpose Current proof point
GoalDriven Master intake, payload validation, safety routing, executor/checker orchestration importable inactive workflow JSON
Agent Task Executor one bounded execution iteration mock, dry-run, real-readonly, and read-only provider sandbox paths
Criteria Checker evaluate evidence against criteria criterion-indexed evidence contract validated
Error Handler capture failed workflow executions n8n Error Trigger workflow implemented
Safety boundary prevent unsafe automation high-risk approval gate and forbidden action rejection
Audit / sign-off human-readable local review loop sanitized record → report → sign-off → decision ledger → summary
flowchart TD
    A["Goal Request\ngoal + criteria + limits"] --> B["[GoalDriven] 01 Master"]
    B --> C["Payload Validator"]
    C --> D{"Safety Boundary\napproval / forbidden checks"}
    D -->|invalid / blocked| R["Blocked Response"]
    D -->|validated| E["Task Initializer\nrun_id + task_id"]
    E --> F["Agent Dispatcher"]
    F --> G["[GoalDriven] 02 Agent Task Executor"]
    G --> H{"Mode Router"}
    H -->|mock| H1["Mock Adapter"]
    H -->|dry-run| H2["Dry-run Adapter"]
    H -->|real-readonly| H3["Read-only Provider Path"]
    H1 --> I["Result Normalizer\nagent_result"]
    H2 --> I
    H3 --> I
    I --> J["[GoalDriven] 03 Criteria Checker"]
    J --> K{"Criteria Result"}
    K -->|met| L["Final Reporter"]
    K -->|not met| M["Next Action / Stop"]
    B -. execution failure .-> O["[GoalDriven] 04 Error Handler"]
    G -. execution failure .-> O
    J -. execution failure .-> O

Import into n8n

Import the workflows in this order:

  1. [GoalDriven] 02 Agent Task Executorworkflows/agent_task_executor.workflow.json
  2. [GoalDriven] 03 Criteria Checkerworkflows/criteria_checker.workflow.json
  3. [GoalDriven] 04 Error Handlerworkflows/error_handler.workflow.json
  4. [GoalDriven] 01 Masterworkflows/goal_driven_master.workflow.json

After importing, verify sub-workflow bindings manually. Cross-instance n8n imports may require reselecting the Executor, Checker, and Error Handler workflows.

Useful docs:

Real provider sandbox

The real provider path is intentionally read-only. It is designed to generate structured summary, intended actions, evidence, and risk context. It must still return review-oriented output and keep human approval boundaries intact.

To try this path, use your own local n8n instance and your own provider key stored in n8n Credentials. Do not put provider keys in workflow JSON, docs, examples, prompts, or Git.

See:

Safety boundaries

Auto Agent Factory is deliberately conservative:

  • workflows are exported inactive by default
  • no API keys in workflow JSON
  • no .env files committed
  • no .local-audit/ artifacts committed
  • no credential plaintext in docs or examples
  • no raw provider responses stored in repo fixtures
  • no full prompt/message payloads stored in audit records
  • no shell execution
  • no Git modification
  • no file-write workflow action
  • no external write action
  • no production database or hosted user system
  • no production autonomous Agent execution

Before sharing changes, check that the diff does not contain:

Bearer <secret>
real API keys
.env
credential plaintext
.local-audit/
provider raw response
full prompt / messages

What this is not

This project is not:

  • a SaaS product
  • a multi-user production approval system
  • a production autonomous coding agent
  • a replacement for n8n security configuration
  • a workflow that can safely write to files, Git, shells, or external systems by default
  • a place to store provider keys or private user data

It is an open-source, local-first toolkit for learning, validating, and extending safer Agent workflow patterns.

Repository structure

workflows/              n8n workflow JSON exports
docs/                   architecture, runbooks, safety docs, release notes
examples/               safe sample payloads and sanitized fixtures
src/schema/             JSON schemas for workflow and audit contracts
src/utils/              validation, scoring, sanitizer, report utilities
scripts/                validation, import checks, demo and audit CLIs
tests/                  Node test suite
.local-audit/           dev-only generated artifacts, ignored by Git

Documentation map

Start here:

Open-source process:

Roadmap

Near-term:

  • stabilize v1.0 release-candidate docs and local demo path
  • implement V0.17 Recovery Policy for bounded retry / stop / review decisions
  • keep real provider usage read-only first
  • improve screenshots or diagrams only when they reflect real repository state
  • expand evaluator quality tests for ambiguous evidence

Later:

  • optional provider adapters behind the same agent_result contract
  • Codex / coding-agent executor adapter behind explicit human approval
  • production-grade persistence design, if needed
  • hosted dashboard or approval UI, if the project grows beyond local-first usage
  • multi-agent task routing and RAG / knowledge-base adapters

Planned items are not current capabilities.

License

MIT. See LICENSE.