Core Feature

Tagging System

Tags are the difference between remembering an AI conversation and actually being able to use it again. Folders help you browse. Tags help you retrieve.

The Point of Tags (No Theory)

AI chats fail you later, not in the moment.

You get a great answer, nod, move on… then two weeks later you vaguely remember it existed and can't find it. Tags solve that exact problem.

A tag is just a short label that answers one question: "What is this conversation useful for?"

How Tags Actually Work

Tags are attached to entire conversations, not individual messages.

When you tag a chat:

  • It becomes searchable later
  • It can appear in multiple contexts
  • It stops being tied to browser history

You're turning a disposable chat into a reusable asset.

Adding Tags (The Only Flow That Matters)

You'll usually add tags from the floating menu.

1
Open any supported AI chat
2
Look at the floating Navigator
3
Type a tag
4
Press Enter

Done. No modal. No save button. No ceremony.

This is intentional. Tagging should feel almost unconscious.

Naming Tags Without Overthinking

Tags are lowercase, case-insensitive, and hyphenated if needed.

Examples that work well

architecture bug-fix important research client-alpha

Examples that don't

stuff misc work

If a tag won't help future-you decide why the chat mattered, skip it.

Autocomplete Is Your Friend

As you type, ThinkForge Chat suggests tags you've already used.

This prevents:

  • Duplicate tags
  • Slightly different spellings
  • A bloated tag list

Consistency beats cleverness here.

Removing Tags

Tags aren't permanent.

Click the × on any tag chip to remove it instantly. No confirmation dialog. If it doesn't belong anymore, remove it and move on.

You're allowed to change your mind.

How Tags and Search Work Together

Once you've tagged a few conversations, search becomes fast.

You can:

  • Filter by one tag
  • Combine multiple tags
  • Narrow down to exactly what you're looking for

Think of tags as filters, not folders.

Folders answer "where does this live?"
Tags answer "what is this about?"

Tagging Strategies That Actually Hold Up

By Purpose

decision reference example solution

By Topic

auth database ui deployment

By Project

project-website client-alpha side-project

Pick one or two patterns and stick with them. That's enough.

Tags vs Folders (Use Both, Don't Confuse Them)

Folders are rigid. Tags are flexible.

A conversation can live in one folder, but have many tags.

That's the power.

Example:

Folder: Backend

Tags: auth jwt security important

Later, you don't need to remember where it was filed. You just search what you remember.

Forge Docs and Inherited Tags

When you save part of a conversation as a Forge Doc, its tags can carry over.

That means:

  • Your docs stay connected to their origin
  • Context isn't lost
  • Search keeps working

This matters once your archive grows.

Common Mistakes (Avoid These)

  • Waiting to tag "later"
  • Creating ultra-generic tags
  • Over-tagging everything
  • Trying to design the perfect system

Tag what matters when it matters. Clean it up later if needed.

The Payoff

Once you've tagged 20–30 conversations, something clicks.

You stop asking: "Didn't I already solve this?"

And start answering it in seconds. That's the whole point.