forgecraft 1.0.0 → 1.2.0

package/README.md

@@ -1,8 +1,8 @@
 <p align="center">
-  <img src="https://img.shields.io/npm/v/forgeai?style=flat-square&color=000" alt="npm version" />
+  <img src="https://img.shields.io/npm/v/forgecraft?style=flat-square&color=000" alt="npm version" />
   <img src="https://img.shields.io/badge/node-%3E%3D18-000?style=flat-square" alt="node version" />
   <img src="https://img.shields.io/github/license/joeljohn159/forgeai?style=flat-square&color=000" alt="license" />
-  <img src="https://img.shields.io/badge/frameworks-Next.js%20%7C%20React%20%7C%20Django-000?style=flat-square" alt="frameworks" />
+  <img src="https://img.shields.io/badge/frameworks-Next.js%20%7C%20React%20%7C%20Django%20%7C%20Any-000?style=flat-square" alt="frameworks" />
 </p>
 
 <h1 align="center">ForgeAI</h1>
@@ -97,24 +97,33 @@ Each phase has a clear input, a clear output, and a gate between them. Stories t
 # Prerequisites: Node 18+, Claude Code CLI (logged in)
 
 # Install globally
-npm install -g forgeai
+npm install -g forgecraft
 
 # Create a new project directory
 mkdir my-app && cd my-app
 
-# Initialize (choose Next.js, React+Vite, or Django)
+# Initialize (choose Next.js, React+Vite, Django, or any stack)
 forge init
 
 # Build something
 forge auto "a task management app with projects, due dates, and team assignment"
 
+# Full auto — skip all prompts
+forge auto "an API with Express and MongoDB" --yes
+
+# Attach references — drag & drop files into the terminal
+forge auto "build this app" /path/to/mockup.png /path/to/spec.pdf
+#  Attachments:
+#    [Image1] mockup.png
+#    [Document1] spec.pdf
+
 # Start the dev server
 forge start
 
 # If interrupted, resume where you left off
 forge resume
 
-# Fix a bug (supports screenshots)
+# Fix a bug (drag & drop screenshots or use --image)
 forge fix "the sidebar overlaps on mobile" --image screenshot.png
 
 # Push to GitHub manually (auto-push happens after forge auto)
@@ -150,6 +159,32 @@ Type a message at any point during the build. It gets queued and processed at th
 "what's the database schema?"         → Orchestrator answers directly
 ```
 
+### Drag & Drop Attachments
+Drag files directly into the terminal to attach mockups, specs, or screenshots. Forge detects the file paths, classifies them, and passes them to the agents as context.
+
+```bash
+# Drag & drop images and documents right into your prompt
+forge auto "build this landing page" /Users/me/mockup.png /Users/me/requirements.pdf
+
+  Attachments:
+    [Image1] mockup.png
+    [Document1] requirements.pdf
+
+# Also works with forge fix
+forge fix "match this design" /Users/me/screenshot.png
+```
+
+Supports images (`.png`, `.jpg`, `.svg`, `.webp`), documents (`.pdf`, `.doc`, `.txt`, `.md`, `.csv`, `.json`, `.yaml`), and design files (`.figma`, `.sketch`). Files are copied to `.forge/attachments/` so agents can reference them.
+
+### Zero-Prompt Mode (`--yes`)
+Skip every confirmation dialog — Claude Code permission prompts, review gates, resume confirmations. Fully hands-free.
+
+```bash
+forge auto "a blog with auth" --yes
+forge auto "a dashboard" -y --skip-design --quiet
+forge resume -y
+```
+
 ### Screenshot-Based Bug Fixing
 Pass a screenshot to `forge fix` and Claude reads the image to understand the visual issue:
 
@@ -183,9 +218,18 @@ ForgeAI isn't locked to one framework. Each adapter knows how to scaffold, build
 | **Next.js** | TypeScript | Storybook | Stable |
 | **React + Vite** | TypeScript | Storybook | Stable |
 | **Django** | Python | Skipped | Stable |
-| Flutter | Dart | — | Planned |
+| **Any Stack** | Auto-detect | Skipped | Stable |
 
-Worker prompts automatically adapt to the framework — Next.js gets App Router instructions, Vite gets SPA routing, Django gets migration commands.
+The **"Other"** option in `forge init` enables a generic adapter that works with any tech stack — Express, Vue, Svelte, Go, Rust, FastAPI, Flutter, Rails, and more. The agent auto-detects your project's language, package manager, build commands, and file structure from existing config files. If starting from scratch, it scaffolds using the standard tooling for the detected stack.
+
+```bash
+# Works with anything
+forge auto "a REST API with Express, Prisma, and PostgreSQL"
+forge auto "a CLI tool in Rust that converts images to WebP"
+forge auto "a FastAPI backend with SQLAlchemy and JWT auth"
+```
+
+Worker prompts automatically adapt to the framework — Next.js gets App Router instructions, Vite gets SPA routing, Django gets migration commands, and generic projects get smart auto-detection.
 
 ### Sprint Resume
 If a build gets interrupted (auth expires, network drops, you close the terminal), your progress is saved. Run `forge resume` to pick up exactly where you left off. Blocked stories can be retried.
@@ -201,10 +245,12 @@ Pass `--deploy` and ForgeAI configures `next.config` for static export and creat
 
 ```bash
 forge auto "description"              # Full autonomous pipeline (auto-pushes to GitHub)
