Gate applies shared cleanup before posts reach agents. Configure it in Gate, rather than repeating cleanup instructions in every agent.
Choose the checks
Non-news and exact-text checks do not need an AI key. Enable them only when appropriate for your collection goal; non-news cleanup does not suit every subject or format.
Advertising, teaser and repeat checks use AI and need your OpenRouter key. These paid checks are currently enabled by default: review the switches and key before going live. They can run before Relay, although Relay itself uses rules.
A provider failure during cleanup generally lets the post continue. A skipped or failed check does not mean a successful AI review.
Follow the decision
Select a stage to see what happens there.
- Sources
Sources. Public Telegram channels you follow. A source belongs to one agent in your workspace.
- Gate
Gate. Shared cleanup runs before agents. Held posts can be reviewed in Dropped.
- Agent
Agent. Relay, Filter or Correspondent applies your selection rules.
- Dropped
Dropped. Inspect why a post was held or dropped. Rescue eligible posts for another review.
Continuing posts still face agent selection. Inspect held or dropped posts in Dropped. The reason distinguishes Gate cleanup, agent selection, topic policy and processing errors. Held posts are not necessarily lost permanently.
Review and rescue
Inspect the original and reason in Dropped, then use the available rescue action for an eligible post. Check Backstage before publishing. Frequent rescues may mean Gate is too strict for your sources.
Manual Telegram rejection does not create a Dropped copy: it is feedback on an existing proposal. See Backstage.
Test expectations
Agent dry runs do not exercise paid advertising, teaser or repeat checks, live daily caps or final rich formatting. Check Gate and real arrival reasons separately. Troubleshooting helps trace missing posts.