Skip to main content

Usage

Description

Initialize a new VibeHub repository in the current directory. This sets up the necessary configuration for syncing with VibeHub.

What It Does

When you run vibe init, the CLI:
  1. Creates a .vibehub directory in your project
  2. Generates a local configuration file
  3. Prepares the project for pushing to VibeHub

Options

--name
string
Specify a project name (optional)
--description
string
Add a project description (optional)

Examples

Basic Initialization

Initialize with Name

Initialize with Description

Directory Structure

After initialization, your project will have:
The .vibehub directory contains local configuration. You may want to add it to .gitignore.

Next Steps After Init

After initializing, you typically:
  1. Create a VibeHub project (if you haven’t already):
  2. Connect to the project:
  3. Push your code:

Common Workflows

New Project from Scratch

Existing Project

Re-initializing

If you need to reinitialize (e.g., after deleting .vibehub):
This creates a fresh configuration. You’ll need to run vibe set again to connect to your project.

Troubleshooting

Already Initialized

If the project is already initialized:
  • The command will notify you
  • Your existing configuration is preserved
  • Use vibe status to check current state

Permission Denied

If you can’t create the .vibehub directory:
  • Check you have write permissions in the current directory
  • Ensure you’re not in a read-only location