This guide installs the backend, builds the UI, and configures API keys.
- Python 3.10+ (Windows:
py -3, macOS/Linux:python3) - Node.js 18+ and npm
- Git (optional but recommended)
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
.\setup.ps1chmod +x ./setup.sh
./setup.shThe scripts will:
- Create a
.venvvirtual environment - Install Python dependencies from
requirements.txt - Install UI dependencies and build the UI bundle
- Prompt for provider API keys and set environment variables
Activate the virtual environment (if the script is not already running):
.\.venv\Scripts\Activate.ps1source .venv/bin/activateStart the server:
python -m app --selfOpen:
http://127.0.0.1:8000
@break: pause all agent work for the active run.@attention: pause work and call a team meeting (await instructions).@resume: resume work (any stakeholder message also resumes).
python -m venv .venvActivate:
- Windows:
.\.venv\Scripts\Activate.ps1 - macOS/Linux:
source .venv/bin/activate
python -m pip install --upgrade pip
pip install -r requirements.txtcd ui
npm install
npm run build
cd ..These are used by the provider integrations. You can set only the ones you need.
OPENAI_API_KEYANTHROPIC_API_KEYGROQ_API_KEYGEMINI_API_KEY
Optional:
AI_DEVTEAM_ENV(default:dev)AI_DEVTEAM_ALLOW_SELF_EDIT(default:true)AI_DEVTEAM_ALLOW_SELF_PROJECT(default:false)AI_DEVTEAM_GENERATE_PROFILES(default:true)AI_DEVTEAM_REPO_ROOT(defaults to current directory)
$env:OPENAI_API_KEY = "sk-..."export OPENAI_API_KEY="sk-..."- If the UI still shows old assets, hard refresh the browser.
- If PowerShell blocks script execution, use:
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass