Forum Topics

A Telegram supergroup can be turned into a forum — one chat with multiple named topics inside it (think of them as channels-within-a-chat). Members post into a specific topic, and /list would be useless if it ignored that structure: a meme-coin topic and a blue-chip topic shouldn’t share the same watchlist.

Prysm scopes group watchlists per topic automatically. This page covers how the scoping works and how /migrate moves existing rows when a group switches forum mode on or off.

How Prysm scopes per topic

Every group token row carries a topic ID. When forum mode is off — or when a token was added in the group’s General area — that ID is null. When a token is added inside a topic, the ID is the topic’s thread number.

/list, /compact, and /detailed read that ID:

• Run from inside a topic, the list filters to tokens whose topic ID matches that topic.
• Run from a non-forum group (or from General in a forum group), the list shows the rows with no topic ID.

That’s the entire mechanism. Each topic effectively has its own slice of the group watchlist, and General has its own slice too.

When a topic ID is captured

The topic is recorded once, on insert. It applies the same way to every entry path:

• /add <contract> in a topic — the new row carries that topic’s thread ID.
• Pasting a contract in Manual Mode — the preview card’s “Add” button writes the topic ID with the row.
• Silent Auto-Track — every silently-captured paste records the topic it came from, just like a manual add.

Once stored, the row stays in that topic until it’s removed (or, for auto-tracked rows, until it expires). Moving a message between topics in Telegram has no effect on rows that are already saved.

Note

Topic scoping only kicks in for forum supergroups. In a regular (non-forum) group, every row’s topic ID is null and /list always shows the full group watchlist. There’s no setting to flip — the behaviour follows Telegram’s forum mode.

What happens when forum mode is toggled

Telegram lets a group admin turn forum mode on or off at any time from the group’s settings. Prysm doesn’t know about the toggle until the next message — and rows that already exist still carry their old topic ID (or null). That’s where /migrate comes in.

/migrate is the bridge that updates existing rows to match the group’s new shape. It’s an admin-only command, and which direction it moves rows depends on where you run it.

Forum mode just turned on

Before forum mode, every token’s topic ID was null. After forum mode is on, those rows still have null IDs and won’t appear in /list from any topic. To bring them back, run /migrate from inside a topic (the General topic works). Prysm moves every null-topic row into the General topic so they’re visible again.

From there, you can keep them in General, or /remove them and re-add the ones you want directly inside the relevant topics.

Forum mode just turned off

Going the other way: rows you added while forum mode was on still have a topic ID, but there are no topics to render them in. Run /migrate from outside any topic (i.e. from the main chat thread of the group, which Telegram treats as non-topic). Prysm flattens every topic-scoped row back to a null topic ID, so a single /list shows them all.

Caution

/migrate is admin-only — only the group’s creator or administrators can run it. Members get a polite refusal. The command also only works in groups; running it in a DM does nothing.

A note on duplicates

If the same token already exists with the destination topic ID, /migrate keeps the existing row and drops the duplicate from the source. You won’t see two copies of the same token in the same topic, and you won’t lose a row by re-running the command.

Example: scoped /list in a forum group

Suppose your group has forum mode on, with two topics: General and Alpha. You’ve added PEPE in General and BONK in Alpha.

Running /list from the General topic shows only the General slice:

📋 Watchlist — #General

Watchlist
Tracking 1 token

🔹 PEPE (Pepe) 🟢 +12.4%
MCap: $5.2M | 📊 DS

Running /list from the Alpha topic shows only Alpha’s slice:

📋 Watchlist — #Alpha

Watchlist
Tracking 1 token

🪙 BONK (Bonk) 🟢 +4.1%
MCap: $1.8B | 📊 DS

Two topics, two completely separate views. Neither topic sees the other’s tokens unless you explicitly add them there too.

Step-by-step: turning forum mode on for an existing group

1. Confirm what you have — run /list in the group while it’s still non-forum. Note the count; that’s the pool of tokens with a null topic ID.

2. Turn on forum mode in Telegram. Group settings → Topics → on. Telegram converts the chat to a forum and creates a General topic.

3. From inside the General topic, run /migrate. Prysm moves every null-topic row into General so your existing list is visible again. Confirmation reply tells you how many rows moved.

4. (Optional) Re-distribute. If some tokens belong in other topics, /remove them from General and re-add inside the topic where they belong. New adds always carry the current topic ID.

Where to next

Silent Auto-Track The default group mode — every paste captured silently, scoped per topic in forum groups.

Manual Mode Preview card on every paste, explicit add, also topic-scoped.

Group Settings Chart provider, sort, price-change period, and other per-group choices.

Watchlists Personal vs group watchlists, with the full picture of how scoping ties into the rest of Prysm.