# Upcoming CLI Breaking Change

**URL:** <https://community.limacharlie.com/t/upcoming-cli-breaking-change/599>\
**Category:** Announcements\
**Tags:** cli\
**Created:** [February 16, 2026, 5:40pm UTC](https://community.limacharlie.com/t/upcoming-cli-breaking-change/599 "2026-02-16T17:40:02Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![maximelb](https://yyz1.discourse-cdn.com/flex033/user_avatar/community.limacharlie.com/maximelb/32/13_2.png) [@maximelb](https://community.limacharlie.com/u/maximelb)\
**Post date:** [February 16, 2026, 5:40pm UTC](https://community.limacharlie.com/t/upcoming-cli-breaking-change/599/1 "2026-02-16T17:40:02Z")

</div>

Hello, although we’re not currently ready to release a new version of our CLI ( [GitHub - refractionPOINT/python-limacharlie: Python API for the LimaCharlie.io service.](https://github.com/refractionPOINT/python-limacharlie/) ), we are working on this next version: [GitHub - refractionPOINT/python-limacharlie at cli-v2](https://github.com/refractionPOINT/python-limacharlie/tree/cli-v2)

In order to prevent any adverse effect when we release it, we strongly suggest pinning the version of the python SDK/CLI you’re using to the current major release of `4.x.x`. This will prevent the backward-compatible breaking changes from popping up automatically for you.

You can do this by using the package definition: `limacharlie~=4.0`.

This way when we release `5.0.0` it won’t be automatically picked up by your code.

The new CLI version will be a major overhaul of the CLI to make it better, complete, maintainable and more discoverable by AI.

Please do give us feedback as usual.

Cheers

---

_[View the full topic](https://community.limacharlie.com/t/upcoming-cli-breaking-change/599)._
