Major changes across 21 files (755 additions, 196 deletions):
Browser Automation Migration:
- Add versioned project migration system (prompts.py) with content-based
detection and section-level regex replacement for coding/testing prompts
- Migrate STEP 5 (browser verification) and BROWSER AUTOMATION sections
in coding prompt template to use playwright-cli commands
- Migrate STEP 2 and AVAILABLE TOOLS sections in testing prompt template
- Migration auto-runs at agent startup (autonomous_agent_demo.py), copies
playwright-cli skill, scaffolds .playwright/cli.config.json, updates
.gitignore, and stamps .migration_version file
- Add playwright-cli command validation to security allowlist (security.py)
with tests for allowed subcommands and blocked eval/run-code
Headless Browser Setting Fix:
- Add _apply_playwright_headless() to process_manager.py that reads/updates
.playwright/cli.config.json before agent subprocess launch
- Remove dead PLAYWRIGHT_HEADLESS env var that was never consumed
- Settings UI toggle now correctly controls visible browser window
Playwright CLI Auto-Install:
- Add ensurePlaywrightCli() to lib/cli.js for npm global entry point
- Add playwright-cli detection + npm install to start.bat, start.sh,
start_ui.bat, start_ui.sh for all startup paths
Other Improvements:
- Add project folder path tooltip to ProjectSelector.tsx dropdown items
- Remove legacy Playwright MCP server configuration from client.py
- Update CLAUDE.md with playwright-cli skill documentation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Complete project rebrand from AutoCoder to AutoForge, touching 62 files
across Python backend, FastAPI server, React UI, documentation, config,
and CI/CD.
Key changes:
- Rename autocoder_paths.py -> autoforge_paths.py with backward-compat
migration from .autocoder/ -> .autoforge/ directories
- Update registry.py to migrate ~/.autocoder/ -> ~/.autoforge/ global
config directory with fallback support
- Update security.py with fallback reads from legacy .autocoder/ paths
- Rename .claude/commands and skills from gsd-to-autocoder-spec to
gsd-to-autoforge-spec
- Update all Python modules: client, prompts, progress, agent,
orchestrator, server routers and services
- Update React UI: package.json name, index.html title, localStorage
keys, all documentation sections, component references
- Update start scripts (bat/sh/py), examples, and .env.example
- Update CLAUDE.md and README.md with new branding and paths
- Update test files for new .autoforge/ directory structure
- Transfer git remote from leonvanzyl/autocoder to
AutoForgeAI/autoforge
Backward compatibility preserved: legacy .autocoder/ directories are
auto-detected and migrated on next agent start. Config fallback chain
checks both new and old paths.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Changes:
- start_ui.sh, start.sh: Check for venv/bin/activate instead of just
venv/ directory to detect Windows venvs in Linux/WSL
- Auto-recreate venv when incompatible platform structure detected
- Add error handling for venv removal, creation, and activation failures
- Provide actionable error messages with distro-specific instructions
- start_ui.bat: Check for venv\Scripts\activate.bat for consistency
with start.bat pattern
Fixes issue where users cloning repo in WSL would encounter:
- "venv/bin/activate: No such file or directory"
- "No module named pip" errors
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The previous credential check looked for ~/.claude/.credentials.json,
which no longer exists in recent versions of Claude CLI. This caused
the script to incorrectly prompt users to login even when they were
already authenticated.
Changes:
- Remove check for non-existent .credentials.json file
- Check for ~/.claude directory existence instead
- Always remind users about 'claude login' since we can't verify auth
status without making an API call
- If ~/.claude doesn't exist, pause and warn (but allow continuing)
- Add explanatory comments about the limitation
The new approach is honest about what we can and can't verify:
- We CAN check if the CLI is installed (command -v claude)
- We CAN check if ~/.claude directory exists (CLI has been run)
- We CANNOT verify actual auth status without an API call
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
