npx aiox-core@latestThis command downloads and runs the latest version of AIOX-Core installer.
| Requirement | Minimum Version | Check Command |
|---|---|---|
| Node.js | v18.0.0+ | node --version |
| npm | v9.0.0+ | npm --version |
| npx | (included with npm 5.2+) | npx --version |
| Git | Any recent version (optional) | git --version |
- Node.js: https://nodejs.org/ (Download LTS version - includes npm & npx)
- Git: https://git-scm.com/ (Optional, but recommended)
# Install in current directory
npx aiox-core@latest
# Install with specific version
npx aiox-core@2.2.0
# Show version
npx aiox-core@latest --version
# Show help
npx aiox-core@latest --helpnpx github:SynkraAI/aiox-core installnpm install -g aiox-core
aiox-coreIf you're having installation issues, run our diagnostic tool:
curl -o diagnose.cmd https://raw.githubusercontent.com/SynkraAI/aiox-core/main/tools/quick-diagnose.cmd && diagnose.cmdirm https://raw.githubusercontent.com/SynkraAI/aiox-core/main/tools/quick-diagnose.ps1 | iexcurl -fsSL https://raw.githubusercontent.com/SynkraAI/aiox-core/main/tools/diagnose-installation.js | nodeError:
error engine Unsupported engine
error notsup Required: {"node":">=18.0.0"}
Solution:
- Download Node.js LTS from https://nodejs.org/
- Install and restart your terminal
- Verify:
node --version(should show v18+ or v20+)
Error:
npm ERR! Required: {"npm":">=9.0.0"}
Solution:
# Update npm globally
npm install -g npm@latest
# Verify
npm --versionCause: npm bin folder not in system PATH
Solution (Windows):
- Find npm prefix:
npm config get prefix - Add to PATH:
- Press Win+X → System → Advanced system settings → Environment Variables
- Edit "Path" under User variables
- Add:
C:\Users\YOUR_USERNAME\AppData\Roaming\npm
- Restart terminal
Solution (macOS/Linux):
# Add to ~/.bashrc or ~/.zshrc
export PATH="$PATH:$(npm config get prefix)/bin"
# Reload
source ~/.bashrcSolution (Windows): Run terminal as Administrator
Solution (macOS/Linux):
# Fix npm permissions (recommended)
mkdir -p ~/.npm-global
npm config set prefix '~/.npm-global'
export PATH=~/.npm-global/bin:$PATH
# Or use nvm (best practice)
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bashCause: Network/firewall blocking npm registry
Solutions:
-
Check npm registry:
npm config get registry # Should be: https://registry.npmjs.org/ -
Reset registry:
npm config set registry https://registry.npmjs.org/ -
Test connectivity:
npm ping
-
Behind corporate proxy:
npm config set proxy http://proxy.company.com:8080 npm config set https-proxy http://proxy.company.com:8080
-
Use mirror (China):
npm config set registry https://registry.npmmirror.com
Error:
File cannot be loaded because running scripts is disabled on this system
Solution:
# Run as Administrator
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUserSolution:
# Clear npm cache
npm cache clean --force
# Remove node_modules if exists
rm -rf node_modules
# Try again
npx aiox-core@latestSolution:
# Temporarily disable strict SSL (not recommended for production)
npm config set strict-ssl false
# Better: Update certificates
npm config set cafile /path/to/certificate.pemCause: npm cache serving old version
Solution:
# Clear npx cache
npx clear-npx-cache
# Or force fresh download
npx --ignore-existing aiox-core@latest
# Or use specific version
npx aiox-core@2.2.0Issue 10: "Pro activation failed: Installed Pro artifact did not create node_modules/@aiox-squads/pro"
Symptom: The installer reaches Step 2 (Pro Content Installation), successfully authenticates the buyer email, downloads the Pro tarball — and then prints:
⚠️ Pro activation failed: Installed Pro artifact did not create node_modules/@aiox-squads/pro.
Continue with Community (free) edition instead? (Y/n)
Root cause: The bug was in installer versions 5.2.5 and earlier. npm install <tarball> walked up the directory tree looking for the first ancestor with a package.json, then installed @aiox-squads/pro there instead of in your chosen target directory. The post-install integrity check then failed because the artifact landed in the wrong place — even though npm had exited 0.
This is fully fixed in @aiox-squads/core@5.2.6 and above. The installer now passes --prefix + --workspaces=false to npm install, which anchors the install to the target directory regardless of ancestor package.json/workspaces declarations.
Solution (most users — works on any OS):
# Update to the fixed version (the -p flag is critical — it forces latest resolution)
npx -y -p @aiox-squads/core@latest aiox installSolution (if you previously hit the error and the fix above still misbehaves — residual state from old attempts):
macOS / Linux (bash/zsh):
# 1. Remove any stray @aiox-squads/pro that the buggy installer left in an ancestor dir
find . -maxdepth 5 -path "*/node_modules/@aiox-squads/pro" -type d 2>/dev/null \
-exec rm -rf {} + 2>/dev/null
# 2. Clear the npx cache so it doesn't serve the old buggy version
rm -rf ~/.npm/_npx 2>/dev/null
# 3. Retry the install with -p forcing the latest published version
npx -y -p @aiox-squads/core@latest aiox installWindows (PowerShell):
# 1. Remove any stray @aiox-squads/pro that the buggy installer left in an ancestor dir
Get-ChildItem -Recurse -Depth 5 -Directory -ErrorAction SilentlyContinue `
| Where-Object { $_.FullName -match '\\node_modules\\@aiox-squads\\pro$' } `
| Remove-Item -Recurse -Force -ErrorAction SilentlyContinue
# 2. Clear the npx cache so it doesn't serve the old buggy version
Remove-Item -Recurse -Force "$env:USERPROFILE\.npm\_npx" -ErrorAction SilentlyContinue
# 3. Retry the install with -p forcing the latest published version
npx -y -p @aiox-squads/core@latest aiox installWindows (Command Prompt / cmd.exe):
:: 1. Remove any stray @aiox-squads/pro that the buggy installer left behind
for /f "delims=" %i in ('dir /b /s /ad "node_modules\@aiox-squads\pro" 2^>nul') do rd /s /q "%i"
:: 2. Clear the npx cache
rd /s /q "%USERPROFILE%\.npm\_npx" 2>nul
:: 3. Retry the install
npx -y -p @aiox-squads/core@latest aiox installYou do NOT need:
npm cache clean --force— does not affect version resolutionrm -rf node_modulesfrom random directories — only matters if step 1 above found a stray Pro install in that location
If it still fails after both solutions, share with support:
pwd && node --version && npm --version- The full installer output (not just the error line)
- Output of:
find . -maxdepth 5 -name package.json 2>/dev/null | head -10
Reference: release-procedure.md (operator playbook), PR #742 (the fix).
Run these commands to verify your environment:
# 1. Check Node.js (need v18+)
node --version
# 2. Check npm (need v9+)
npm --version
# 3. Check npx
npx --version
# 4. Check npm registry access
npm view aiox-core version
# 5. Test installation
npx aiox-core@latest --versionExpected output:
v22.x.x (or v18+/v20+)
11.x.x (or v9+)
11.x.x (same as npm)
2.2.0
2.2.0
If you're still having issues:
- GitHub Issues: https://github.com/SynkraAI/aiox-core/issues
- Run diagnostics:
npx aiox-core@latest doctor - Check system info:
npx aiox-core@latest info
When reporting issues, please include:
- Operating system and version
- Node.js version (
node --version) - npm version (
npm --version) - Full error message
- Output of diagnostic tool
| Command | Description |
|---|---|
npx aiox-core@latest |
Install/run wizard |
npx aiox-core@latest --version |
Show version |
npx aiox-core@latest --help |
Show help |
npx aiox-core@latest install |
Install in current dir |
npx aiox-core@latest init <name> |
Create new project |
npx aiox-core@latest doctor |
Run diagnostics |
npx aiox-core@latest info |
Show system info |
Last updated: December 2025 | AIOX-Core v2.2.0