/setup
/setup is the first-time personalisation wizard for your workspace. It asks you a short series of questions about your business, one at a time, and writes your answers into the files that tell Claude who you are and how your workspace is configured. It takes about five minutes.
When to Use It
Section titled “When to Use It”Run /setup once, straight after you install AI Business OS and before you start any other work. The Running Setup page walks through the first run in context.
You can run /setup again at any later point. Claude warns you first that a second run overwrites your current configuration, and asks you to confirm before it continues.
How to Run It
Section titled “How to Run It”- Open your workspace folder in VS Code, the folder that contains
.claude/. - Open the Claude Code panel from the VS Code sidebar or the editor toolbar.
- Type
/setupin the message box at the bottom of the Claude Code panel and press Enter. - Answer each question as Claude asks it, because Claude waits for your answer before it asks the next one.
- Read the summary that Claude shows at the end and check each value.
- Say yes when Claude asks whether to commit the setup, or say no and run
/synclater.
The Questions
Section titled “The Questions”| # | Question | What Claude does with the answer |
|---|---|---|
| 1 | Company or organisation name | Writes it into CLAUDE.md, state.json and integrations.json |
| 2 | Industry | Writes it into CLAUDE.md |
| 3 | Workspace ID | Suggests an ID built from your company name, such as example-consulting-biz-os, and asks you to confirm it |
| 4 | GitHub repository address | Records it so that /sync can check it pushes to the right place. Answer none if you do not use one |
| 5 | Cloud storage | Asks which service you use for large files and the full path to the synced folder |
| 6 | Language variant | UK English or US English, written into the content defaults rule |
| 7 | Calendar | Asks which calendar app you use, if any, and which calendars to include in your daily briefing |
| 8 | Primary contact | The name Claude uses when it addresses you |
| 9 | Project numbering | Tells you that projects are numbered P001, P002, P003 and so on. On a second run, your existing numbering stays exactly as it is |
After these questions, Claude works through the six company context files. Each file has its own setup prompt at the top. Claude asks you that prompt and writes your answer into the file. If you say “skip” or “not applicable”, Claude leaves the placeholder text in place and moves on.
What It Reads and Writes
Section titled “What It Reads and Writes”| File | What changes |
|---|---|
.claude/CLAUDE.md |
Company name, industry, workspace ID, repository and cloud storage path replace the placeholders. The Customisation Log gets today’s date |
.claude/company/ |
The six company files are filled in from your answers |
.claude/config/integrations.json |
Company name, set-up date, calendar provider and names, storage provider and path, and feature flags |
.claude/state/state.json |
The workspace block (name, ID, type and repository) and the calendars for your daily briefing |
.claude/rules/content-defaults.md |
Your language variant |
Claude Code asks you to approve the calendar tools the first time Claude uses them, and records your approval in .claude/settings.json.
The workspace type is set to client by default, or personal if you are setting up a workspace for yourself.
Example
Section titled “Example”/setupAt the end, Claude shows a summary like this one.
## Setup Complete
**Workspace:** Example Consulting (example-consulting-biz-os)**GitHub:** not configured**Cloud Storage:** Google Drive at /Users/you/Google Drive/Example Consulting**Language:** UK English**Calendar:** not configured**Project numbering:** P001, P002, P003The summary also lists the files Claude updated and suggests next steps. These are to commit with /sync, run /day for your first briefing and create a project with /newproject.
Upgrading From a Version 1 Workspace
Section titled “Upgrading From a Version 1 Workspace”Before it asks any questions, /setup checks for a file called .claude/CLIENT_PROFILE.md. Workspaces set up with AI Business OS version 1 kept all company information in that single file. If Claude finds it, and the company files still hold placeholder text, Claude moves the content into the six company files instead of running the normal questions.
Claude archives the old profile to .claude/engine-backups/company-migration/ and never deletes it. It then shows you which files it wrote and offers to continue with the rest of the setup. The migration leaves state.json, integrations.json, your project folders, your domain files and any custom skills, commands or rules untouched. The /migrate-company command does the same job in more detail, with a walkthrough for areas the old profile covered thinly.