# Feedback Wanted: Manage Plugin Dialog

**URL:** <https://discuss.avogadro.cc/t/feedback-wanted-manage-plugin-dialog/7509>\
**Category:** Design & Interface\
**Created:** [August 29, 2026, 12:18am UTC](https://discuss.avogadro.cc/t/feedback-wanted-manage-plugin-dialog/7509 "2026-08-29T00:18:30Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![ghutchis](https://discuss.avogadro.cc/user_avatar/discuss.avogadro.cc/ghutchis/32/456_2.png) [@ghutchis](https://discuss.avogadro.cc/u/ghutchis)\
**Post date:** [September 18, 2026, 11:08pm UTC](https://discuss.avogadro.cc/t/feedback-wanted-manage-plugin-dialog/7509/8 "2026-09-18T23:08:56Z")

</div>

Flagging plugins for updates is probably a good idea. I’ll need to think a bit because some cases may be an updated plugin for a new version. For example the next update of `generators` will include support for z-matrix coordinates. But that’ll require v2.1 of Avogadro.

I’d probably go for the two levels you mentioned:

- no automated check (current behavior, only show when you open the window)
- some sort of opt-in notification that there are updated plugins to install

I’m pretty reluctant to use automatic updates - in part because I’d hate to break someone’s workflow. 🙂

> [@Thomas](#):
>
> - I would prefer if this level were be an explicit opt-in by the user.

Oh, everything would be opt-in. As I mentioned [elsewhere](https://discuss.avogadro.cc/t/testers-needed-windows-crash-reporting/7499/2), there’s a new build for Windows with crash reporting built-in. But IMHO, that won’t be the default build for Windows and you still need to opt-in at startup for it.

---

_[View the full topic](https://discuss.avogadro.cc/t/feedback-wanted-manage-plugin-dialog/7509)._