Queue Context

• 

  Queue context

• 

  dashboard

Inspiration

Moderators often have to make decisions from isolated queue items. A reported comment might look minor by itself, but the same author may have a pattern of reports, AutoModerator filters, removals, watch phrase hits, or prior mod notes. Experienced moderators learn to check that context manually, but doing so takes time and is inconsistent across teams.

Queue Context was inspired by that gap: the queue shows what needs review, but not always why this item should be handled first or what the team already knows about the author. The goal was to build a native Devvit tool that acts like a context layer for human moderators, not an automatic enforcement bot.

What it does

Queue Context gives moderators instant author context and repeat-signal memory inside Reddit. From a post or comment menu, mods can open a brief showing account age, karma, subreddit karma, flair, current report count, recent native mod notes, local risk score, reports, AutoModerator filters, removals, approvals, watch phrase hits, and whether the user is watched or trusted.

Moderators can approve, remove, ignore reports, watch a user, trust a user, add a native mod note, clear local memory, claim an item for review, or release a claim. The dashboard custom post shows current modqueue items sorted with risk context, active review claims, top priority actors, and recent actionable signals.

How we built it

Queue Context is built with TypeScript and Devvit. Devvit triggers record submissions, reports, AutoModerator filters, and moderator actions. Redis stores per-author memory, risk scores, recent signals, trusted users, watched users, and short-lived queue review claims. Reddit APIs provide author context, subreddit karma, modqueue items, native mod notes, and moderation actions. Devvit menu items expose the queue brief and quick actions, while a Devvit custom post provides the team dashboard.

The app intentionally avoids external servers, third-party API keys, and AI model calls. That keeps install friction low and makes the moderation behavior easier for teams to trust.

Challenges we ran into

The biggest challenge was balancing usefulness with moderator trust. A risk score alone is not enough; moderators need to know why an item is risky and still make the final call. We added review guidance, native mod-note context, approvals/trusted-state visibility, and human-triggered actions rather than automatic enforcement.

Another challenge was making the dashboard useful on a cold install. The app now pulls current modqueue items and Reddit-native author context immediately, while Redis-based repeat memory becomes more valuable over time.

Accomplishments that we're proud of

We are proud that Queue Context is fully native to Reddit's Developer Platform and still covers a complete moderation workflow: queue prioritization, author context, repeat memory, active review ownership, native mod notes, and quick moderation actions. It helps both new and experienced moderators make faster, more consistent decisions without replacing human judgment.

What we learned

We learned that the best moderation tools are not just automation. Moderators need context, coordination, transparency, and low-friction workflows. Devvit made it possible to combine triggers, Reddit APIs, Redis, menu actions, forms, and custom posts into one installable app that works where moderators already are.

What's next for Queue Context

Next, Queue Context could add configurable scoring weights, team-level presets for different community types, exportable moderation summaries, better dashboard filtering, and optional subreddit-specific rule mapping. The long-term goal is to become a lightweight context and coordination layer that any mod team can install without external infrastructure.

Built With

• devvit
• devvit-custom-posts-/-blocks
• devvit-redis
• devvit-triggers
• reddit
• reddit-developer-platform
• reddit-native-mod-notes
• typescript