Skip to main content

​
Usage

vibe pull [options]

​
Description

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

​
Options

​
--force
boolean
Force pull and overwrite local changes. Use with caution.
​
--dry-run
boolean
Preview what would be pulled without actually pulling.
​
--project-id
string
Specify a project ID to pull from.
​
--branch
string
Specify which branch to pull from (defaults to current branch).

​
Examples

​
Basic Pull

vibe pull
Pulls all new commits from the connected VibeHub project.

​
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

​
What Gets Pulled

When you pull, you receive:
ContentIncluded
New commitsYes
Updated filesYes
Deleted filesYes
Commit metadataYes
AI promptsYes (viewable in VibeHub)

​
Prerequisites

Before pulling, ensure you have:
  1. Authenticated with vibe login
  2. Initialized your project with vibe init
  3. Connected to a VibeHub project with vibe set <project-url>

​
Pull Workflow

​
Output

A successful pull shows: 
Pulling from vibehub.co.in/username/project-name...
✓ 2 new commits
✓ 8 files updated
✓ 1 file deleted
Pull complete!

​
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

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

​
Use Cases

Use pull to get the latest code when switching between computers.
# On your second machine
vibe pull
Pull to receive commits pushed by collaborators.
vibe pull
# Review changes
git log
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.

​
No Remote Changes

Already up to date.
This is normal - it means your local copy matches VibeHub.