Last verified: September 19, 2026
What You Can Now Do
Context Memo now shows live counts on every tag chip in the memo builder, and clicking a tag opens a filtered list of memos carrying that tag in a new browser tab. The count updates as your library changes, so a tag reading 14 tells you fourteen published or draft memos already cover that theme before you commit to writing a fifteenth. That changes one specific decision: whether the memo in front of you is new coverage or a near-duplicate of something you already published. Instead of guessing, you glance at the chip, open the filtered view, and confirm.
Where It Is in Context Memo
The tag chips live in the memo builder, on the tag field of the memo you have open. Each chip now carries its count inline. The filtered list opens in a new tab, which means your draft stays exactly where it was: same scroll position, same unsaved edits, same editor state. Nothing is lost by checking.
How to Use It
- Open any memo in the memo builder and look at the tag field. Each tag chip displays its current count next to the label.
- Scan the counts before you write. A tag showing a high count signals a well-covered theme; a tag showing 1 or 2 signals a thin area where a new memo adds real coverage.
- Click a tag chip. Context Memo opens a new tab with every memo carrying that tag, filtered and listed.
- Review that list for overlap. If a memo already answers the prompt you were about to target, close the tab and pick a different angle, or update the existing memo instead.
- Return to your original tab. Your draft is untouched. Add or remove tags on the memo you are building, and the counts reflect the change.
- Repeat the check when you assign tags to a batch of auto-generated memos, so clusters stay balanced instead of piling onto one theme.
Why We Built It
The request came in plainly: "I need to quickly see how many memos have a given tag and filter to just those memos without navigating away from my current view." The cost of not having it was small each time and large in aggregate. You left the builder, went to the memo index, applied a filter, read the results, then navigated back and rebuilt your place in the draft. Some people did that check. Most skipped it, and the result was uneven coverage: four memos on one topic cluster, none on an adjacent one that buyers were actually prompting about.
Tag counts turn that check into a glance. Coverage depth becomes something you see while you work rather than something you audit afterward.
What It Does Not Do Yet
The filtered list opens in a new tab rather than as an in-page panel or modal. That is deliberate for now: a new tab guarantees your draft state survives the detour, with no risk of an editor reload dropping unsaved work. If your workflow favors staying in a single tab, the memo index still supports tag filtering directly.
A few other limits worth knowing:
- Counts reflect tag assignment, not citation performance. A tag with 20 memos behind it is not automatically your strongest theme. For that read, use citation tracking and share of voice, which measure whether those memos are actually being cited across the models you scan.
- No multi-tag intersection from the chip. Clicking a chip filters on that single tag. Narrowing to memos that carry two tags at once is not available from the builder.
- No count thresholds or alerts. Context Memo will not flag a tag as over- or under-covered. The number is there; the judgment is yours.
Tag hygiene still pays off here. Counts are only as useful as your taxonomy, so near-duplicate tags ("ai-search" and "ai search") will split a count across two chips and understate real coverage. If your library grew organically, consolidating tags first will make the numbers worth trusting.