+forge auto "description" --yes        # Skip all prompts (fully hands-free)
 forge auto "description" --skip-design  # Skip Storybook previews (faster)
 forge auto "description" --deploy     # Add GitHub Pages deployment
 forge auto "description" --mute       # No notification sounds
 forge auto "description" --quiet      # Spinners only, no tool details
+forge auto "desc" file.png spec.pdf   # Attach reference files (drag & drop)
 ```
 
 ### Step-by-Step Mode
@@ -286,6 +332,7 @@ src/
 │   │   ├── nextjs.ts                 # Next.js adapter
 │   │   ├── react-vite.ts             # React + Vite adapter
 │   │   ├── django.ts                 # Django adapter
+│   │   ├── generic.ts                # Generic adapter (any tech stack)
 │   │   └── index.ts                  # Adapter registry + factory
 │   │
 │   ├── git/
@@ -295,6 +342,7 @@ src/
 │   │   └── index.ts                  # GitHub Issues sync (via gh CLI)
 │   │
 │   └── utils/
+│       ├── attachments.ts            # Drag & drop file attachment parser
 │       ├── config.ts                 # Config validation
 │       └── sound.ts                  # Notification sounds (macOS/Linux/fallback)
 │
@@ -379,9 +427,10 @@ After `forge init`, your `forge.config.json` controls:
 | Git strategy | Manual | Manual | Manual | **Auto commits + tags + push** |
 | Parallelism | N/A | N/A | N/A | **Dependency-grouped parallel** |
 | Human oversight | Full control | None | Approve/reject | **Stage gates + live feedback** |
-| Bug fix with screenshots | N/A | N/A | N/A | **forge fix --image** |
+| Bug fix with screenshots | N/A | N/A | N/A | **forge fix --image + drag & drop** |
 | SEO & assets | You remember | You remember | You remember | **Built-in defaults** |
-| Multi-framework | N/A | Any | Any | **Next.js, React, Django** |
+| Multi-framework | N/A | Any | Any | **Next.js, React, Django, Any** |
+| File attachments | N/A | N/A | N/A | **Drag & drop mockups/specs** |
 | Resume on failure | Start over | N/A | N/A | **Auto-save + resume** |
 
 <br/>
@@ -394,7 +443,7 @@ After `forge init`, your `forge.config.json` controls:
 
 **v0.3** — React + Vite and Django adapters, `forge map`, `forge resume`
 
-**v1.0** — Current
+**v1.0** — Initial Release
 - 21 CLI commands covering the full development lifecycle
 - 3 framework adapters (Next.js, React + Vite, Django)
 - Framework-aware prompts via pluggable adapter system
@@ -406,10 +455,13 @@ After `forge init`, your `forge.config.json` controls:
 - Config validation with actionable error messages
 - Token expiry handling with auto-retry
 
-**v1.1** — Next Up
-- **Flutter adapter** — Dart support with widget-based design previews
-- **Vue.js / Nuxt adapter** — Vue 3 + Composition API + Nuxt 3 SSR support
-- **Svelte / SvelteKit adapter** — Svelte 5 with runes and SvelteKit routing
+**v1.1** — Current
+- **Any tech stack support** — generic adapter auto-detects language, package manager, build commands, and project structure. Works with Express, Vue, Svelte, Go, Rust, FastAPI, Rails, and more.
+- **`--yes` flag** — skip all confirmation prompts for fully hands-free operation
+- **Drag & drop attachments** — attach mockups, screenshots, specs, and design files by dragging into the terminal. Supports images, PDFs, docs, and design files.
+- Published as `forgecraft` on npm
+
+**v1.2** — Next Up
 - **Test generation phase** — auto-generate unit and integration tests after build (Vitest, pytest, Flutter test)
 - **Custom adapter plugin API** — drop a JS file in `.forge/adapters/` to add your own framework
 

package/dist/{chunk-2HFEPXBV.js → chunk-P5CLBIGQ.js}

@@ -220,11 +220,68 @@ requirements.txt             # Python dependencies
 `.trim()
 };
 
