[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[Feedback](/c/feedback/8)

# No CLI docs for how to pull env from specific project

104 views · 1 like · 2 posts


Paul Berg (@prberg) · 2025-04-18

The `vercel pull` command is capable of retrieving project-specific information when the `VERCEL_PROJECT_ID` environment variable is set. However, Vercel users are not informed about this functionality. Running `vercel pull --help`, there's no information about this:

<details><summary>Toggle to see command output</summary>
<p>

Vercel CLI 41.4.1

  ▲ vercel pull [project-path] [options]

  Pull latest environment variables and project settings from Vercel.                                                      

  Options:

       --environment <TARGET>  Deployment environment [development]                                                             
       --git-branch <NAME>     Specify the Git branch to pull specific Environment Variables for                                
  -y,  --yes                   Skip questions when setting up new project using default scope and settings                      


  Global Options:

       --cwd <DIR>            Sets the current working directory for a single run of a command                             
  -d,  --debug                Debug mode (default off)                                                                     
  -Q,  --global-config <DIR>  Path to the global `.vercel` directory                                                       
  -h,  --help                 Output usage information                                                                     
  -A,  --local-config <FILE>  Path to the local `vercel.json` file                                                         
       --no-color             No color mode (default off)                                                                  
  -S,  --scope                Set a custom scope                                                                           
  -t,  --token <TOKEN>        Login token                                                                                  
  -v,  --version              Output the version number                                                                    


  Examples:

  - Pull the latest Environment Variables and Project Settings from the cloud

    $ vercel pull

  - Pull the latest Environment Variables and Project Settings from the cloud targeting a directory

    $ vercel pull ./path-to-project

  - Pull for a specific environment

    $ vercel pull --environment=<production | preview | development>

  - Pull for a preview feature branch

    $ vercel pull --environment=preview --git-branch=feature-branch

  - If you want to download environment variables to a specific file, use `vercel env pull` instead

    $ vercel env pull


</p>
</details> 

As you can see, there's no guidance about `VERCEL_PROJECT_ID`.

I also think that a `--project` flag might be helpful. When this flag is set, it overrides the environment variable.


Swarnava Sengupta (@swarnava) · 2025-04-18 · ♥ 1

Hey Paul,

Thank you for your sharing the feedback. I think it's a fair ask, :) I have passed it to the relevant team.