Dark Factory

Autonomous coding pipeline — drop prompts in, get commits out.

One factory per project, sequential prompt processing, zero human intervention between spec and commit.

You (fast)                                    Factory (slow, unattended)
├── write prompt    ──→  prompts/              (inbox, passive)
├── ready to go     ──→  prompts/in-progress/  ┌─ watcher renames, processor executes
├── write prompt 2  ──→  prompts/              │  YOLO → commit → push* → tag*
├── move to queue   ──→  prompts/in-progress/  │  YOLO → commit → push* → tag*
└── go AFK                                     └─ idle, watching prompts/in-progress/
                                                    ↓
You come back                       ←── changes committed (push/tag depending on config)

* push happens when autoRelease: true; tag is additionally produced when CHANGELOG.md exists. See configuration.md and release-process.md.

• Go 1.26+ — to build dark-factory
• Docker — to run claude-yolo containers
• claude-yolo image — docker pull docker.io/bborbe/claude-yolo:v0.11.1
• ~/.claude-yolo/ — Claude Code config for the YOLO agent (see YOLO Container Setup)

go install github.com/bborbe/dark-factory@latest

Or build from source:

git clone https://github.com/bborbe/dark-factory.git
cd dark-factory
make install

# 1. Initialize project
cd ~/your-project
mkdir -p prompts/in-progress prompts/completed prompts/log
cat > .dark-factory.yaml <<'EOF'
pr: false
worktree: false
EOF

# 2. Write a prompt
cat > prompts/my-feature.md << 'EOF'
<summary>
- Adds a /health endpoint returning 200 OK
- No authentication required
- Existing endpoints unchanged
</summary>

<objective>
Add a health check endpoint for load balancer probes.
</objective>

<context>
Read CLAUDE.md for project conventions.
</context>

<requirements>
1. Add GET /health handler returning 200 with body "ok"
2. Register in the router
3. Add test
</requirements>

<constraints>
- Do NOT commit — dark-factory handles git
- Existing tests must still pass
</constraints>

<verification>
Run `make precommit` -- must pass.
</verification>
EOF

# 3. Approve and run
dark-factory prompt approve my-feature
dark-factory daemon

Dark-factory includes a Claude Code plugin for writing and auditing specs and prompts.

# Install
claude plugin marketplace add bborbe/dark-factory
claude plugin install dark-factory

# Update
claude plugin marketplace update dark-factory
claude plugin update dark-factory@dark-factory

Optional .dark-factory.yaml in project root:

pr: false                                            # create PRs (default: false)
worktree: false                                      # clone repo for isolation (default: false)
validationCommand: "make precommit"                  # shell command run after each prompt
validationPrompt: docs/dod.md                        # AI-judged quality criteria (file or inline)
containerImage: docker.io/bborbe/claude-yolo:v0.11.1  # YOLO Docker image
model: claude-sonnet-4-6                             # Claude model
claudeDir: ~/.claude-yolo                            # host claude config dir (default: ~/.claude-yolo)

User-level defaults in ~/.config/dark-factory/config.yaml (XDG; falls back to ~/.dark-factory/config.yaml) apply across every project that doesn't override them. Supports model, hideGit, autoRelease, dirtyFileThreshold, maxContainers, autoGeneratePrompts. Precedence: default ← global ← project ← CLI arg.

Spec→prompts can be auto or manual. Default: the daemon does NOT auto-generate prompts when a spec is approved — invoke /dark-factory:generate-prompts-for-spec <spec-path> by hand. Set autoGeneratePrompts: true in ~/.config/dark-factory/config.yaml (XDG), .dark-factory.yaml, or via --set autoGeneratePrompts=true to enable auto-generation. See docs/running.md § Two ways to generate prompts for tradeoffs.

Per-invocation CLI flags for run/daemon: --model NAME, --hide-git, --no-hide-git, --max-containers N, --skip-preflight, --auto-approve. Override yaml without editing files.

See docs/configuration.md for all config fields, the full layering precedence, and patterns like running on an existing manual worktree.

Dark-factory executes prompts inside a claude-yolo Docker container. The container needs a Claude Code config directory on the host, mounted into the container.

Quick setup (use bborbe's config):

git clone https://github.com/bborbe/claude-yolo.git ~/.claude-yolo
cd ~/.claude-yolo && claude login

Minimal setup (create your own): You need three files — OAuth credentials (claude login), settings.json, and a CLAUDE.md with agent instructions.

See docs/yolo-container-setup.md for both options in detail.

your-project/
├── .dark-factory.yaml        # config
├── prompts/                  # inbox (drop prompts here)
│   ├── in-progress/          # queued/executing
│   ├── completed/            # archived
│   └── log/                  # execution logs
├── specs/                    # spec inbox
│   ├── in-progress/          # approved specs
│   └── completed/            # done specs
└── scenarios/                # end-to-end verification

• YOLO has NO git access — all git ops happen on the host
• Sequential processing — prompts execute in number order
• Frontmatter = state — no database
• Fresh context per prompt — no context rot
• Stop on failure — never skip failed prompts
• Instance lock — one dark-factory per project

BSD-2-Clause