Waymaker init

Overview

Initialize a project directory with Waymaker connection settings. This command connects your local directory to a workspace, project, and taskboard in Commander.

Usage

waymaker init [options]

Prerequisites

• Must be authenticated: waymaker auth login
• Must be part of an organization with at least one workspace

Interactive Flow

When you run waymaker init, you'll be guided through an interactive picker:

cd /path/to/your/project
waymaker init

Step 1: Select Workspace

? Select a workspace:
  Advisory
  My Workspace
> Product
  Support

Step 2: Select Project

? Select a project in "Product":
  Marketing Website
> Commander Development
  Mobile App

Step 3: Select Taskboard

? Select a taskboard in "Commander Development":
> Sprint 42
  Backlog
  Bugs

Result

Initialized Waymaker connection!

Workspace: Product
Project: Commander Development
Taskboard: Sprint 42

Configuration saved to .commander/config.json

Next steps:
  waymaker sync start  - Start syncing files
  waymaker kanban      - View your taskboard
  waymaker serve       - Start MCP server for AI assistants

Configuration File

The command creates .commander/config.json in your project:

{
  "workspace_id": "cd95b528-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "project_id": "0bc85964-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "taskboard_id": "a1b2c3d4-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "workspace_name": "Product",
  "project_name": "Commander Development",
  "taskboard_name": "Sprint 42"
}

Options

Option	Description
--workspace <id>	Skip workspace picker, use this ID
--project <id>	Skip project picker, use this ID
--taskboard <id>	Skip taskboard picker, use this ID
--force	Overwrite existing configuration

Non-Interactive Usage

Skip the interactive prompts by providing IDs:

waymaker init \
  --workspace cd95b528-xxxx \
  --project 0bc85964-xxxx \
  --taskboard a1b2c3d4-xxxx

Useful for scripting or CI/CD pipelines.

Directory Structure

After initialization, your project will have:

your-project/
├── .commander/
│   └── config.json    # Connection configuration
└── ... your files

Git Integration

Add to .gitignore if you don't want to share settings:

.commander/

Or commit it if you want team members to use the same connection:

git add .commander/config.json
git commit -m "Add Waymaker connection config"

Re-Initialization

To change the connected workspace/project/taskboard:

waymaker init --force

This overwrites the existing .commander/config.json.

Troubleshooting

"No workspaces found"

Symptoms: The workspace picker shows no options.

Causes:

• Not authenticated
• Not part of an organization
• Organization has no workspaces

Solutions:

1. Check auth: waymaker auth status
2. Ensure you're in an organization in Commander
3. Create a workspace in Commander first

"No projects found"

Symptoms: The project picker shows no options.

Causes:

• Selected workspace has no projects

Solutions:

1. Create a project in the workspace via Commander
2. Select a different workspace

"Permission denied"

Symptoms: Can't create .commander/ directory.

Solutions:

1. Check you have write permissions in the directory
2. Run from a directory you own

"Already initialized"

Symptoms: Error when running init on initialized directory.

Solutions:

waymaker init --force

Or manually delete .commander/ and run again.

Verifying Initialization

Check your configuration:

cat .commander/config.json

Verify connection works:

waymaker sync status

Related Commands

• auth - Authenticate before init
• sync - Start syncing after init
• kanban - View taskboard after init
• serve - Start MCP server