Skip to content

Release v0.2.5: Fix CLI onboarding loop bug with context-aware configuration#62

Merged
freshtechbro merged 1 commit intomasterfrom
bug-fixes
Aug 14, 2025
Merged

Release v0.2.5: Fix CLI onboarding loop bug with context-aware configuration#62
freshtechbro merged 1 commit intomasterfrom
bug-fixes

Conversation

@freshtechbro
Copy link
Owner

Summary

  • Fixed critical CLI onboarding loop bug where vibe command repeatedly triggered first-run setup
  • Implemented context-aware configuration system using enhanced TransportContext pattern
  • CLI now correctly detects user's project directory using process.cwd() instead of package directory
  • Configuration files now save to user's working directory with package directory fallback

Technical Changes

  • Enhanced OpenRouterConfigManager with context-aware path resolution
  • Updated SetupWizard to accept TransportContext for intelligent file operations
  • Implemented dual-location configuration saving for reliability
  • Added comprehensive test coverage for CLI onboarding flows

User Experience Improvements

  • CLI users can now run vibe from any directory in their project
  • Enhanced error handling and debugging information
  • Better setup wizard experience with improved validation
  • Maintains full backward compatibility for all existing setups

Quality Assurance

  • ✅ TypeScript compilation passes with zero errors
  • ✅ ESLint validation passes with no issues
  • ✅ Build process completes successfully
  • ✅ Maintains strict typing enforcement standards
  • ✅ All tests pass with comprehensive coverage

Test plan

  • Test CLI first-run detection in fresh directory
  • Verify configuration files saved to correct user project location
  • Test that subsequent CLI runs skip onboarding
  • Validate server mode still works with package directory
  • Test context-aware path resolution logic
  • Validate error handling and edge cases

🤖 Generated with Claude Code

…uration

### Major Bug Fixes
- **Fixed critical CLI onboarding loop bug** where vibe command repeatedly triggered first-run setup
- CLI now correctly detects user's project directory using process.cwd() instead of package directory
- Configuration files (`.env`, `llm_config.json`, `.vibe-config.json`) now save to user's working directory

### Architecture Enhancements
- **Context-aware configuration system** using enhanced TransportContext pattern
- Dual-location configuration saving (user directory + package fallback) for reliability
- Enhanced OpenRouterConfigManager with intelligent path resolution based on transport type
- Updated SetupWizard with transport context support for CLI vs server differentiation

### User Experience Improvements
- CLI users can now run `vibe` from any directory in their project
- Enhanced error handling and debugging information for configuration persistence
- Improved first-run detection logic with context-aware validation
- Better setup wizard user experience with comprehensive test coverage

### Documentation Updates
- Updated README.md with v0.2.5 release notes and CLI enhancement details
- Enhanced CLAUDE.md with CLI auto-detection features and transport context documentation
- Updated CHANGELOG.md with comprehensive release notes
- Updated setup scripts (setup.sh, setup.bat) to reflect v2.5

### Technical Improvements
- Maintains full backward compatibility for all existing server setups
- Follows DRY principles and existing architectural patterns
- Enhanced UnifiedSecurityConfigManager integration
- Comprehensive test coverage for CLI onboarding flows
- Zero breaking changes for MCP client integrations

### Quality Assurance
- All TypeScript compilation checks pass with zero errors
- ESLint validation passes with no issues
- Build process completes successfully
- Maintains strict typing enforcement standards

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@freshtechbro freshtechbro merged commit 3ff6f71 into master Aug 14, 2025
3 checks passed
@freshtechbro freshtechbro deleted the bug-fixes branch August 14, 2025 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant