Hey HN, I'm Shreyash from Feyn. We help companies build custom models from their data. Today we're releasing Critic, a change review platform that lets you engage directly with the AI that wrote the code.

Agents write most of our code. While that has made us more productive, understanding a change and its consequences has become incredibly difficult. As our company adopted more agentic tools, we found it harder to loop people in on the impact of a PR and the state of a project. We built Critic to fix this.

Critic lets AI agents present their code, annotate key blocks, and include relevant evidence (like screenshots and instructions to run locally). Anyone viewing that change can talk directly to the agent that wrote it. See a demo here: https://www.youtube.com/watch?v=U2--lytmOtQ.

Critic works through a plugin for Codex or Claude Code. When your agent writes code, the plugin asks it to also write a narrative describing the story behind the change, and highlight any assumptions, decisions, or complex code. You can then view the change at critic.run or have your agent pull it via the bundled MCP. Every feature in Critic is available over MCP, so your agent gets all the same context without leaving its harness.

From the dashboard or MCP, you can chat with the authoring agent directly. When Critic receives a question, it forks the authoring session and forwards your question there. That way your main thread stays clean and keeps working.

Local changes are visible only to the owner. Anything pushed to GitHub is mirrored and visible to anyone with permission to view that change on GitHub.

When building Critic, security was a big priority for us. AI agents often run in auto mode and can take many actions on your computer. We wanted to ensure that giving people access to your agent doesn't mean giving them access to your computer. All Critic forked sessions are stripped of their write tools. They can only answer questions about the change and in-progress work in that workspace.

Critic has helped us catch several incidents before they hit production. The most common is a model not reusing artifacts, like existing styles, components, or functions. Because it's so easy to dig into an agent's work and question it, we've also caught more cases of models misdiagnosing issues or writing unhelpful code. Since Critic's UI is faster and friendlier to agents than GitHub, our team is returning feedback quicker as well.

Critic is free to use. Sign up at critic.run. Let me know if you have feedback or questions

Fragments: September 24

Double-entry bookkeeping and paper and tokens

Pummelvision Back

Legal and General to Cut 10% of Jobs by Middle of 2027

Beware Overreliance on Metaphor

AI Workers' Inquiry 2026

.si domain registrations outpace .ai after Trump's 'Super Intelligence' rename

Unmasking "zombie cells" in aging tissue with an AI-powered barcode

Weapons of Mass Decentralization Magazine

Why Washington Governs by Fiscal Cliff

Forging 1024-bit RSA signatures in nearly SNFS time

The Chosen People

Show HN: OpenArcade – open-source software from the VR arcade I ran for 4 years

Vibe Coded Musical Correspondences

China's Mind on AI

It's "Underwear on the Outside" Time

Mythical Thought and Scientific Thought

DBDelve: Fast and modern DB Client made in Rust and gpui

Excel adds nested arrays

Near-Total Liquid Heat Capture Keeps AI Racks Cool

Show HN: Critic – Review code with the agent that wrote it

Patents on laser designation and machine-aided targeting

Funny VideosHow to Start a Faceless YouTube Channel with AI: A Complete Guide

Tidewater Island Fishing Game

The Rise of Audio AR

One URL, Three Different Tricks

Startups I am curious, what ERP system do you guys use?

The Qodo Agentic Toolbox: A CLI-powered Quality counterpart for coding agents

The grey box of post-quantum cryptography standards

Nigel Richards – The best Scrabble player [video]

Ask HN: Are .shop domains down?

Comments