Get your organization
How does the course get into the folder I already have?
You already have a workbench. Today one skill copies the Agent Workforce organization into it: 20 agents, each one met the first time it works, the profiles for the whole organization, the skills those agents run, and the course lessons and prompts. It goes into the same folder you have been using since Essentials. Nothing you made is touched. Your own skills stay exactly as they are. Then you save it, the way you saved everything in Essentials.
Fifteen minutes. You paste two prompts, read one list, say yes once, and save.
20 agents in .claude/agents (and .codex/agents for Codex), your Chief of Staff among them, each one met the first time it works; a workforce folder with every seat's profile and the skills; and a course/workforce folder with the lessons. All inside my-workbench.
Week 1 opens with "your workbench should already have a workforce folder." This is the lesson that makes that sentence true.
Your agent checks that your account can see the course, connects the course’s branch to your workbench, shows you exactly what would be added, and waits for your yes. Only then does anything land, as one commit on top of your own history.
You paste, you read the list, you say yes, you save. The agent does the downloading and the checking. If the list says it will replace or delete something you wrote, you stop. Step 3 says what to expect if you finished Agent Team HQ.
First, refresh your workbench. One paste, one minute.
Your workbench was built from a template, and the template has moved on since setup weekend: the skill that connects a program got smarter. Running the installer again will not bring that in (setup never rewrites a workbench that already exists). This paste does. It copies the latest aibl- skills into your workbench, nothing else, and saves them as one commit. Then it checks whether any program you have joined has an update.
You are the AI Build Lab update assistant. I am a student and this session is open on my workbench. Fetch the update procedure from this URL and follow it from the beginning, step by step, without summarizing: https://raw.githubusercontent.com/aibuild-lab/aibl-installer/main/UPDATE-PROMPT.md Say what you are about to do before each step. Do not install anything, do not re-run setup, and do not touch anything I made. If you cannot fetch the URL, say so and I will paste the procedure into chat.
When it finishes, start a new session in the same folder so the app loads the fresh skills. If it says your skills were already current, that is a pass, not a problem.
Whenever the team says an update is out, or whenever you want to check, this is the move. It is also on the installer’s start page under “Later: update your workbench.”
You finished Agent Team HQ: do not run setup again. Paste the update prompt above (it is the same “Later: update your workbench” paste from the installer’s start page), then enroll in Step 2. If you changed any Team HQ agent file, first ask your agent to copy your changes into a note in work/, and save with /aibl-checkpoint.
You came from Camp: first do Essentials lesson 3, the install, on the computer that has the app. Leave your Camp folders alone, and never copy Camp agents into your workbench.
You were in Cohort 1: you are already enrolled, so do not run aibl-enroll again. If the app offers to run aibl-update, skip that offer. Paste the update prompt above instead: it refreshes aibl-update first, then brings your course up to date.
Step 1. Open the app on your workbench, in Auto mode.
Same four checks as every Essentials lesson: pick the my-workbench folder, check Local, set your mode, check the model. Two of them matter more today than they ever have. The folder: the agents you are about to bring in live inside it, and the app only sees them when that folder is the open project. The mode: Auto, not Accept edits, because the Chief of Staff runs its team in the background and reports back into your thread, and that only works in Auto.
When your course access opens, GitHub sends an email inviting you to join aibuild-lab. It goes to the email address on your GitHub account, which may not be the one you use for class. Open it and click Join. Cannot find it? Check spam, or sign in on github.com and open github.com/settings/organizations: a waiting invitation shows there with a button to accept it. Access opens on your cohort's schedule, not at the first live session, so if there is no invitation yet, check your cohort on the Learn dashboard.
Step 2. Run the enroll skill. It shows you what will be added, then waits.
Click in the box where you type and press the forward-slash key. In Codex, type a dollar sign instead. Pick aibl-enroll, one of the skills that came with your workbench (refreshed a minute ago).
/aibl-enroll
Three things happen before you are asked anything. The agent checks that your GitHub account can see the course. It connects the course’s own branch to your workbench (the same way your private copy on GitHub is connected, just read-only). Then it lists everything that would be added, and checks that none of it collides with a file of yours.
Nothing is wrong with your workbench. The first three almost always mean a GitHub invitation is waiting for you to accept: check the email on your GitHub account, or github.com/settings/organizations, accept it, then run aibl-enroll again. If there is no invitation there, your access has not opened yet (check your cohort on the Learn dashboard), or it went to a different GitHub account. Post in your program channel with the GitHub username the agent showed you. The last one means the course team has not published the branch yet. Come back later. None of these changed anything on your computer.
Step 3. Read the preview. It should say exactly this. Then say yes.
The preview is a list. Read it against this one:
- Added:
.claude/agents/and.codex/agents/: 20 agent files, one per seat, one set for Claude Code and one for Codex. These are the agents you can pick from the@list. Every one is namedaibl-something. - Added:
.claude/skills/and.agents/skills/: the skills those agents run. A few dozen, all namedaibl-. - Added: a
workforce/folder (every seat's profile, the skills again, the registry that says who is who) and acourse/workforce/folder (lessons, prompts, worksheets). A few hundred files. That is the organization. - Untouched: your own
aibl-skills,context/,work/,library/, yourCLAUDE.mdandAGENTS.md, and your Git history.
The list is long, and the exact count changes with each release of the course. What matters is that these folders are on it, that nothing under Replaced is a file you wrote, and that nothing is deleted. If that holds, tell the agent yes. It applies the plan it just showed you, nothing else. If it asks you to confirm a second time because something changed in between, read the new list the same way.
After that it makes a few short offers, one at a time. One of them is to add your agents to the @ list. Say yes to that one; Step 6 explains why.
Both programs ship some of the same agents under the same names, one copy for Claude Code and one for Codex, plus each program’s list of its agents. The agent shows them as one group with one choice, and it recommends taking the Agent Workforce copies. Take the recommended choice. Your Team HQ lessons still work through the aibl-team-hq skill. If you changed one of those Team HQ agent files and have not copied your changes into a note yet, say no for now, ask your agent to copy your changes into a note in work/, save with /aibl-checkpoint, then run /aibl-enroll again.
Stop. Do not say yes. That means a file you wrote, or a file outside those shared agent files. Take a screenshot of the whole preview and post it in your program channel. Saying no changes nothing.
Step 4. Look at what landed.
Do not take the agent's word for it. Ask it to show you:
What did that just add to my workbench? List the new top-level folders and the agents in .claude/agents, one line each, and confirm that nothing in context/, work/ or library/ changed.
Your folder now looks like this. The lit lines are new; everything else was already yours.
GitHub/
└── my-workbench/
├── CLAUDE.md the note it reads first (Claude)
├── AGENTS.md the same note (Codex)
├── context/ what it knows about you unchanged
├── library/ things you gave it to read unchanged
├── work/ what it makes for you unchanged
├── .claude/agents/ the 20 agents, one file each (Claude Code)
│ ├── aibl-chief-of-staff.md your Chief of Staff
│ └── aibl-ygm.md … the writer, the reviewer, the Professor, Gigawatt and the rest
├── .codex/agents/ the same 20, for Codex
├── .claude/skills/ .agents/skills/
│ ├── aibl-personalize unchanged
│ ├── aibl-checkpoint unchanged
│ ├── aibl-enroll unchanged
│ ├── aibl-update unchanged
│ └── aibl-brief/ aibl-work-order/ … the skills the agents run
├── workforce/ the organization on paper
│ ├── profiles/ every seat, one file each
│ ├── skills/ the same skills, kept with the organization
│ └── shed/registry.yaml who is who, and what each seat may use
└── course/workforce/ the lessons, prompts and worksheets
└── START-HERE.md the four-week path
.claude/agents/, the organization’s profiles in workforce/profiles/. Open any one of them; it is a page of plain text.Text version: the workbench gains a .claude/agents folder and a .codex/agents folder with the 20 agents, new aibl- skills beside the four it already had (unchanged), a workforce folder with every seat's profile, the skills and the registry, and a course/workforce folder with the lessons and START-HERE. The context, library and work folders and both instruction files are unchanged.
Step 5. Save it, so your private copy on GitHub has the organization too.
Same move as Essentials lesson 5. Run the checkpoint skill and let it do the commit and the push.
/aibl-checkpoint
In Codex, type a dollar sign instead of the slash to open the same menu. When it finishes, open github.com, go to your my-workbench repository, and look for the new commit at the top. Click into .claude/agents, then into workforce. If the agents and the profiles are there, your organization is saved somewhere your laptop cannot lose it.
No. Enroll never touches the four skills your workbench came with: aibl-personalize, aibl-checkpoint, aibl-enroll and aibl-update. The update paste at the top of this page is what refreshes them, and it asks you before it changes any one of them.
Step 6. Meet your Chief of Staff, then stop.
@ list”The @ list in Claude Code reads the agents folder in your user folder, not the one in your workbench: ~/.claude/agents/ on a Mac, C:\Users\<you>\.claude\agents\ on Windows. Near the end, aibl-enroll offered to add your agents to the @ list. If you said yes, it put copies of the course’s agents there and did not touch any agent of your own.
Said no, or missed the offer? Run /aibl-enroll again. It sees the course is already in your workbench, adds nothing, and makes the offer again. Say yes. After a course update, the update paste makes the same offer, so the list keeps up.
Codex does not use this list; there you ask for an agent by name.
The app reads that agents folder when it starts, not when a thread starts. So quit the app fully and open it again on the same folder, in Auto (proved on Windows: a new thread alone still showed only file paths; after a restart the agents appeared at the top of the list with their descriptions). Type @. The list now shows the 20 aibl- agents above the file paths. Pick aibl-the-professor, the course companion, and say:
Open the course.
It reads the course's own start page and offers you the first lesson, Meet your organization. You can stop right there. That lesson is Week 1, and it opens in the live session. Coming back tomorrow and asking the Professor the same thing takes you to wherever you left off. If your slash menu also shows /aibl-workforce, that runs the same start page.
The course has three kinds of lessons. Only one is required.
Open your workbench folder as the project. Start a new thread, type @, and pick aibl-chief-of-staff from the list. The thread then runs as your Chief of Staff. Typing the name by hand also works, but then the main session answers on its behalf and rewords what it said.Start a new thread and ask for it by name: “Have aibl-chief-of-staff handle this.”
No. Same folder, same note about you, same skill you wrote. The organization moves in next to your things; it does not move them out.
Once, in the app you used for Essentials. The files serve both: every skill is installed for Claude Code and for Codex at the same time. Open the other app on the same folder later and the agents and skills are already there.
Practice (optional)
Three quick questions to ask your organization, so the new words stick. Copy one into your app. They only read; nothing changes.
Show me the agents in this workbench, one line each: name, then its one job. Then the profiles in workforce/profiles by department.
Open my Chief of Staff's agent file and tell me, in two sentences, its four jobs and what it never does.
Read course/workforce/START-HERE.md and tell me what Week 1 ends with. Do not start anything.
You're done. Here's how you know.
Your organization is in your workbench and on GitHub. Week 1 opens with "your workbench should already have a workforce folder," and yours does.