Open-source cleanup that respects contributors.
Keep open-source and tech communities active with transparent inactivity tracking. No message access. No privileged intents.
"How exactly does the score work?"
What you’re optimizing for
- Removing "dead" accounts to keep the user list relevant.
- Ensuring contributors are recognized.
Common pain points
- Users who join for one question and vanish forever.
- Need to be extremely transparent about how automation works.
Ghost Mode Setup Preset
Select Quick Start (Ghost) during /start.
Core Behavior
- Operating Mode
- Ghost (Staff-only outputs)
- Timeline
-
Warning 30 days (~1mo)Mark Inactive 60 days (~2mo)Kick Eligible 120 days (~4mo)
- Auto-kick
- Off
Signals & Actions
- Activity Signals (ON)
- Messages, reactions, interactions, typing, threads, rsvps.
- Engagement
- Polls OFF, CTA OFF.
- No reward roles configured in this preset to keep noise minimal.
Suggested Channels & Roles
Why CleanerBot fits this use case
Tech communities demand transparency. We provide a clear, deterministic Decay Score system that explains exactly why a user is considered inactive, without spying on their message content.
Respect contributors and reduce noise
Open-source communities often have long quiet periods between bursts of activity. The safest approach is to label carefully and review with context. CleanerBot frames open-source cleanup as a way to respect contributors while keeping the community legible.
The open-source preset defaults are deliberately patient. Contributors may disappear during release work and return later with major fixes. A longer runway protects goodwill while still highlighting accounts that are likely gone.
The target group analysis suggests a fairness-first stance for technical communities. Manual review queues, explicit exemptions for maintainers, and clear status labels make the process legible instead of political.
Contributor-safe defaults
- Exempt maintainers and trusted roles.
- Review after releases, not during them.
- Favor labels over removals for contributors.
Keep it readable
- Publish the timeline in contributor docs.
- Use one review channel with pinned guidance.
- Explain changes in release notes or updates.
Related reading: inactivity policy template, auto-kick guardrails.
Common Questions
Can I audit the actions?
Yes. Every action (warning, role assignment, kick suggestion) is logged to the configured log channels with a reason code.
Can I switch out of Ghost Mode?
Yes. You can switch to Standard mode anytime via /config if you decide you want member-facing warnings.
How do I exempt Maintainers?
Add your Maintainer/Contributor roles to the exemption list. They will be ignored by the decay system entirely.
What about occasional contributors who go quiet between releases?
Use a longer timeline and review context before acting. Open-source cleanup should protect contributor goodwill first, especially when quiet periods align with release work.
Can we keep discussions open but clean up access roles?
Yes. Many maintainers keep public read access while using CleanerBot to manage contributor or project roles. This keeps the community legible without locking out returning contributors.
Invite CleanerBot, run /start, and publish a short, transparent inactivity policy in your rules channel with the Inactivity Policy Template.
Moving away from Discord Prune? Read the Discord Prune vs CleanerBot Comparison.