What You’ll Learn

This live open Q&A is a grab-bag of practical questions from real users, and out of it comes a clear starter guide: the exact setup you need to run Claude Cowork, the end-of-session habit that keeps your operating system smart, and the single mindset shift James keeps pushing. If you’re new to this, it’s the on-ramp.

By the end you’ll know the minimum setup to get going, why you should wrap up every session deliberately, how two orchestrators can work together, and the one habit worth building above all others.

The Minimum Setup

James’s two cents on what you actually need:

1. Install the desktop app. You must have the Claude application installed directly on your computer — Windows or Mac (claude.com/download). Don’t work at claude.ai in the browser; open the desktop software.

2. Be on a paid plan. The minimum is the $20 plan. You can confirm it by checking the bottom-right for a Pro or Max plan.

💡 In Plain English: the desktop app plus a paid plan is the doorway. Everything else — the operating system, the agents — installs on top of that.

The Habit That Keeps It Smart: Wrap Up Every Session

James demonstrates something he does at the end of every session with Dean, his orchestrator: he says “we’re finished — write this to the project board, save your memories, update the wiki.” Dean then updates the wiki page, the daily log, the memory, and the task ledger before the session closes.

Why it matters: he’s run roughly a thousand sessions, and while none of that work is technically lost, the learnings — the things worth remembering and indexing for later — aren’t pulled into context unless you capture them.

“I do a bit of a wrap-up at the end so the memory is in context next time. Otherwise it’s there, but Dean can’t see it.”

This is the discipline that turns a pile of chats into a compounding second brain.

Two Orchestrators, One Business

A neat case from the Q&A: a customer (Ted) already had his own orchestration officer and some agents before installing Dean. Rather than choosing one, he had Claude set them up to work together — one orchestrator handling its piece and handing off to the departments Dean runs. You don’t have to throw away what you’ve built to adopt an operating system; you can wire them together.

Bonus: A Video Repurposing Stack

For turning livestreams into short clips, James points at a stack he’s experimenting with: Remotion (a free, AI-powered video editor you install from GitHub), ElevenLabs for natural voice, and eCamm for live streaming — which records landscape and a simultaneous portrait headshot. That separate vertical headshot solves a common problem: AI repurposing tools often crop half your face and half your screen, but with a clean headshot saved separately, Remotion can rebuild proper vertical clips with supporting text.

The One Habit to Build

James closes with the lesson he says matters most for the rest of the year — and admits he’s still working on it himself: stop asking AI tools to do something for you, and instead state the outcome you want.

“I’m trying really hard not to ask AI to do a task. I’m trying to say what I want at the end — ‘I want 15 new qualified leads for this service.'”

The Takeaway

Get the desktop app and a paid plan, wrap up every session so your memory and wiki stay current, and practice asking for outcomes instead of tasks. Those three habits are what make an AI operating system actually compound over time. When you’re ready for the full system, Dean and the campus operating system install into Claude Desktop at trainingsites.io/os, and the community is free at trainingsites.io/join.

Teach more, and let the agents do the rest.

This tutorial is a recap of a live open Q&A session.