Documentation
waymaker init
cd /path/to/your/project
waymaker init
What it does
Writes an empty .commander/config.json in the current directory and prints next steps. That's
it — there's no interactive workspace/project/taskboard picker; the config file starts empty and
gets filled in as you use other commands.
✓ Waymaker CLI initialized
Config file: /path/to/your/project/.commander/config.json
ℹ Next steps:
ℹ 1. Set your API key: export WAYMAKER_API_KEY=wm_sk_...
ℹ 2. Select a workspace: waymaker workspaces use <id>
ℹ 3. Start creating resources: waymaker tables create ...
Running it again in an already-initialized directory is a no-op — it warns and shows the existing config path rather than overwriting it.
After init
waymaker workspaces list
waymaker workspaces use <workspaceId>
waymaker projects list
waymaker projects use <projectId>
Selecting a workspace/project this way is what actually sets your working context — init itself
only creates the file that holds it.
If you're setting up sync
waymaker init on its own doesn't configure sync — that's a separate step:
waymaker sync configure --workspace <id> --project <id> --taskboard <id>
See Project Organization.