# Built-in Tag Intersection Navigator

**URL:** https://meta.discourse.org/t/built-in-tag-intersection-navigator/395466
**Category:** Feature
**Created:** [February 8, 2026, 12:04pm UTC](https://meta.discourse.org/t/built-in-tag-intersection-navigator/395466 "2026-02-08T12:04:40Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![mhawash](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mhawash/32/542302_2.png) [@mhawash](https://meta.discourse.org/u/mhawash)
#### Post date: [February 8, 2026, 12:04pm UTC](https://meta.discourse.org/t/built-in-tag-intersection-navigator/395466/1 "2026-02-08T12:04:40Z")

</div>

Discourse would greatly benefit from a built-in **Tag Intersection Navigator** , similar to the one developed by @merefield

Tag intersections are a core navigation feature in many modern forum platforms including Discord, Nodebb and more. Supporting this natively would significantly improve content discovery, filtering precision, without relying on custom implementations or plugins.

Making this a first-class feature would align Discourse with common forum UX expectations and enhance the experience for communities that rely heavily on structured tagging.

It could be something like (relative to category tags):

 ![Discord_KhzayB6Mft](https://global.discourse-cdn.com/meta/original/4X/9/8/d/98d9b7aa038a7cec553c5bb4ea4a2d0bf514fa8e.png)

Thank you.

---

<div class="post-metadata">

### Author: ![mhawash](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mhawash/32/542302_2.png) [@mhawash](https://meta.discourse.org/u/mhawash)
#### Post date: [February 8, 2026, 12:06pm UTC](https://meta.discourse.org/t/built-in-tag-intersection-navigator/395466/2 "2026-02-08T12:06:09Z")

</div>

Example: [Tag Intersection Navigator](https://meta.discourse.org/t/tag-intersection-navigator/368815)

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [February 8, 2026, 12:10pm UTC](https://meta.discourse.org/t/built-in-tag-intersection-navigator/395466/3 "2026-02-08T12:10:53Z")

</div>

Have you tried the #topic-filter at [/filter](https://meta.discourse.org/filter)? You can use it to search for topics with at least one of the tags, all of the tags, or none of the tags.

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [February 8, 2026, 12:11pm UTC](https://meta.discourse.org/t/built-in-tag-intersection-navigator/395466/4 "2026-02-08T12:11:15Z")

</div>

Just to be fully clear my plugin extends and improves the existing tag intersection functionality and UI but there is already some support already.

---

<div class="post-metadata">

### Author: ![mhawash](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mhawash/32/542302_2.png) [@mhawash](https://meta.discourse.org/u/mhawash)
#### Post date: [February 8, 2026, 12:16pm UTC](https://meta.discourse.org/t/built-in-tag-intersection-navigator/395466/5 "2026-02-08T12:16:27Z")

</div>

I know about that, but that’s a different thing and not as user friendly as to just pressing multiple tags on the category you’re in to narrow down the topics list in real-time for what you actually care for under that specific category.

---

<div class="post-metadata">

### Author: ![mhawash](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mhawash/32/542302_2.png) [@mhawash](https://meta.discourse.org/u/mhawash)
#### Post date: [February 8, 2026, 12:19pm UTC](https://meta.discourse.org/t/built-in-tag-intersection-navigator/395466/6 "2026-02-08T12:19:31Z")

</div>

> [@merefield](#):
>
> Just to be fully clear my plugin extends and improves the existing tag intersection functionality and UI but there is already some support already.

Yup, and that’s the point, it’s already there! just we need little UI/UX modifications to make it happen! Yet, it should be provided as a core plugin.
