Quick Start
System Requirements
| Requirement | Minimum Version | Check Command |
|---|---|---|
| Node.js | v18.0.0+ | node --version |
| npm | v9.0.0+ | npm --version |
| npx | (included with npm) | npx --version |
| Git | Any recent version | git --version |
Download Links
- Node.js: https://nodejs.org/ (Download LTS version - includes npm & npx)
- Git: https://git-scm.com/ (Optional, but recommended)
Installation Methods
Method 1: npx (Recommended)
Method 2: From GitHub
Method 3: Global Installation
Diagnostic Tool
If you’re having installation issues, run our diagnostic tool:Windows (CMD)
Windows (PowerShell)
macOS/Linux
Common Issues & Solutions
Issue 1: “Node.js version too old”
Error:- Download Node.js LTS from https://nodejs.org/
- Install and restart your terminal
- Verify:
node --version(should show v18+ or v20+)
Issue 2: “npm version too old”
Error:Issue 3: “npx not found” or “npx command not recognized”
Cause: 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
Issue 4: “EACCES: permission denied”
Solution (Windows): Run terminal as Administrator Solution (macOS/Linux):Issue 5: “ETIMEDOUT” or “ECONNREFUSED”
Cause: Network/firewall blocking npm registry Solutions:-
Check npm registry:
-
Reset registry:
-
Test connectivity:
-
Behind corporate proxy:
-
Use mirror (China):
Issue 6: “PowerShell execution policy” (Windows)
Error:Issue 7: “Cannot find module” or “Missing dependencies”
Solution:Issue 8: “SSL/Certificate errors”
Solution:Issue 9: Package shows old version
Cause: npm cache serving old version Solution:Environment Verification Checklist
Run these commands to verify your environment:Post-Installation Verification
Verify AIOX Installation
Test Agent Activation
- Open your IDE (Claude Code, Cursor, etc.)
- Activate an agent:
@dev - Run help command:
*help - Verify you see agent commands
Brownfield Installation
Installing in Existing Projects
What AIOX Adds
.aiox-core/directory with framework files- IDE integration files (
.claude/,.codex/, etc.) docs/stories/directory for development stories- npm scripts for quality gates and sync
Safety Guarantees
- Non-destructive: AIOX creates files, never overwrites existing
- Rollback:
git checkout HEAD~1 -- .restores pre-AIOX state - Config preservation: Your
.eslintrc,tsconfig.json, etc. stay intact
Getting Help
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 - Discord: Join our community for support
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
Quick Reference
| 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 |
npx aiox-core@latest init <name> | Create new project |
npx aiox-core@latest doctor | Run diagnostics |
npx aiox-core@latest info | Show system info |
Platform-Specific Notes
Windows
- Use PowerShell or Git Bash for best compatibility
- Some commands may require running as Administrator
- Path separators use backslash (
\) or forward slash (/)
macOS
- May need to install Xcode Command Line Tools
- Use Homebrew for Node.js:
brew install node - Path issues rare with modern Node.js installers
Linux
- Avoid using
sudowith npm - use nvm instead - May need to install build-essential:
sudo apt install build-essential - Permissions issues common - use nvm or fix npm permissions