# Oops! wp-cli updated automatically for non-wp site

**URL:** <https://community.localwp.com/t/oops-wp-cli-updated-automatically-for-non-wp-site/576>\
**Category:** Uncategorized\
**Created:** [January 24, 2017, 12:35am UTC](https://community.localwp.com/t/oops-wp-cli-updated-automatically-for-non-wp-site/576 "2017-01-24T00:35:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![NdnaJnz](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/ndnajnz/32/4435_2.png) [@NdnaJnz](https://community.localwp.com/u/NdnaJnz)\
**Post date:** [January 24, 2017, 12:35am UTC](https://community.localwp.com/t/oops-wp-cli-updated-automatically-for-non-wp-site/576/1 "2017-01-24T00:35:21Z")

</div>

Hmm… Under Local 1.4.1, I am continuing development of a non-WP Web app. Running fine - mostly. I got stuck in a PHP loop of some sort and went to restart the site and saw a notice of “WP-CLI was out of date for this site. It has been automatically updated.”

I don’t see any evidence of that. Does each site/container actually have its own install of WP-CLI (I assume it does.) I don’t see WP-CLI anywhere in there.

And of course, Local KNOWS if WP is not installed in this site so should probably not update WP-CLI. Or even check for it.

 ![](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/1X/3dfe25d3eb63b65954dc577f132856dd1e0870c4.png)

---

<div class="post-metadata">

**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\
**Post date:** [November 19, 2025, 5:27pm UTC](https://community.localwp.com/t/oops-wp-cli-updated-automatically-for-non-wp-site/576/2 "2025-11-19T17:27:31Z")

</div>

Closed on November 19, 2025, 5:27pm UTC