Repository navigation
v3.13.1 - Critical Command Fix
Release Notes - v3.13.1
🐛 Critical Fix
Command Registration Issue Fixed
- Fixed: "command 'autoclaude.start' not found" error
- Changed activation event from
onCommand:autoclaude.starttoonStartupFinished - This prevents circular dependency where extension needs to be activated to register the command that activates it
Build Improvements
- Added
keepNames: trueto esbuild configuration to preserve function names - Ensures proper export of
activateanddeactivatefunctions - Prevents minification from breaking extension exports
🔧 Technical Details
What was wrong?
The extension was configured to activate only when autoclaude.start command was invoked, but the command couldn't be registered until the extension was activated - creating a circular dependency.
The fix:
- Extension now activates after VS Code startup is finished
- All commands are registered immediately when extension activates
- Commands are available as soon as VS Code is ready
📦 Installation
# VS Code Marketplace
ext install R3ENetwork.autoclaude
# Manual Installation
code --install-extension autoclaude-3.13.1.vsix✅ Verification
After installing, you should be able to:
- Open Command Palette (Ctrl/Cmd + Shift + P)
- Type "Claude"
- See all AutoClaude commands
- Run "Claude: 🚀 Start Claude Assistant" without errors
Full Changelog: v3.13.0...v3.13.1