🚀 Quick Setup
Quick Setup with Plug & Play Modules
A beginner-friendly setup path using the Claude Desktop App and pre-built modules you install
with a single command. No terminal required to get started — just download, drop in, and run
/install.
Section 01
Two Paths to the Same Destination
The plug and play modules work the same way regardless of how you run Claude Code.
The difference is the interface — not the capabilities. Pick the path that matches
your comfort level. You can always switch later.
🖥
Beginner Path
Claude Desktop App
- Download and open Claude — no CLI install needed
- Click the Code tab, choose your workspace folder
- Friendly interface, lower intimidation factor
- Tabs for running multiple sessions side-by-side
- Limitation: must manually run
/prime each new session — no auto-prime on startup
- Same modules, same commands, same results
⚡
Technical Path
VS Code / Cursor + CLI
- Install Claude Code CLI, open terminal in your IDE
- Shell alias
cr = new session + auto-prime + YOLO mode
- Multiple terminals = multiple parallel sessions
- Cron jobs and background scripts run reliably
- IDE choice doesn't matter — Cursor, VS Code, Windsurf all identical
- More power and flexibility for serious builds
💡
The IDE is just a file viewer. When people debate VS Code vs Cursor vs Windsurf —
it doesn't actually matter for Claude Code. All the IDE does is give you a terminal to run Claude Code
in, and a file browser to see your workspace beside it. Pick whichever you're comfortable with.
Section 02
Getting Started with Claude Desktop
The fastest way to get up and running. Skip the CLI install entirely —
just download Claude, open the Code section, and point it at your workspace folder.
1
Download Claude desktop
Get the Claude desktop app (claude.ai/download). You need an active subscription — Max plan recommended for heavy use, Pro plan works to start.
2
Download and unzip the starter template
Get the starter template ZIP from the course materials. Double-click to unzip. Rename the folder to something that represents your workspace (e.g., myagency-workspace). Remember: press Cmd+Shift+Period on Mac to reveal hidden files if the .claude/ folder seems missing.
3
Open the Code section and choose your folder
In Claude desktop, click the Code tab at the top. Click "Choose a different folder" and navigate to your unzipped workspace folder. Set bypass permissions so Claude can work without constant confirmation prompts.
4
Run /prime to initialize
Type /prime in the Claude Code chat to load your context and orient Claude for the session. Unlike the CLI path, you need to do this manually each time you open a new session in the desktop app.
/prime
5
Install your first module
Drop a module ZIP into your module-installs/ folder, then run the install command pointing at it. Claude walks you through the full setup — no manual configuration.
/install @module-installs/context-os.zip
Section 03
The Plug & Play Module Library
Each module is a pre-built ZIP you download from the course, drop into your
module-installs/ folder, and install with a single command.
The modules are designed to be installed in order — each one builds on the previous.
1
Context OS
Foundation layer. Sets up your context files, CLAUDE.md, and /prime command. Everything else builds on this.
Install first
2
Infra OS
Infrastructure layer — GitHub setup, remote repo, system reliability. Enables your workspace to be version-controlled and portable.
3
Data OS
Data pipeline setup. Scopes your funnel, identifies API connections, builds your local database, and sets up daily data collection cron.
4
Intel OS
AI intelligence layer. Includes the AI model tracker — daily scan of leaderboards, updates workspace docs with the latest best models for each use case.
5
Command OS (Telegram)
Telegram as your mobile command interface. /new opus, /name, voice note transcription, daily brief delivery. Spin up new Claude sessions from your phone.
Includes voice notes
6
Daily Brief
Morning intelligence report. Pulls from all data sources + Fireflies meeting intel. Sends Telegram summary + saves PDF to outputs/. Runs at 7 AM.
7
Productivity OS
Task management, GTD integration, daily planning workflows. Turns your AIOS into a personal productivity system alongside your business OS.
+
More modules coming
Each module is versioned — you'll see when updates are available. Modules for meeting intelligence, warm outreach CRM, content pipeline, and more in development.
📦
Versioned and updatable. Each module has a version number. When an improved version
ships, you'll see it — download the new ZIP, drop it in, run /install again.
The install command handles the update. Your customizations are preserved.
Section 04
The /install Command — How It Works
/install is a command built into the starter template. You point it at a module ZIP,
and it handles everything: unzips, reads the install.md, and walks you through
setup step by step — asking questions, identifying what API keys you need, configuring
what's relevant for your business.
1
Download ZIP
Get the module ZIP from the course materials library.
2
Drop into folder
Drag the ZIP into your module-installs/ folder.
3
Run /install
Reference the ZIP in your Claude Code session.
/install @module-installs/data-os.zip
4
Claude guides you
Reads install.md, walks through every step, asks questions, configures for your business.
5
Module active
New commands available, context updated, everything integrated into your workspace.
📋
What's inside a module ZIP: Every module has a standard structure — an
install.md (the guided setup instructions Claude follows), a README.md
for humans, any scripts or reference files needed, and an env.example showing
which API keys are required. The install command reads all of this and orchestrates the setup.
Section 05
Loading Your Context — Three Ways In
When the Context OS module installs, it needs to know about you and your business
to fill in your context files. You can approach this however fits your situation —
there's no single right method.
📁
Drop files in import/
Drag any existing documents into context/import/ — website copy, LinkedIn profile, past proposals, company overview docs. Claude extracts and synthesizes.
💬
Chat interview
Claude asks you questions directly. Great if you don't have existing docs or want to think through your context fresh. Takes 10–15 minutes of back-and-forth.
📋
Paste text
Copy-paste content from ChatGPT exports, Google Docs, Notion pages, or anywhere else. Claude processes whatever you give it and builds the context files.
🔁
Context accumulates over time. You don't have to get it perfect on day one.
Start with whatever you have — even rough, incomplete notes are dramatically better than nothing.
As you use the workspace, Claude learns more about your business and you can update the context
files anytime. The files get richer with every session.
Section 06
Telegram — Your Mobile Command Layer
The Command OS module sets up Telegram as a mobile interface to your AIOS. Telegram's
programmatic slash commands make it uniquely well-suited for this — you can spin up
new Claude sessions, name them, send voice notes, and receive your daily brief,
all from your phone.
⚡
/new opus — Spin up a new session
Creates a new topic in your Telegram group and automatically spins up a new Claude Code instance. Auto-primes it. Mirrors exactly what cr does in the terminal — new session, primed, YOLO mode ready.
🏷
/name — Label your session
Renames the current Telegram topic and adds an emoji. Keeps your sessions organized when you have multiple running. Fires automatically after /new opus to label the context.
🎙
Voice note transcription — Built in
Send a voice message to your Telegram group. The Command OS module picks it up, transcribes it, and processes it — adds it to your ideas database, queues it as a task, or routes it to the right workflow. On the go becomes just as powerful as at your desk.
📊
Daily brief delivery
The daily digest arrives in your Telegram every morning — business metrics, meeting summaries, model updates, anything your cron jobs generated overnight. Read it before you open your laptop.
🗂
Topics = organized sessions
Each Telegram topic is a separate session. Your content session stays separate from your client session from your data session. Organized without any manual filing.
📱
Why Telegram over Slack: Telegram's slash commands work natively in a
programmatic way that Slack doesn't replicate as cleanly. Topics within groups map
directly to separate Claude sessions. Voice notes are first-class. Slack can work —
but it has friction that Telegram doesn't.
Section 07
Why /prime Matters — More Than Just Loading Context
CLAUDE.md loads automatically every session — so why do you need /prime? Because CLAUDE.md
is intentionally kept lean (workspace structure, commands, rules), while /prime does the
deeper loading: it reads your context files, pulls current metrics, loads the operational
index, and confirms what everything is before you start work.
As your workspace grows in complexity, /prime becomes the mechanism that keeps it all navigable.
Here's what a mature prime command reads:
context/business-info.md
What this business is, who it serves, what it sells — the organizational stage.
context/strategy.md
Current strategic priorities and goals — what we're trying to achieve right now.
context/current-data.md
Latest metrics — where things actually stand relative to goals.
context/index.md (advanced)
A documentation index — reads a summary and tells Claude where to go for deeper information when a task requires it. Keeps prime fast while preserving access to depth.
🔧
The advanced pattern: The index document tells Claude "these files are not needed
for prime, but load them when a task requires full deep detail." This keeps your prime command
fast and context-window-efficient, while ensuring Claude can always find what it needs when
working on a specific task. You can keep adding depth without bloating every session.
You can skip /prime when you're first starting with an empty workspace and nothing to load.
But once you've built a meaningful system — real context files, real data, real commands —
skipping prime means Claude walks into the session blind. Don't skip it.
Section 08
Running Multiple Sessions in Parallel
One of the biggest productivity unlocks in AIOS is running multiple Claude sessions
simultaneously — one doing research, one building a command, one analyzing data —
while you manage and direct them all. Here's how it works across both paths.
-
Desktop app: Open multiple tabs within the Code section. Each tab is a separate Claude session running against the same workspace folder. Good for 2–3 parallel sessions before it gets unwieldy.
-
VS Code / CLI: Open multiple terminal panes. Run
cr (or claude + /prime) in each. Easier to manage 4–6 parallel sessions — each one visible in its own terminal window.
-
Same workspace, different tasks: Multiple sessions running on the same folder works well for AIOS — you're usually doing different things (researching in one, building in another) rather than editing the same file simultaneously.
-
Watch for conflicts: If two sessions try to edit the same file at the same time, you'll get conflicts. Avoid having two sessions working on the same command or context file simultaneously.
-
Mac Mini for always-on: If you want cron jobs running 24/7 without leaving your laptop open, set up a Mac Mini with screen sharing. Take your laptop anywhere — AIOS keeps running on the Mini. This is the eventual architecture for serious use.
Key Takeaways
What to Remember
Takeaway 01
Both paths use the same modules
Desktop app or VS Code — the plug and play modules, the context files, the slash commands are all identical. Pick your interface, not a different system.
Takeaway 02
Install in order
Context OS first. Then Infra OS. Then Data OS. Then Intel and Command OS. Each module assumes the previous is in place. Don't skip ahead.
Takeaway 03
/install handles all the complexity
You don't need to understand what's inside a module to install it. Drop the ZIP in, run /install, answer Claude's questions, done. The module does the rest.
Takeaway 04
Context can come from anywhere
Files, pasted text, a chat interview — whatever you have. Even rough is better than nothing. The context files get richer over time as you use the system.
Takeaway 05
Telegram is your mobile cockpit
Once Command OS is installed, your AIOS travels with you. Spin up sessions, send voice notes, get your morning brief — all from your phone, no laptop required.
Takeaway 06
Run /prime every session — without exception
CLAUDE.md loads automatically but doesn't load your context, data, or strategy. /prime is what makes the AI business-aware. Skip it and you're working with a blank slate.
Get Moving
What to Do Right Now
- Download Claude desktop or install the CLI — whichever path you're taking. Get it open and pointed at your workspace folder today.
- Install Context OS first. Drop the ZIP in module-installs/, run /install, answer the questions. Get your four context files populated — even roughly.
- Run /prime and confirm it reads your context back correctly. If Claude summarizes your business accurately, the foundation is set. Move on to Infra OS next.
- Install modules in order. Context → Infra → Data → Intel → Command OS. Don't rush. Each one builds on what's already there.
- Set up Telegram once Command OS is installed. This is the quality-of-life upgrade that makes everything feel like a real operating system rather than a desktop tool.
Continue Learning
Related Modules