vibe pull

Usage

vibe pull [remote] [branch] [options]

Description

Pull commits and files from your VibeHub project to your local machine. This syncs your local repository with the remote state.

Arguments

remote

string

Remote name to pull from. Defaults to origin.

branch

string

Branch to pull. Defaults to the current branch.

Options

-f, --force

boolean

Force pull and overwrite local changes. Use with caution.

-d, --dry-run

boolean

Preview what would be pulled without actually pulling.

-p, --project-id

string

Specify a project ID to pull from.

Examples

Basic Pull

vibe pull

Pulls all new commits from the current branch on the connected VibeHub project.

Pull from a Specific Branch

vibe pull origin develop

Pulls commits from the develop branch on the remote.

Preview Changes

vibe pull --dry-run

Shows what would be pulled without making any changes.

Force Pull

Force pulling will overwrite your local changes. Make sure to backup any unsaved work.

vibe pull --force

Branch Workflow

VibeHub CLI uses Git for local branch management. Here’s how to work with branches:

Pull from Current Branch

# Ensure you're on the right branch
git checkout main

# Pull latest changes
vibe pull

Pull from a Different Branch

# Pull from develop branch regardless of current local branch
vibe pull origin develop

Switch Branch and Pull

# Switch to feature branch
git checkout feature/user-auth

# Pull latest changes for that branch
vibe pull

What Gets Pulled

When you pull, you receive:

Content	Included
New commits	Yes
Updated files	Yes
Deleted files	Yes
Commit metadata	Yes
AI prompts	Yes (viewable in VibeHub)

Prerequisites

Before pulling, ensure you have:

Authenticated with vibe login
Initialized your project with vibe init
Connected to a VibeHub project with vibe set <project-url>

Output

A successful pull shows:

📥 Pulling from origin/main...
📥 Pulling all data from VibeHub cloud...
✅ Successfully pulled from VibeHub cloud!
  Total commits: 5
  Total sessions: 2
  Total prompts: 12
💾 Saving cloud data locally...
✅ Successfully added 19 items from cloud to local repository

Handling Conflicts

If your local changes conflict with remote changes:

Warning: Local changes would be overwritten.
Files with conflicts:
  - src/app.js
  - config/settings.json

Use --force to overwrite local changes, or commit/stash them first.

Resolving Conflicts

Backup your changes: Copy modified files elsewhere
Force pull: vibe pull --force
Manually merge: Re-apply your changes to the pulled files

Use Cases

Syncing Multiple Machines

Use pull to get the latest code when switching between computers.

# On your second machine
vibe pull

Getting Team Changes

Pull to receive commits pushed by collaborators.

vibe pull
# Review what changed
vibe status

Pull from Feature Branch

Pull changes from a specific feature branch.

vibe pull origin feature/new-api

Starting Fresh

Force pull to reset your local state to match VibeHub.

vibe pull --force

Error Handling

Not Connected

Error: No project connected. Run 'vibe set <project-url>' first.

Solution: Connect to a project with vibe set.

Not Authenticated

Error: Not logged in. Run 'vibe login' first.

Solution: Authenticate with vibe login.

Access Denied

❌ Access denied
You don't have permission to pull from this project.

Solution: Request access from the project owner.

No Remote Changes

📭 No data found in VibeHub cloud

This means the cloud project is empty or you’re already up to date.

vibe push - Push commits to VibeHub
vibe status - Check sync status
vibe clone - Clone a project

Getting Started

Core Commands

Sync Commands

Branch Commands

Usage

Description

Arguments

Options

Examples

Basic Pull

Pull from a Specific Branch

Preview Changes

Force Pull

Branch Workflow

Pull from Current Branch

Pull from a Different Branch

Switch Branch and Pull

What Gets Pulled

Prerequisites

Output

Handling Conflicts

Resolving Conflicts

Use Cases

Error Handling

Not Connected

Not Authenticated

Access Denied

No Remote Changes

​Usage

​Description

​Arguments

​Options

​Examples

​Basic Pull

​Pull from a Specific Branch

​Preview Changes

​Force Pull

​Branch Workflow

​Pull from Current Branch

​Pull from a Different Branch

​Switch Branch and Pull

​What Gets Pulled

​Prerequisites

​Output

​Handling Conflicts

​Resolving Conflicts

​Use Cases

​Error Handling

​Not Connected

​Not Authenticated

​Access Denied

​No Remote Changes

​Related Commands

Usage

Description

Arguments

Options

Examples

Basic Pull

Pull from a Specific Branch

Preview Changes

Force Pull

Branch Workflow

Pull from Current Branch

Pull from a Different Branch

Switch Branch and Pull

What Gets Pulled

Prerequisites

Output

Handling Conflicts

Resolving Conflicts

Use Cases

Error Handling

Not Connected

Not Authenticated

Access Denied

No Remote Changes

Related Commands