bimaiReference
Commands
Every bimai command, in the terminal and in a Claude Code session.
Not built yet
Planned for v0.1. This page describes the target experience; commands may not exist yet. Already available:
bimai validate, bimai init, bimai team, bimai connect and bimai auth (see Checking your files).In a session (Claude Code)
| Command | Does |
|---|---|
/bimai:onboard | Run or re-run the onboarding interview |
/bimai:plan | Plan my day across all projects |
/bimai:meeting | Process a meeting transcript into minutes and tasks |
/bimai:meeting-prep | Build a coordination meeting agenda |
/bimai:triage | Triage open ACC issues |
/bimai:report | Weekly design progress report |
/bimai:delivery-check | Check a model against the delivery checklist |
/bimai:approve | Review changes and proposals waiting for approval |
/bimai:private | Leave this session out of the shared journal |
/bimai:new-connector · new-pack · new-workflow · new-automation | Build on bimai |
/bimai:certify · /bimai:register | Test and register what you built |
You can also just ask in plain language; the Coordinator picks the right workflow.
Getting started
| Command | Does |
|---|---|
bimai setup | Install check, sign-in, create your desk (once per computer) |
bimai new <name> | Start a project: repository, onboarding, BEP |
bimai new --demo | Create the demo project |
bimai init | Add bimai to an existing folder or repository (available now) |
bimai join <link> | Join a colleague's project |
bimai invite <email> | Give a colleague access |
bimai open [project] | Open your desk or a project in VS Code |
bimai doctor | Check the setup and explain what's wrong |
bimai status | Workflows running, approvals waiting, connector health |
Team, positions and people
| Command | Does |
|---|---|
bimai team | Update your Claude Code team after editing seat.yaml (available now) |
bimai team review | Suggest adding or removing team members |
bimai onboard --update | Re-run the interview after a role or phase change |
bimai position add <id> | Add a position, e.g. a modeller for zone B |
bimai position assign <id> --to <person> | Give a position to someone |
bimai cover <id> --by <person> --until <date> | Temporary cover for absence |
bimai transfer <id> --to <person> | Permanent handover |
bimai seat leave | Leave a project |
bimai activity --since <day> | What the team did, from the session journals |
Project knowledge
| Command | Does |
|---|---|
bimai bep import <file> · bimai bep diff | Read a BEP (revision) into agreements |
bimai data import <file> · list · diff | Relatics and planning exports |
bimai meeting import <file> | Process a meeting transcript |
bimai learn promote | Propose a learning as a shared rule |
bimai site build · open · publish | Build, open or privately publish the project site |
Tasks and projects
| Command | Does |
|---|---|
bimai tasks add · done · list | Manage tasks |
bimai tasks due --days 7 | Upcoming and overdue work |
bimai tasks plan --day | Fit tasks into your day |
bimai tasks assign | Give someone a task (used by meeting intake) |
bimai projects list · status · set | Your projects |
Saving and history
| Command | Does |
|---|---|
bimai save · bimai sync · bimai restore | Run automatically; available if you want them |
bimai desk backup --remote <url> | Back up your desk |
Workflows and automations
| Command | Does |
|---|---|
bimai workflow run · plan · status · resume | Run and inspect workflows |
bimai run <automation> | Run an automation now |
bimai schedule install · export --github | Schedule it |
Connections and security
| Command | Does |
|---|---|
bimai connect · bimai connect <server> | List the servers your team can use, or connect one (Connections) (available now) |
bimai disconnect <server> | Remove a server, its approval rule and its sign-in (available now) |
bimai bridge install · status · uninstall | Install, check or remove a bimai bridge such as the Civil 3D bridge (available now) |
bimai auth login · status · logout | Sign in to a server, see what needs signing in, sign out (available now) |
bimai auth rotate | Replace a key and revoke the old one |
bimai connector new · record · test | Build and test connectors |
bimai graph team · workflow · connectors · project · projects | Draw diagrams |
bimai validate | Check every bimai file (available now) |
bimai update · update --check | Update bimai itself, or only check for a new version (available now) |
bimai upgrade | Update bimai files; never touches your decisions or history |
bimai nap | Compact agent learnings and archive or anonymize old logs (retention) |
bimai lint | Check that outputs cite evidence and decisions are logged (runs automatically) |
bimai hook <name> | Used by Claude Code hooks; not for everyday use |
Checking your files
bimai validate checks every file in a project's .bimai/ folder: that each one has the right
fields, that the people and positions they mention exist, and that workflows have no missing steps
or loops. It never changes anything.
curl -LsSf https://docs.bimai.nl/install.sh | sh # Windows: powershell -ExecutionPolicy ByPass -c "irm https://docs.bimai.nl/install.ps1 | iex"
bimai validate # the project in the current folder
bimai validate ../bridge-3 # or another projectWhen something is wrong, each problem is one line: the file, where in the file, and what's wrong.
.bimai/ownership.yaml: cover.0.until: '9 oktober' is not a 'date'
.bimai/project.yaml: 'id' is a required property
.bimai/workflows/weekly-coordination.yaml: steps.cluster.needs: step 'fetch-isues' does not exist
3 problems found| Exit code | Means |
|---|---|
| 0 | Everything is valid |
| 1 | Problems were found |
| 2 | No bimai project in that folder |
Add --json to get the result as {"valid": …, "problems": [{"file", "location", "message"}]},
for scripts and CI.