+// src/core/adapters/generic.ts
+var genericAdapter = {
+  id: "generic",
+  name: "Custom Stack",
+  language: "typescript",
+  // default, but prompts tell the agent to auto-detect
+  scaffoldCommands: [],
+  buildCommand: "AUTO_DETECT",
+  lintCommand: "AUTO_DETECT",
+  typecheckCommand: "AUTO_DETECT",
+  devCommand: "npm run dev",
+  devPort: 3e3,
+  designSupport: false,
+  packageManager: "npm",
+  requiredFiles: [],
+  buildPromptAdditions: `
+CUSTOM TECH STACK \u2014 IMPORTANT:
+This project uses a tech stack chosen by the user. You MUST auto-detect everything.
+
+STEP 1 \u2014 DETECT THE STACK:
+Before writing ANY code, read these files (whichever exist):
+- package.json (Node.js/JS/TS projects)
+- requirements.txt / pyproject.toml / Pipfile (Python projects)
+- go.mod (Go projects)
+- Cargo.toml (Rust projects)
+- pom.xml / build.gradle (Java/Kotlin projects)
+- pubspec.yaml (Flutter/Dart projects)
+- Gemfile (Ruby projects)
+- composer.json (PHP projects)
+- Any existing source files to understand patterns
+
+STEP 2 \u2014 FOLLOW EXISTING CONVENTIONS:
+- If the project already has code, match its style exactly (naming, file structure, patterns)
+- If starting from scratch, use the standard project structure for the detected tech stack
+- Use the package manager the project already uses (npm, yarn, pnpm, pip, poetry, cargo, go, etc.)
+
+STEP 3 \u2014 BUILD VERIFICATION:
+- Detect the correct build/lint/test commands from the project config
+- For Node.js: check package.json "scripts" for build, lint, typecheck commands
+- For Python: use pytest, flake8/ruff, mypy if configured
+- For Go: use go build, go vet, go test
+- For Rust: use cargo build, cargo clippy, cargo test
+- If no build script exists, skip the build step \u2014 do NOT fail
+- If a command does not exist or is not configured, skip it gracefully
+
+STEP 4 \u2014 SCAFFOLDING:
+- If the project directory is empty, scaffold the project using the standard tooling for the stack
+  (e.g., npm init, cargo init, go mod init, django-admin startproject, etc.)
+- Install dependencies after scaffolding
+`.trim(),
+  designPromptAdditions: "",
+  fileStructure: `
+(auto-detected \u2014 read the project's existing files to determine structure)
+`.trim()
+};
+
 // src/core/adapters/index.ts
 var adapters = {
   nextjs: nextjsAdapter,
   react: reactViteAdapter,
-  django: djangoAdapter
+  django: djangoAdapter,
+  generic: genericAdapter
 };
 function getAdapter(framework) {
   const adapter = adapters[framework];
@@ -362,12 +419,14 @@ var Orchestrator = class {
   // ── Plan Generation ───────────────────────────────────────
   async generatePlan(description) {
     const adapter = getAdapter(this.config.framework);
+    const isGeneric = adapter.id === "generic";
+    const frameworkHint = isGeneric ? `Tech stack: Detect from the user's description below. The user may specify their own framework, language, and tools.` : `Framework: ${adapter.name} (${this.config.framework})
+      Language: ${adapter.language}`;
     const prompt = `
       The user wants to build the following application:
       "${description}"
 
-      Framework: ${adapter.name} (${this.config.framework})
-      Language: ${adapter.language}
+      ${frameworkHint}
       Design support: ${adapter.designSupport ? "yes (Storybook)" : "no"}
 
       Break this down into epics and stories. Each story should be:
@@ -522,11 +581,31 @@ var Orchestrator = class {
     `;
   }
   craftBuildPrompt(story, context, adapter) {
+    const isGeneric = adapter.id === "generic";
     const designRef = context.designMeta ? `
 Approved design: Follow the design in stories/${story.id}.stories.tsx exactly.` : "";
     const existingRef = context.existingFiles?.length ? `
 Existing files to reference for patterns:
 ${context.existingFiles.map((f) => `  - ${f}`).join("\n")}` : "";
+    const verifySteps = isGeneric ? `
+      After writing code:
+      1. Detect the project's build/lint/typecheck commands from its config files (package.json scripts, Makefile, pyproject.toml, etc.)
+      2. Run whichever commands exist \u2014 skip any that aren't configured
+      3. Fix any errors before finishing
+      ` : `
+      After writing code:
+      1. Run: ${adapter.buildCommand} (fix any errors)
+      2. Run: ${adapter.lintCommand} (fix any warnings)
+      3. Run: ${adapter.typecheckCommand} (fix any type errors)
+      `;
+    const structureRef = isGeneric ? `
+      Project structure:
+      Read the existing project files to understand the structure.
+      If starting from scratch, use the standard conventions for this tech stack.
+      ` : `
+      Expected project structure:
+      ${adapter.fileStructure}
+      `;
     return `
       Implement: "${story.title}"
 
@@ -535,8 +614,7 @@ ${context.existingFiles.map((f) => `  - ${f}`).join("\n")}` : "";
       ${designRef}
       ${existingRef}
 
-      Expected project structure:
-      ${adapter.fileStructure}
+      ${structureRef}
 
       Technical requirements:
       - Follow existing code patterns in the project
@@ -544,16 +622,18 @@ ${context.existingFiles.map((f) => `  - ${f}`).join("\n")}` : "";
       - Proper error handling
       - Responsive design (mobile-first)
 
-      After writing code:
-      1. Run: ${adapter.buildCommand} (fix any errors)
-      2. Run: ${adapter.lintCommand} (fix any warnings)
-      3. Run: ${adapter.typecheckCommand} (fix any type errors)
+      ${verifySteps}
 
       If any command fails, read the error, fix it, and re-run.
       Do NOT leave broken code.
     `;
   }
   craftReviewPrompt(story, context, adapter) {
+    const isGeneric = adapter.id === "generic";
+    const runCmds = isGeneric ? `Run the project's build/lint/test commands (detect from config files). Skip any that aren't configured.` : `Run:
+      - ${adapter.buildCommand}
+      - ${adapter.lintCommand}
+      - ${adapter.typecheckCommand}`;
     return `
       Review the code for: "${story.title}"
 
@@ -568,10 +648,7 @@ ${context.existingFiles.map((f) => `  - ${f}`).join("\n")}` : "";
       6. Accessibility \u2014 semantic HTML, ARIA labels
       7. No debug logs, no commented-out code, no TODOs
 
-      Run:
-      - ${adapter.buildCommand}
-      - ${adapter.lintCommand}
-      - ${adapter.typecheckCommand}
+      ${runCmds}
 
       If you find issues:
       - Minor (formatting, missing type): fix them directly
@@ -581,12 +658,14 @@ ${context.existingFiles.map((f) => `  - ${f}`).join("\n")}` : "";
     `;
   }
   craftFixPrompt(story, context, adapter) {
+    const isGeneric = adapter.id === "generic";
+    const verifyCmds = isGeneric ? "After fixing, run the project's build/test commands to verify (detect from config files)." : `After fixing, run ${adapter.buildCommand} and ${adapter.typecheckCommand} to verify.`;
     return `
       Fix an issue in: "${story.title}"
       Framework: ${adapter.name}
 
       Make the smallest possible change. Do not refactor.
-      After fixing, run ${adapter.buildCommand} and ${adapter.typecheckCommand} to verify.
+      ${verifyCmds}
     `;
   }
   // ── SDK Query Helper ──────────────────────────────────────
@@ -699,9 +778,20 @@ ${additions}
 function getBuildPrompt(framework) {
   const adapter = framework ? getAdapter(framework) : null;
   const additions = adapter?.buildPromptAdditions || "";
-  const buildCmd = adapter?.buildCommand || "npm run build";
-  const lintCmd = adapter?.lintCommand || "npm run lint";
-  const typecheckCmd = adapter?.typecheckCommand || "npx tsc --noEmit";
+  const isGeneric = adapter?.id === "generic";
+  const verifyBlock = isGeneric ? `
+AFTER WRITING CODE:
+1. Detect the project's build/lint/typecheck/test commands from its config files
+   (package.json scripts, Makefile, pyproject.toml, Cargo.toml, etc.)
+2. Run whichever commands exist \u2014 skip any that aren't configured
+3. Fix ALL errors before proceeding
+4. If no build system is configured, verify the code is syntactically valid
+` : `
+AFTER WRITING CODE:
+1. Run: ${adapter?.buildCommand || "npm run build"} \u2014 fix ALL errors before proceeding
+2. Run: ${adapter?.lintCommand || "npm run lint"} \u2014 fix warnings
+3. Run: ${adapter?.typecheckCommand || "npx tsc --noEmit"} \u2014 fix type errors
+`;
   return `
 You are a senior fullstack developer working within the Forge development framework.
 Your job is to implement features based on approved designs and story requirements.
@@ -715,10 +805,7 @@ CODING STANDARDS:
 
 ${additions}
 
-AFTER WRITING CODE:
-1. Run: ${buildCmd} \u2014 fix ALL errors before proceeding
-2. Run: ${lintCmd} \u2014 fix warnings
-3. Run: ${typecheckCmd} \u2014 fix type errors
+${verifyBlock}
 
 If any command fails:
 - Read the full error output
@@ -736,10 +823,21 @@ GIT:
 }
 function getReviewPrompt(framework) {
   const adapter = framework ? getAdapter(framework) : null;
-  const buildCmd = adapter?.buildCommand || "npm run build";
-  const lintCmd = adapter?.lintCommand || "npm run lint";
-  const typecheckCmd = adapter?.typecheckCommand || "npx tsc --noEmit";
+  const isGeneric = adapter?.id === "generic";
   const lang = adapter?.language || "typescript";
+  const langCheck = isGeneric ? "3. Code quality \u2014 follows the language's best practices and idioms" : lang === "typescript" ? "3. TypeScript strict compliance (no any, no ts-ignore, no ts-expect-error)" : "3. Python code quality (no bare except, proper type hints where used)";
+  const runBlock = isGeneric ? `
+RUN THESE COMMANDS:
+- Detect build/lint/test commands from the project's config files (package.json, Makefile, pyproject.toml, Cargo.toml, etc.)
+- Run whichever exist \u2014 skip any that aren't configured
+- Run tests if a test runner is configured
+` : `
+RUN THESE COMMANDS:
+- ${adapter?.buildCommand || "npm run build"}
+- ${adapter?.lintCommand || "npm run lint"}
+- ${adapter?.typecheckCommand || "npx tsc --noEmit"}
+- npm run test (if tests exist)
+`;
   return `
 You are a QA engineer reviewing code within the Forge development framework.
 Your job is to catch issues before code is merged to main.
@@ -747,7 +845,7 @@ Your job is to catch issues before code is merged to main.
 REVIEW CHECKLIST:
 1. Implementation matches the story description
 2. If design was approved \u2014 implementation matches the design
-${lang === "typescript" ? "3. TypeScript strict compliance (no any, no ts-ignore, no ts-expect-error)" : "3. Python code quality (no bare except, proper type hints where used)"}
+${langCheck}
 4. Responsive design works at 375px, 768px, 1440px
 5. Error handling \u2014 what happens when things fail?
 6. Loading states \u2014 what does the user see while waiting?
@@ -758,11 +856,7 @@ ${lang === "typescript" ? "3. TypeScript strict compliance (no any, no ts-ignore
 11. No TODO/FIXME/HACK comments left behind
 12. No hardcoded values that should be configurable
 
-RUN THESE COMMANDS:
-- ${buildCmd}
-- ${lintCmd}
-- ${typecheckCmd}
-- npm run test (if tests exist)
+${runBlock}
 
 ISSUE CLASSIFICATION:
 - MINOR: formatting, missing type annotation, unused import
@@ -781,8 +875,18 @@ Provide a structured review summary:
 }
 function getFixPrompt(framework) {
   const adapter = framework ? getAdapter(framework) : null;
-  const buildCmd = adapter?.buildCommand || "npm run build";
-  const typecheckCmd = adapter?.typecheckCommand || "npx tsc --noEmit";
+  const isGeneric = adapter?.id === "generic";
+  const verifyBlock = isGeneric ? `
+AFTER EVERY FIX:
+1. Detect the project's build/test commands from its config files
+2. Run whichever exist to verify nothing is broken
+3. Verify the fix works
+` : `
+AFTER EVERY FIX:
+1. Run: ${adapter?.buildCommand || "npm run build"}
+2. Run: ${adapter?.typecheckCommand || "npx tsc --noEmit"}
+3. Verify the fix works
+`;
   return `
 You are a debugger and problem solver within the Forge development framework.
 Your job is to make targeted fixes without breaking anything else.
@@ -805,10 +909,7 @@ FOR BUG FIXES:
 - Check if the same bug pattern exists elsewhere
 - Verify the fix by running the relevant command
 
-AFTER EVERY FIX:
-1. Run: ${buildCmd}
-2. Run: ${typecheckCmd}
-3. Verify the fix works
+${verifyBlock}
 
 If your fix introduces new errors, undo it and try a different approach.
 `.trim();
@@ -911,6 +1012,9 @@ var Worker = class {
       cwd: workingDir,
       maxTurns: MODE_MAX_TURNS[mode]
     };
+    if (this.sandboxOpts.yes && !this.sandboxOpts.sandbox) {
+      sdkOptions.permissionMode = "bypassPermissions";
+    }
     if (this.sandboxOpts.sandbox) {
       sdkOptions.permissionMode = "bypassPermissions";
       sdkOptions.sandbox = {
@@ -1904,6 +2008,120 @@ var GitHubSync = class {
   }
 };
 
+// src/core/utils/attachments.ts
+import fs3 from "fs";
+import path3 from "path";
+var IMAGE_EXTS = /* @__PURE__ */ new Set([
+  ".png",
+  ".jpg",
+  ".jpeg",
+  ".gif",
+  ".webp",
+  ".svg",
+  ".bmp",
+  ".ico",
+  ".tiff",
+  ".avif"
+]);
+var DOCUMENT_EXTS = /* @__PURE__ */ new Set([
+  ".pdf",
+  ".doc",
+  ".docx",
+  ".txt",
+  ".md",
+  ".csv",
+  ".xls",
+  ".xlsx",
+  ".ppt",
+  ".pptx",
+  ".rtf",
+  ".html",
+  ".json",
+  ".yaml",
+  ".yml",
+  ".xml",
+  ".figma",
+  ".sketch",
+  ".xd"
+]);
+var PATH_PATTERN = /(?:"([^"]+\.[\w]+)")|(?:'([^']+\.[\w]+)')|(?:((?:\/|[A-Z]:\\)(?:[^\s,;]|\\[ ])+\.[\w]+))/g;
+function parseAttachments(input) {
+  const attachments = [];
+  let imageCount = 0;
+  let docCount = 0;
+  let cleaned = input.replace(PATH_PATTERN, (match, quoted, singleQuoted, raw) => {
+    const filePath = (quoted || singleQuoted || raw || "").replace(/\\ /g, " ").trim();
+    if (!filePath) return match;
+    const resolved = path3.resolve(filePath);
+    if (!fs3.existsSync(resolved)) return match;
+    const ext = path3.extname(resolved).toLowerCase();
+    const fileName = path3.basename(resolved);
+    let type;
+    let label;
+    if (IMAGE_EXTS.has(ext)) {
+      imageCount++;
+      type = "image";
+      label = `[Image${imageCount}]`;
+    } else if (DOCUMENT_EXTS.has(ext)) {
+      docCount++;
+      type = "document";
+      label = `[Document${docCount}]`;
+    } else {
+      docCount++;
+      type = "document";
+      label = `[Document${docCount}]`;
+    }
+    attachments.push({
+      label,
+      originalPath: match,
+      resolvedPath: resolved,
+      type,
+      ext,
+      fileName
+    });
+    return label;
+  });
+  cleaned = cleaned.replace(/\s{2,}/g, " ").trim();
+  return { description: cleaned, attachments };
+}
+function stageAttachments(attachments) {
+  if (attachments.length === 0) return [];
+  const attachDir = path3.join(process.cwd(), ".forge", "attachments");
+  fs3.mkdirSync(attachDir, { recursive: true });
+  const stagedPaths = [];
+  for (const att of attachments) {
+    const stagedName = att.label.replace(/[\[\]]/g, "").toLowerCase() + att.ext;
+    const dest = path3.join(attachDir, stagedName);
+    try {
+      fs3.copyFileSync(att.resolvedPath, dest);
+      stagedPaths.push(dest);
+    } catch {
+    }
+  }
+  return stagedPaths;
+}
+function formatAttachmentList(attachments) {
+  if (attachments.length === 0) return "";
+  return attachments.map((a) => `    ${a.label} ${a.fileName}`).join("\n");
+}
+function buildAttachmentPrompt(attachments) {
+  if (attachments.length === 0) return "";
+  const lines = attachments.map((a) => {
+    const relPath = path3.relative(process.cwd(), a.resolvedPath);
+    if (a.type === "image") {
+      return `- ${a.label}: Image file at ${relPath} \u2014 read this file to see the visual reference`;
+    }
+    return `- ${a.label}: Document at ${relPath} \u2014 read this file for requirements/specs`;
+  });
+  return `
+ATTACHMENTS (provided by the user):
+${lines.join("\n")}
+
+Use these attachments as reference material. For images, match the visual style/layout.
+For documents, extract requirements and specifications from them.
+`;
+}
+
 // src/core/pipeline/auto.ts
 var AutoPipeline = class {
   orchestrator;
@@ -1927,6 +2145,7 @@ var AutoPipeline = class {
       config,
       {
         sandbox: options.sandbox ?? true,
+        yes: options.yes ?? false,
         workingDir: options.workingDir,
         allowedDomains: options.allowedDomains
       },
@@ -2027,7 +2246,11 @@ var AutoPipeline = class {
     const errors = [];
     this.startTime = Date.now();
     console.log(chalk4.bold("\n  forge") + chalk4.dim(" auto"));
-    console.log(chalk4.dim(`  sandbox ${this.options.sandbox !== false ? "on" : "off"} \xB7 type a message anytime to queue feedback
+    const flags = [
+      `sandbox ${this.options.sandbox !== false ? "on" : "off"}`,
+      ...this.options.yes ? ["auto-approve on"] : []
+    ].join(" \xB7 ");
+    console.log(chalk4.dim(`  ${flags} \xB7 type a message anytime to queue feedback
 `));
     this.startChatListener();
     await this.git.ensureRepo();
@@ -2035,7 +2258,8 @@ var AutoPipeline = class {
     const planSpinner = ora2({ text: `${this.elapsed()} Planning...`, indent: 2 }).start();
     this.activeSpinner = planSpinner;
     try {
-      this.plan = await this.orchestrator.generatePlan(description);
+      const attachmentContext = buildAttachmentPrompt(this.options.attachments || []);
+      this.plan = await this.orchestrator.generatePlan(description + attachmentContext);
       planSpinner.succeed(`${this.elapsed()} Plan ready`);
       this.activeSpinner = null;
       this.displayPlan(this.plan);
@@ -2415,6 +2639,7 @@ var AutoPipeline = class {
   }
   // ── Review Gate ───────────────────────────────────────────
   async reviewGate() {
+    if (this.options.yes) return "continue";
     if (!process.stdout.isTTY) return "continue";
     if (!this.options.mute) {
       playSound();
@@ -2801,8 +3026,12 @@ export {
   GitManager,
   stateManager,
   Pipeline,
+  parseAttachments,
+  stageAttachments,
+  formatAttachmentList,
+  buildAttachmentPrompt,
   AutoPipeline,
   validateConfig,
   loadAndValidateConfig
 };
-//# sourceMappingURL=chunk-2HFEPXBV.js.map
+//# sourceMappingURL=chunk-P5CLBIGQ.js.map