bimaiInstall bimai
Copy one prompt into Claude Code and it installs bimai and sets up your team.
Start here
Available
bimai init.Open your project folder in VS Code, start Claude Code, and paste this prompt. Claude installs bimai, asks you a few questions, shows you the team it proposes, and only writes files after you say yes.
What you need: VS Code with Claude Code, and Python 3.11 or newer. Claude checks Python for you and tells you if it's missing.
Then paste it into Claude Code, in your project folder.
Show the prompt
Set up bimai (https://docs.bimai.nl) in this project folder for me. Follow these steps in order and
don't skip the confirmation.
1. Check that Python 3.11 or newer is available. Then install bimai:
pip install "git+https://github.com/StefanDaniels1/BIMAI.git"
Check it worked with: bimai --version
2. Look at what's already in this folder, so you can suggest answers: models (.ifc, .rvt, .nwd,
.dgn, .dwg), BCF issues, a BEP or EIR document, planning exports, Relatics exports and meeting
transcripts.
3. Ask me these questions one at a time, in plain language, suggesting answers where you can:
- The project name.
- My name.
- My role: design coordinator, BIM coordinator, BIM modeller or information manager.
- What I want help with. Choose from: requirements, risks, planning, reporting, issues,
model-checks, delivery, meetings.
- Which tools and data the project uses. Choose from: revit, civil3d, openroads, navisworks,
bonsai, ifc, autocad, acc, bcf, ids, bep, relatics, primavera, msproject.
- Whether I'm new to VS Code.
- The language for documents: en (English) or nl (Dutch).
4. Show me what bimai would do, without writing anything:
bimai init --dry-run --yes --name "<project>" --person "<my name>" --role "<role>" \
--goals <goals, comma-separated> --tools <tools, comma-separated> --language <en|nl>
Add --new-to-vscode if I said I'm new to VS Code. Explain the proposed team and why each
member is on it, in a few sentences.
5. Ask me: "Shall I set this up?" Only when I say yes, run the same command without --dry-run.
6. Run: bimai validate
Then tell me to start a new Claude Code session, so my new team is loaded, and give me three
example questions I can ask my team.
If a command fails, show me the error and explain it simply. Don't work around it by editing
bimai's files by hand.What happens
- Claude installs bimai and checks that it works.
- It looks at your folder and asks the questions from the interview. Everything it finds (a BEP, Revit models, a planning export) is suggested as an answer.
- You see your team before anything is written: who is on it, why, and which files bimai would create. Say no, and nothing changes.
- After your yes, bimai writes your project files (
.bimai/), your team (.claude/agents/) and the Coordinator's instructions (CLAUDE.md). It never overwrites files you already have. - Start a new session and your team is there. Ask it something, for example "who is on my team?"
Want to change your team later? See Your team.
Prefer to type it yourself?
pip install "git+https://github.com/StefanDaniels1/BIMAI.git"
cd your-project-folder
bimai initbimai init asks the same questions in the terminal. See
Start a project.
Coming in v0.1: the full installer
Not built yet
What you need
- A Windows or Mac computer. (Revit, Civil 3D and OpenRoads connections only work on Windows, because those programs only run on Windows.)
- A Claude account from your organization.
- An account on your company's git host, usually GitHub or Azure DevOps. IT can arrange this; you'll never have to use git yourself.
Install
Install the bimai program
pipx install bimaiRun the setup
bimai setupSetup checks that git and Claude Code are installed (and installs them if they're missing), signs you in to your git host once, and asks two questions: your language (Dutch or English) and your working hours.
Check that everything works
bimai doctorEverything should be green. If something isn't, the message says what to do.
Where your files are
Everything bimai keeps is in one folder in your user folder, for example C:\Users\anna\bimai.
It's deliberately not in Documents, because Documents is often synced by OneDrive, which doesn't
work well with bimai's project history.
bimai/
├── desk/ private to you: your projects, plans and preferences
└── projects/ one folder per project, shared with that project's team