Skip to main content

​
Usage

vibe fetch [remote] [options]

​
Description

Download branches and their commit references from the remote VibeHub project. This updates your local knowledge of remote branches without modifying your working files.
Unlike vibe pull, fetch only downloads metadata and doesn’t merge changes into your working branch.

​
Arguments

​
remote
string
Remote name to fetch from. Defaults to origin.

​
Options

​
--all
boolean
Fetch from all remotes.
​
--prune
boolean
Remove remote-tracking references that no longer exist on the remote.
​
-v, --verbose
boolean
Show detailed output including all remote branches.

​
Examples

​
Basic Fetch

vibe fetch
Output: 
Fetching from origin...

Fetch complete.
  Remote branches: 5
  Last fetch: 1/25/2026, 2:30:45 PM

​
Fetch with Details

vibe fetch -v
Output: 
Fetching from origin...

Found 5 remote branch(es):
* origin/main -> abc1234
  origin/develop -> def5678
  origin/feature/auth -> ghi9012
  origin/feature/api -> jkl3456
  origin/hotfix/security -> mno7890

Fetch complete.
  Remote branches: 5
  Last fetch: 1/25/2026, 2:30:45 PM

Current branch 'main':
  Remote head: abc1234

​
When to Use Fetch

Use vibe fetch when you want to:
  • See what branches exist on the remote
  • Check if there are new commits before pulling
  • Update your local reference of remote branches
  • Prepare for a merge without affecting your working files

​
Fetch vs Pull

CommandDownloads DataUpdates Working FilesMerges Changes
vibe fetchYesNoNo
vibe pullYesYesYes

​
Typical Workflow

# First, see what's changed on remote
vibe fetch -v

# Check the differences
vibe diff main..origin/main

# If you want the changes, pull them
vibe pull

​
Error Messages

​
Not Connected

Not connected to VibeHub cloud
Run 'vibe set <project-url>' to connect to a cloud project
Solution: Connect your repository to a VibeHub project first.

​
Network Error

Failed to fetch: Network error
Solution: Check your internet connection and try again.