# Discourse Events

**URL:** https://meta.discourse.org/t/discourse-events/97376
**Category:** Plugin
**Tags:** official, events, included-in-core
**Created:** [September 17, 2018, 3:50pm UTC](https://meta.discourse.org/t/discourse-events/97376 "2018-09-17T15:50:24Z")
**Posts on this page:** 1
**Showing post:** 577

<div class="post-metadata">

### Author: ![oshyan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/oshyan/32/212644_2.png) [@oshyan](https://meta.discourse.org/u/oshyan)
#### Post date: [May 3, 2026, 6:32pm UTC](https://meta.discourse.org/t/discourse-events/97376/577 "2026-05-03T18:32:43Z")

</div>

> [@gilles](#):
>
> In my opinion, it would be better to implement a complete event management system with parameters to enable or disable event modules to meet everyone’s needs. Currently, you always have to add different plugins to fulfill a request, so a very comprehensive plugin can only be beneficial for everyone 😅.

That’s more or less what I intend. I want to make different functions configurable and enable/disable in settings, within reason. I haven’t designed the plugin as modular from the beginning, perhaps I should have. But the functions are interconnected enough and I didn’t want to have it require its _own_ plugins.

I use both Codex (OpenAI) and Claude (Anthropic, of course), both directly rather than through alternative harnesses/environments like Cursor. I get better use out of my subscription dollars this way, and in general I haven’t found the short-term advantages of other tools to make up for their various downsides. Staying in each respective company’s own native coding tools and ecosystem has served me better and better over time, and I use MCPs and skills to make up the difference (e.g. experimenting with novel memory skills backed by on-disk markdown files, or ygrep for file search, etc.).

---

_[View the full topic](https://meta.discourse.org/t/discourse-events/97376)._