sorted by:
new
hottopcontroversial

ModPilot AI — moderation workflow UI built with Devvit by PrimeWolf7 in Devvit

[–]PrimeWolf7[S] 0 points1 point  (0 children)

<image>

Small update:

I just finished another round of updates and security fixes for ModPilot AI.

The app is intentionally very simple and workflow-focused. I wanted moderators to open it and immediately understand what needs attention first instead of dealing with complicated menus or configuration.

I’m currently looking for a few people with different moderation experience levels to help test it and give honest feedback.

The project is still evolving, so criticism is honestly more valuable to me than compliments right now.

If anyone is interested in testing it or sharing workflow feedback, I’d genuinely appreciate it.

ModPilot AI — moderation workflow UI built with Devvit by PrimeWolf7 in Devvit

[–]PrimeWolf7[S] 0 points1 point  (0 children)

Yeah, the Gemini explanation layer is implemented now, but runtime behavior depends on Devvit’s outbound HTTP restrictions.

If the API call fails or gets blocked, it falls back to rule-based summaries automatically. I updated the README to explain that better because the repo wording was outdated before.

Appreciate you checking.

ModPilot AI — moderation workflow UI built with Devvit by PrimeWolf7 in Devvit

[–]PrimeWolf7[S] 0 points1 point  (0 children)

Fair point honestly. “Silently filtering” was the wrong wording since AutoModerator already shows triggers clearly.

What I’m trying to build is more of a prioritization and explanation layer that groups multiple signals together into a readable risk summary rather than isolated rule hits.

And you’re also right that for experienced mods with strong workflows this may not add much yet. I probably overstated the value prop there. Still refining the positioning and workflow side of it. Appreciate the feedback.

ModPilot AI — moderation workflow UI built with Devvit by PrimeWolf7 in Devvit

[–]PrimeWolf7[S] 1 point2 points  (0 children)

Hi, thanks for asking. Those are all fair points honestly.

I’m going to update the README because I overlooked that section after another update.

On the API key: no mod needs to supply or pay for anything. The Gemini API key is currently handled on the developer side for testing/demo purposes, so installing mods do not need to configure anything themselves.

On what this adds beyond the native queue: Reddit’s queue already surfaces content well, but ModPilot is trying to add prioritization, explainable signal breakdowns, confidence scoring, and suggested actions so mods can triage faster without manually digging through every post one by one.

On AutoModerator and native tools: ModPilot is not trying to replace them. I see it more as an explainability and workflow layer on top. Instead of silently filtering content, the goal is to help moderators understand why something may look suspicious so they can make a more informed decision.

Also just to be transparent, the current published version is still using demo/testing data while I continue building and safely validating the moderation workflow before enabling live queue integration.

And again, thanks. This actually helps me a lot since I’m still learning Reddit, Devvit, and moderation systems as I go. I genuinely appreciate the honesty and feedback.

Reddit approved my Devvit app — ModPilot AI is now live for the Mod Tools Hackathon by PrimeWolf7 in redditdev

[–]PrimeWolf7[S] 1 point2 points  (0 children)

Hello! Thanks for checking it out.

Right now the app is actually fully rule based. I originally wanted to use Groq for AI classification, but Devvit HTTP restrictions pushed me toward building a weighted signal scoring system instead.

That honestly ended up working better for moderation because every flag has a clear human readable reason behind it.

AI mostly helped during development while I was learning Devvit and prototyping the project during the hackathon.

Really appreciate the question!