🛠️ All DevTools

[Other] A platform for reproducible world model research and evaluation

[Other] Bijou64: A variable-length integer encoding

[Other] Show HN: Repolog, website audit for SEO, performance, security, and AI readiness

[Code Quality] Show HN: AISlop, a CLI for catching AI generated code smells Hi, I’m Kenny, I’ve been building aislop. I starting working on this after using Claude Code, codex and opencode several times and noticing some slops. They aren’t syntax and passes most tests, they are patterns like empty catch blocks, useless comments, duplicated helpers, dead code and many more. So I built a tool to scan and check for these patterns and wired it into hooks so after each tool call, the agent checks for the slops.<p>You can try it out with npx aislop scan.<p>It’s all local and no code is transferred. Thank you.

[Other] Local Git Remotes

[Other] Data Engineering Zoomcamp is a free 9-week course on building production-ready data pipelines. The next cohort starts in January 2026. Join the course here 👇🏼

[Other] Cursor plugin specification and official plugins

[CLI Tool] Wterm – Terminal Emulator for the Web

[Other] Undisclosed addition in jqwik instructed AI coding agents to delete app output

[Other] Show HN: Zot – Yet another coding agent harness

[Other] Claude Code – Everything You Can Configure That the Docs Don't Tell You

[Other] Show HN: htop for the airwaves — a live 802.11 RF dashboard in your terminal

[Other] MOSS‑TTS Family is an open‑source speech and sound generation model family from MOSI.AI and the OpenMOSS team. It is designed for high‑fidelity, high‑expressiveness, and complex real‑world scenarios, covering stable long‑form speech, multi‑speaker dialogue, voice/character design, environmental sound effects, and real‑time streaming TTS.

[Other] GitHub bans security researcher who posted zero-day Windows exploits

[Other] Protestware for Coding Agents

[Other] Show HN: Open Envelope – an open schema for defining AI agent teams Built an open JSON Schema for defining AI agent teams.<p>Multi-agent systems are becoming a real deployment pattern — not single assistants, but teams with roles, handoffs, and human checkpoints. But there&#x27;s no shared way to define one that travels across frameworks. Every implementation is scattered, locked to whichever tool you picked first. Built the schema to fix that.<p>The schema lives at schema.openenvelope.org and is registered in SchemaStore, so if you drop a .envelope.json file in VS Code you get autocomplete and validation without installing anything. It&#x27;s also on npm as @openenvelope&#x2F;schema if you want to validate programmatically.<p>The spec covers: agent definitions (role, prompt, model, access policy), supervisor&#x2F;sub-agent hierarchy, human-in-the-loop gates, pipelines, schedules, and secrets&#x2F;variables that get injected at deploy time. Access policies let you declare exactly which hosts each agent can call — the runtime enforces this at the network level, not in the prompt.<p>The goal is a portable definition format — define a team once, any compatible runtime can execute it. Similar to how Dockerfiles describe a container without being tied to a specific host. There&#x27;s a managed runtime at openenvelope.org but the schema is Apache 2.0 and anyone can implement it.<p>Happy to answer questions on any part of the spec — especially interested in feedback from people who&#x27;ve built multi-agent systems and have opinions on what&#x27;s missing.

[Other] Announcing Rust 1.96

[Other] Building durable workflows on Postgres

[CLI Tool] Show HN: Py-SQL-cleaner – format SQL embedded in Python strings Hi HN, I built py-sql-cleaner, a CLI for formatting SQL embedded in Python files.<p>Python formatters handle Python syntax. They do not format SQL written inside Python code. On the other hand, SQL formatters usually target SQL files or raw SQL text, not SQL embedded inside a Python file.<p>Still, I think it is not uncommon to find long SQL queries inside Python codebases.<p>py-sql-cleaner detects embedded SQL inside Python files and works only on that SQL. The main things it can do are: find the SQL, format it in place, or extract it into a .sql file.<p>It avoids rewriting SQL that depends on runtime values or template expansion. For example, SQL containing parameters like %s or :name, or Jinja-style template variables like {{ ds }}, is skipped by default.<p>Try it with:<p><pre><code> uvx py-sql-cleaner list path&#x2F;to&#x2F;file.py uvx py-sql-cleaner format path&#x2F;to&#x2F;file.py --dry-run </code></pre> If you write Python, have run into this kind of SQL cleanup problem, or are just curious, I’d be happy if you take a look.

[Other] Dynamic Workflows in Claude Code