Topics organize posts by subject and let you decide how much of each subject reaches review or automatic publication. Open Topics to manage the pool.
Build your topic pool
Review the topics Krabli has learned and name or adjust them to match your work. Study and Insights help you inspect patterns before tightening policy. Let the pool learn from representative posts; a sparse sample can give a misleading picture.
Choose Pass, Count or Drop
- Pass: allow posts on that topic to continue.
- Count: track the topic’s volume without making it a blanket rejection rule.
- Drop: stop posts matching that policy.
Topic decisions are one part of the route. Gate and agent rules still apply. Inspect the recorded reason in Dropped before changing a policy.
Only Pass consumes the Backstage topic cap; Count tracks posts without restricting them by that cap.
Select a stage to see what happens there.
Set separate limits
A topic can have a period cap for Backstage intake and a separate cap for Main automatic publishing. Reaching the intake cap affects admission to review. Reaching the Main cap prevents further automatic publication under that cap; you can still publish manually from Backstage.
Check the period and destination when interpreting a limit. Topic caps differ from an agent’s proposal budget and from the workspace’s daily AI allowance.
Improve the decisions
Use the post, its assigned topic and its reason together when investigating mistakes. Manual review feedback and the Editor’s precedents serve related but different purposes; changing a topic policy is not the same as rejecting one proposal.
If a useful post was held or dropped, inspect the available rescue action and review the result in Backstage. See Gate for cleanup and Editor for automatic publishing safeguards.