Setting up your AI Workforce
Five steps, about ten minutes. You copy a single pack from the install page and paste it into the Code tab of the Claude Desktop App, rather than dragging a file in, and the Claude Desktop App writes out every seat file itself.
Build your team on the site
Pick your seats, name them if you want to, and answer the four context questions: what you do, what the team can read, where finished work should be filed, and what should never happen without you. That's what makes the pack yours rather than a generic template.
Open the Claude Desktop App in the folder you work from
Start the session in the actual folder you want the team to operate from, not a folder above or below it. The pack checks where it's running, and everything downstream depends on getting this one right.
Copy the pack and paste it in
Copy the pack from the install page and paste it into the Code tab of the Claude Desktop App. Before it writes anything, it asks you two questions: which folder is the root, and where your working files live. Answer both and it takes it from there.
Run the Chief of Staff and answer its interview
Use the Chief of Staff's slash command, which is the name you gave it on the site with a slash in front (the install page shows the exact command), and answer its first-run interview one question at a time: mailboxes, calendars, filing, how you approve things, and which playbooks to switch on. It plays back what it heard before moving to the next question, so you're never guessing whether it understood you.
Check it worked
Ask the Chief of Staff who's on the team. It should name every seat it found. A generic answer instead of specific names means the pack didn't load properly, so go back to step three.
Where it lives
The pack has to sit at the root of the folder you open the Claude Desktop App in, not a level below it in a subfolder. The Claude Desktop App only looks where the session started, so a pack written one level too deep doesn't error. It simply never loads: no seats, no Chief of Staff, and no obvious reason why. If a session isn't finding your team, this is the first thing to check.
Three ways to use it
Use its slash command in any Claude Desktop App session; it's the only seat you address directly.
Ask for one by name (inbox triage, voice memo to content, weekly sweep) and it delegates to whichever seats that playbook needs.
Ask what's open and it reports back across every seat, not just the one you last spoke to.
Change your team later
Edit your seats on the site whenever you want to add one, rename one, or change what a seat covers. Copy the pack again and paste it into the same Claude Desktop App session: it adds or amends what's changed without clobbering anything you've already got running. If you edit the site and forget to re-paste, the install page shows a notice that your setup has moved past what you last pasted in, so you're never running on a stale pack without knowing it.
Go to installThe Claude Desktop App only, for now
Workforce runs inside the Claude Desktop App only. Every seat is an agent file it writes, and the Chief of Staff needs its session and file tools to work at all. There's no ChatGPT or Gemini version and no hosted app. If you don't already use the Claude Desktop App, install it before you configure a pack.
See the benchLooking for the Boardroom?
The Boardroom is a standing team for decisions: seats that argue a question through and hand you one recommendation. The Workforce is a standing team for the work itself: seats that draft, triage, and file, then check their own work before it reaches you.
Setting up your Boardroom