The engine that posts
Neurocommenting
Set up AI comments on Telegram channels: the pool and daily limits, channels and folders, persona, the Settings section, and the ramp for new accounts.
01What it does
Neurocommenting watches the channels you list. When a new post appears, an account from your pool writes a comment with AI, waits a human-like delay and posts it.
It needs three things: accounts in the pool, channels to watch, and an active persona (the prompt the comments are written with).
02Set it up
Prepare the accounts first: one week of Active Warmup and the protection steps. Brand-new accounts that start commenting at once are the fastest way to lose them.
Add accounts to the Commenting Pool: the arrow on a row moves one account; tick several to move them together.
Set a daily limit. For new accounts start at 3 (see Daily limit).
Add channels: Channels → Add channel(s), one @username or t.me link per line. Or press Start commenting on rows in Channel Parser.
Press Auto-assign channels, so every channel has an account that handles it.
Pick a persona. Copy the closest built-in and edit the copy.
Leave the delay at Recommended (480–1500 s) and press Start. If accounts, channels or a persona are missing, a preflight dialog lists what is missing before anything runs.
Before step 1: Active Warmup and Account Protection.
03Start, sessions and Auto-continue

Start connects the accounts in the pool (this can take a couple of minutes; Cancel start stops it) and begins watching the channels. Changes to the pool, the channel list, the delay and limits are picked up on the next round, about once a minute. You do not need to restart.
| Control | What it does |
|---|---|
| Session cap | A session runs for up to 10 hours, then the engine stops itself cleanly. The bar shows how far it is and when it ends. |
| Auto-continue | On (default): after the session the engine takes a random break of 90 to 210 minutes and starts the next session by itself. The panel shows “Between sessions — the next one starts …”. Off: it stays stopped until you press Start. |
| Stop | Ends the session. Comments still waiting out their delay are cancelled and their posts go back in the queue for later. |
| Warmup | Off by default. When on, each account starts at 1 comment an hour and 3 a day and climbs to full speed over 14 days from when it was added. This is separate from the daily limit and from the Active Warmup module. |
| Delay before commenting | The random wait between writing a comment and posting it. Recommended 480–1500 s (8–25 min). Presets fill the fields; Save applies them. |
| Engine logs | Live log of what the engine decides. Open it when something looks wrong. |
If the engine is Running but nobody can post, an amber line under the bar says why (accounts paused, in cooldown, at their pace limit and so on). “Done for today” is not a fault: every account has used its daily limit and they come back after 00:00 UTC.
A server restart does not stop a running engine. It starts again by itself a minute or two after the service is back.
04Pool and daily limit

An account works in one module at a time. If another module (NeuroDialogs, Mass Reactions, Active Warmup) holds it, or it is still in its Supervise rest, it is refused with the reason. The rest of the batch is still added. Removing an account from the pool frees it at once.
The comment limit is a daily limit. It counts successful comments since 00:00 UTC and each row reads “N of M today”. An account that reaches it stops for the day and resumes by itself shortly after 00:00 UTC. The engine keeps running meanwhile and carries on after midnight.
| Control | What it does |
|---|---|
| Set limit | Type a number and press Enter or the tick. Applies to every account in the pool. There is no limit until you set one. |
| Clear limits | Removes the limit from every pooled account. |
| Reset counts | Sets today’s count back to zero for the ticked accounts, so they can post again before midnight. Comment history is kept. |
| Pause / Resume | Takes one account out of posting until you resume it. Nothing automatic ever resumes a manual pause. |
| Auto-assign channels | Deals the whole channel list evenly across the pool, replacing old assignments. |
| Shuffle channels | Gives every account a different set of the channels already assigned, same number each. |
| Clear assignments | Removes all assignments. Posting continues: any free pool account takes the post. |
Assignment is a preference. If the assigned account cannot post right now (cooldown, paused, at its limit), another account from the pool takes the post. Accounts outside the pool are never used.
Ramp for new accounts: after a week of warmup and protection, start Neurocommenting at 3 comments per account per day and raise the daily limit by 1 every day (3, 4, 5, …). Use Set limit once a day to raise it.
05Channels
The channel list is what the engine watches. Every change saves immediately and is picked up on the next round.
| Control | What it does |
|---|---|
| Add channel(s) | Paste channels, one per line: @username, t.me link or bare username. Duplicates and invalid lines are reported, not added. |
| Clear all | Empties the list (asks first). Assignments, blacklist, history and presets stay. |
| Save Preset | Saves the current list under a name. Load on a preset card replaces the list with it. |
A post is only commented if it has text and comments switched on. When a discussion group needs the account to join first, the account joins before writing. A group that approves members by hand gets a join request, and another account takes the post meanwhile.
06Working by folders
A Telegram folder (a t.me/addlist link) holds up to 100 channels. Joining it is one request that puts an account into all of them. With Work by folders on, pool accounts get their channels this way instead of joining channels one by one.
Save your channel list as a preset (Channels → Save Preset).
Channels → Folders → Create folders. Pick the preset and a creator account. The creator must be outside the commenting pool and stays in the channels to keep the folders alive. A large preset may need a second or third creator; the dialog says so.
Confirm. The creator joins the preset’s channels one by one, 20 to 60 seconds apart with a 2 to 5 minute pause every 20 joins. Channels it is already in are skipped, and several creators work in parallel. The dialog shows an estimate; you can close the page.
Wait until the folder cards read Ready. A progress bar shows the build.
In the Pool, switch Work by folders on and press Auto-assign channels. It shows how many accounts go to each folder and how many joins that means, and waits for Assign & join.
Accounts join their folder in the background and start commenting in its channels as soon as they are in.


