Fix: preserve user working directory when spawning Claude instances

[jrevillard]

Problem

When running claude-flow claude spawn from a specific directory, Claude was incorrectly started with the claude-flow installation directory (/usr/local/share/npm-global/lib/node_modules/claude-flow) as its working directory instead of the user's current working directory.

Root Cause

The issue occurred because:

1. bin/claude-flow sets cwd: path.join(__dirname, '..') when spawning the Deno process
2. src/cli/simple-cli.js did not specify a working directory when spawning Claude, inheriting the claude-flow installation directory

Solution

Implemented a comprehensive fix that preserves the user's original working directory:

Changes Made

1. bin/claude-flow - Added CLAUDE_FLOW_ORIGINAL_CWD environment variable to capture user's original working directory

2. src/cli/simple-cli.js - Multiple improvements:

   • Set cwd parameter to use original working directory when spawning Claude process
   • Added CLAUDE_FLOW_CWD environment variable passed to Claude
   • Added working directory to configuration display in enhanced task
   • Added explicit instructions to Claude about correct working directory

How It Works

1. Capture: bin/claude-flow captures process.cwd() in CLAUDE_FLOW_ORIGINAL_CWD
2. Process CWD: Claude subprocess spawns with original directory as working directory
3. Environment: Claude receives CLAUDE_FLOW_CWD environment variable
4. Instructions: Claude gets explicit guidance about correct working directory
5. Configuration: Working directory is displayed in task configuration

Testing

• Tested with dry-run mode to verify correct working directory is used
• Verified environment variables are properly set and passed

Result

After this fix, when users run claude-flow claude spawn from their project directory, Claude will:

• Start with the correct working directory as its process CWD
• Receive explicit instructions about the working directory
• Show the correct directory in its welcome message
• Perform all file operations relative to the user's project directory

Fixes issue where Claude was working in claude-flow installation directory instead of user's project directory.

[ruvnet]

take a look at my update. i think i resolved this