Vibe Coding Machine CLI

Vibe Coding Machine command-line interface for managing repositories, auto mode, requirements, IDE actions, and status.

Install

From the monorepo root:

npm install
# optional: link locally for global access
npm run --workspaces --if-present build
npm link ./packages/cli

Then run vibecodingmachine or vcm (short version).

Note: The vcm shortcut will only be installed if you don't already have another vcm command on your system. If a conflict is detected, you can still use the full vibecodingmachine command.

Usage

vibecodingmachine --help   # or: vcm --help (if installed)
vibecodingmachine -v       # or: vcm -v (if installed)

Note: You can use either vibecodingmachine or vcm - they're the same command!

Repository

vcm repo:init                 # initialize .vibecodingmachine in CWD and set repo
vcm repo:set /path/to/repo    # set active repository
vcm repo:get                  # print current repo path

Auto Mode

vcm auto:start --ide cursor --max-chats 10
vcm auto:status
vcm auto:config --max-chats 25 --never-stop
vcm auto:stop

Requirements

vcm req:list
vcm req:add "Build initial CLI MVP"
vcm req:current
vcm req:next
vcm req:edit
vcm req:watch

IDE

vcm ide:list
vcm ide:open cursor           # or vscode, windsurf
vcm ide:send "Summarize failures" -i cursor

Status

vcm status
vcm progress
vcm logs -n 100

Interactive

vcm interactive

Configuration

• Stored at ~/.config/vibecodingmachine/config.json by default
• Override for testing with env var VIBECODINGMACHINE_CONFIG_PATH=/tmp/your-test-config.json

Development

# format and lint
npm run -w @vibecodingmachine/cli format
npm run -w @vibecodingmachine/cli lint

# tests
npm run -w @vibecodingmachine/cli test