- Copy a folder link, but do not open it in your own Telegram: it offers to add your own account to every channel in it.
- While a creator builds, it counts as In work in Account Manager and cannot be put in any module.
- Delete on a card removes the folder and its link. Accounts leave the folder but stay in its channels.
- Shuffle with folders on asks whether to reshuffle channels within the same folders or move accounts to new folders.
07Blacklist and deletion control

| Category | When a channel is listed |
|---|---|
| Channels with no successful comments | At least 5 attempts from at least 2 accounts in the last 30 days, and not one comment published. The row shows the attempts, the accounts and the most common reason. |
| Comments deleted | Only while Comment deletion control is on: your comments were found removed from the thread. The X on a row forgets those deletions. |
Comment deletion control (off by default): about an hour after each comment, the account that posted it checks the thread. If the comment is gone, the channel is listed. It costs one read per comment. A deleted post or lost access does not count as a deletion.
Remove channels stops watching every ticked channel, after a confirmation, and also removes them from your presets and folders. Comment history stays. Nothing is removed automatically; you decide.
08Model and persona
Model picks which AI writes the comments. The default is Grok 4.3. The choice applies from the next comment and is separate from the NeuroDialogs model.
| Model | In short |
|---|---|
| Grok 4.3 | Default. Declined every sensitive post in our test. Writes the shortest comments. |
| Gemini 3.5 Flash-Lite | The cheapest model that also declined sensitive posts. |
| Claude Haiku 4.5 | Writes the longest comments. The most expensive per token. |
| Kimi K2.6 | Works, but costs about 70 times the cheapest model per comment and is slow. |
| GPT-4o mini | Cheapest, but it commented on about one in four sensitive posts in our test. Only for channels where nothing sensitive is posted. |

A persona is a name and a prompt you write. The six built-ins can be read and copied but not edited; your own go under My Prompts. Clicking a card makes it active from the next comment.
- Tokens you can use in the prompt: {post_text}, {channel_title}, {account_username}, {account_first_name}.
- Tell the model when to skip. The built-ins end with “reply with the literal token SKIP” when the post does not fit. Without such a line it comments on everything.
- Don’t comment on sensitive content (on by default) tells the model to skip posts about death, violence, war, disasters, mourning and politics. Turning it off asks for confirmation and lasts 7 days, then it switches back on. A separate check before writing always runs, whatever this switch says.
09Settings
The // Settings section at the bottom of the page, after Persona, holds three blocks: AI Protection, AI Autoreply and Advanced settings. The (i) next to each name explains it.

AI Protection. While an account works, it also does what a person does in Telegram now and then: reads chats and channels, scrolls, looks at posts and stories, looks through its settings, likes a post, archives a chat. Off, Low, Medium (default) or High sets how often: about every 25, 10 or 4 minutes per working account. It only uses the account’s own chats on the connection the engine already has, never looks up usernames or joins anything, and never touches private chats. A like counts toward the pace limit. The (i) shows how many actions were made in the last 24 hours.
The same switch is on NeuroDialogs and Mass Reactions: AI Protection across the modules.
AI Autoreply (off by default). When someone sends a private message to one of your commenting accounts, the account answers once with your text.
| Setting | What it does |
|---|---|
| Switch | Turns it on. Write the reply text first; an empty text cannot be switched on. |
| Reply text | Sent exactly as written (up to 1,000 characters). Saved when you leave the field. |
| Reply delay, minutes | A random wait between the two numbers, counted from when the account first sees the unread message. Default 2–15. |
| Who gets it | People with unread private messages, one reply per person per account, ever, even after a restart. Channels, groups and bots are ignored. Telegram’s own service messages are only marked read. |
| When | Only while the Neurocommenting engine runs, with “typing…” shown first. Each reply counts toward the pace limit; when the hour is full it is sent later, never dropped. |
Advanced settings apply to all your modules, not only this one. Each setting saves as you change it.
| Setting | Default | What it does |
|---|---|---|
| Parallel joins on a shared gateway | Off | Off: accounts behind the same exit IP take turns to join. On: they join in parallel regardless of proxy. Applies to every join: discussion groups, folders, bulk joins, reactions and warmup. |
| Concurrent joins per proxy | 2 (1–10) | How many accounts behind one exit IP may join at the same time. Only used while parallel joins are off. Lower is safer. |
| Skip already-joined discussions | Off | On restart, trust our records of joined discussions and folders instead of checking each one. Faster, fewer requests; an account that left since is not re-joined up front. |
| Limit pace per account | Off | Caps each account’s visible actions in any rolling hour. When an account is full, Neurocommenting gives the post to another account; reactions, warmup, dialogs and joins wait. |
| Actions per hour per account | 10 (1–100) | The cap. Counts comments, reactions, warmup actions, dialog messages, autoreplies and joins; reading and checks do not count. |
10Statistics and comments
Statistics shows Total Attempts, Successful, Failed sends and Success Rate. The line above the tiles says whether they count since the last Start or all time.
Comments lists every event, newest first, 50 per page. Open a row to see the post, the comment and the reason it did or did not post. Export CSV saves the current page. Clear deletes the whole history permanently, including the statistics; to let accounts post again today use Reset counts instead.
11Common mistakes
- Starting new accounts without warmup and protection, or at a high daily limit. Start at 3 per day and add 1 a day.
- Putting an account in two modules. It is refused; take it out of the other module first.
- Putting the folder creator into the commenting pool, or opening a folder link in your own Telegram.
- A persona without a skip instruction. It comments on posts it should leave alone.
- Reading “Done for today” as a fault. The accounts are at their daily limit and return after 00:00 UTC.
- Pressing Clear under Comments to “reset” accounts. That deletes the history; Reset counts is the right button.