我们发现了什么
今天我们发布 Critic,一个变更评审平台,让你能够直接与编写代码的 AI 互动。随着公司采用更多智能体工具,我们发现越来越难让相关人员了解 PR 的影响以及项目的当前状态。
- 来源:Hacker News(发现于 2026-09-25)
- 证据等级:D · 发现产品或需求信号,暂未获得可核验的商业证据。
- 商业模式:待核验
- 主题:AI Agent
- 初筛评分:18.8/100 · 收录 1 次
证据,比故事更重要。
规则清洗与初筛,未经人工商业核验。原文语境、实际客户和付费情况仍需自行验证。
引用与数字披露
来源类型(原作者自述/第三方测算/媒体转引)需采集端标注,本版尚未落字段。
- 作者
- 未标注
- 抓取日期
- 来源类型
- 未标注
- 币种
- 未标注
- 口径
- 未标注
- 披露主体
- 未标注
- 披露日期
- 未标注
本条正文译文未完成(采集端 translation.body_ok=false),此处只展示英文原文。
英文原文(来源本站未改写)
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 https://critic.run .Let me know if you have feedback or questions.
这条还缺什么证据?
下面每条都由本条已有字段推出(等级、理由、商业模式、来源次数、是否演示), 本站不生成推测性结论;通用验证方法放在方法论页。
- 可核验的收入或付费证据查官网定价页与付费口径;第三方数据源(如 GetLatka)只作旁证,需标注来源与时点。
- 商业模式未定确认按席位/按用量/授权还是开源托管版收费;开源项目另查 LICENSE 与是否存在付费版。
- 只有单一来源找一手站点或其他渠道是否重复出现同一产品;社区热帖数量不等于商业进展。
通用验证清单(谁有这个问题/谁愿意付费/一个人能交付哪一小步)见我们的筛选方法。