Developer Builds Real-Time Chat Moderation Bot for Discord and Twitch Using Jev AI

·2 views

A developer has built an automated chat moderation system for Discord and Twitch using Jev, a decision model from TypeSafe that returns probability scores instead of generating text. Unlike traditional LLMs, Jev answers structured questions with a numerical probability, making it faster and more suitable for binary moderation decisions such as whether to remove a message. The bot was integrated via Composio's Jev toolkit, eliminating the need for a separate HTTP client or hardcoded API keys. Messages scoring 0.8 or above on hostility are deleted automatically, those between 0.5 and 0.8 are flagged for human review, and the rest are left untouched. At roughly $0.042 per million input tokens with output effectively free, moderating 1,000 messages costs under two cents, though the developer recommends keeping human moderators alongside the bot.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

CAPTD Launches Paid Plans Ahead of Product Hunt Debut After Beta Fixes

Developer platform CAPTD transitioned from a free beta to a paid product this week, ahead of its scheduled Product Hunt launch on Saturday. Free tier access is now formally capped at 10 lifetime generations on Instagram only, with all other platforms requiring a paid credit pack. A webhook signature mismatch caused the first live payment order to fail silently, though it was caught and resolved because the test order cost €0. A separate bug fix also addressed a flaw where a failed database write could have permanently lost a paying customer's credits. Analytics cross-checks revealed that roughly 190 genuine visitors used the product over three months, with about half of anonymous database sessions attributed to bots.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How a Speech Habit Taught One Tech Leader the Value of Slowing Down

A software engineering leader at Autodesk describes how a lifelong tendency to pause and speak slowly, once seen as a personal weakness, proved critical during a high-stakes architecture review. Facing a performance crisis with a core data table component used across an enterprise platform, the leader resisted pressure to act quickly and instead prompted the team to step back and examine how data was flowing. The deliberate pace created space for a junior developer, a QA engineer, and a frontend architect to surface overlooked issues, ultimately revealing the problem lay in their own implementation rather than the third-party library. The experience led the team to adopt slower, more intentional communication practices, which the leader credits with improving collaboration and drawing out quieter voices, including a newer developer whose insight later streamlined a key integration process. The author argues that measured speech sets the thinking pace for an entire team and that meaningful silence can unlock insights that urgency tends to suppress.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Write an Effective CLAUDE.md File for Better AI Code Assistance

CLAUDE.md is the first file that Anthropic's Claude AI reads when working inside a repository, making its structure critical to output quality and efficiency. A well-organized file helps Claude understand the project, follow architecture patterns, and avoid repeated mistakes while consuming fewer tokens. Developers are advised to keep the root CLAUDE.md concise, covering only a project summary, critical invariants, and a lightweight index pointing to topic-specific rule files. Detailed guidance — such as UI standards, testing patterns, and API conventions — should live in separate files under a dedicated directory like .claude/rules/, loaded only when relevant. The core principle is that a good CLAUDE.md does not try to document everything, but instead tells the AI where to find what it needs.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Hub API Lets Root Agents Subcontract AI Tasks in a Single Signed Request

A root agent on modelmarket.dev can delegate work to external AI capabilities by routing orders through the Hub while retaining full control of its private key. Developers have two API paths available: a multi-step long path or a condensed single-call approach using POST /ai-market/v2/invoke with the pipeline.run@v1 capability. Preparation is handled via POST /studio/prepare-pipeline, which returns signing materials including EIP-712 authorizations and invoice nonces, but initiates no payment on its own. All transaction signing happens client-side before the signed bundle is submitted, ensuring the Hub never receives the private key. A documented case study from September 2026 shows Codex successfully ordering two GAIA capabilities — weather and air quality reads for Berlin — sequentially through this pipeline on modelmarket.dev.

0 comments Read more at DEV Community