Skip to content

Back to the catalog

Show HN: Agent.reviews – Where AI agents read and write reviews on tools
agent.reviewstool

Show HN: Agent.reviews – Where AI agents read and write reviews on tools

Agent.reviews is a review platform built specifically for AI coding agents: agents like Claude Code, Codex and a "Muse Code" agent write first-hand reviews of developer tools and services (FastAPI, Auth0, Amazon DynamoDB, Redis, Playwright, Vercel, Daytona, Git, npm, Claude API, Cursor) based on real usage during coding tasks, noting concrete friction like nested executables, missing live-credential verification, or scattered docs. The site exposes agent-readable endpoints (skill.md, install.md, llms.txt, and a .md mirror of every page) so a coding agent can both consult prior reviews when choosing a tool and submit its own after a task.

TL;DR A review site where coding agents like Claude Code and Codex read and write candid, task-grounded reviews of dev tools and APIs.
Document

What it claims

Agent.reviews collects reviews of developer tools written by coding agents and organises them by category so a reader can compare tools before opening one. The reviews are task reports, not ratings. Each says what the agent did with the tool in a specific job and how far it got. Visible authors are Claude Code, Codex, Muse Code and an "Other agent" label. One category, "Source control & code review", lists 10 tools, including a hosted PR reviewer and a merge-request CI review job.

How it works

  • Scope. A review covers one task in one codebase. Examples: adding durable retry to an existing FastAPI callback app, or deploying a small Node.js MCP endpoint to Vercel with an existing CLI login.
  • Disclosure of what was not exercised. Reviews state what the agent did not test, and some withhold a score because of it:
  • Auth0: "live login with real credentials was not available for end-to-end verification".
  • DynamoDB: "no live deployment or credentialed read/write was performed".
  • Daytona: "I did not call the SDK by hand, so ease is not scored".
  • CI review job: "No live pipeline was run in the record."
  • Incremental reviews. A later review can cover only what changed. The Playwright entry opens with "New since the last review" and covers popup capture via the page event, a fake microphone, and host-resolver rules with a throwaway certificate in the headless shell.
  • Some reviews speak for a team. The Daytona entry reports "The team was happy with it". Others report the agent's own run.

Limits

  • Many reviews were never tested end to end. Several say the integration was not run against live services. Read each review's disclosure before treating it as evidence that a tool works in production.
  • Sample sizes are very small. Most tools show one review from one agent, tied to one project.
  • No verification or moderation is described. The page does not say how authorship is checked or what stops a vendor from submitting reviews of its own tool.
  • The site addresses agents directly. The top line on the page is an instruction to coding agents: read skill.md and follow install.md. If you let an agent consult or post to the site, it will read instructions and user-submitted text from a third party. Review skill.md and install.md yourself before allowing that.
  • Some reviews appear cut off. On the landing page the Daytona entry ends mid-sentence ("The friction was in…"), so its stated friction is not visible there.

Organisations named here

  • Cursor
  • Auth0
  • Amazon
  • Vercel
  • Daytona
  • Redis

Technologies named here

  • FastAPI
  • Auth0
  • Git
  • Claude API
  • Cursor
  • Amazon DynamoDB
  • Redis
  • Playwright
  • npm
  • Vercel
  • Daytona
  • Codex
  • Claude Code
  • Muse Code