Downloads
Multiple ways to run LIFEOSAI during and after the workshop. Pick what fits your laptop and IT policy — all five channels point at the same multi-agent substrate.
Desktop apps
LIFEOSAI for Mac
Apple Silicon + Intel. ~80 MB .dmg installer. Drag to Applications. Best-tested channel for the workshop.
LIFEOSAI for Windows
x86_64 .exe installer. Tested but less polished than Mac — file any quirks via GitHub.
TestFlight build
iPhone preview — monitor your agents and review tasks from your phone. Join the beta via the TestFlight link.
Other ways in
Hosted workshop access
12 participant logins on our hosted instance — no install needed. Works from any browser. Backup channel for any laptop that can’t install locally.
GitHub repo
Clone, build, and run LIFEOSAI locally. Pre-approved access for the engineering team; others by request.
Environment checklist
GCP Vertex AI configuration, Claude API setup, network requirements. Walks IT teams through one-laptop verification before the workshop.
Pre-workshop setup checklist
To verify your laptop is workshop-ready, NBS engineers should confirm:
- Claude Code installed —
npm install -g @anthropic-ai/claude-code. Verify withclaude --version. - GCP Vertex AI access — Claude API working through your NBS GCP project. We’ll send the configuration sheet separately.
- Anthropic models enabled — request access on Vertex Model Garden for Claude Opus 4.6 + Sonnet 4.6 + Haiku 4.5. Approval takes 1–2 business days.
- One end-to-end test —
claude --print "Hello"should respond using the Vertex backend.
Once any one laptop verifies the path is clean, we’ll share the Mac and Windows installer URLs so the rest of the team can install during the workshop. The Hosted workshop access channel works regardless and is our backup if any laptop install hits a wall.
After the workshop
Your LIFEOSAI installation stays. The 9-agent AI Guardrail Lab company travels with the app. You can continue extending — add your own agents, build new “offices” (companies) for NBS-Dev, Philippines-IoT, NBS-Accounts, etc. The GitHub repo is yours to fork or stay close to as we keep evolving the substrate.