AutoXiv
ExploreAskLearnReproduceMarketplaceAlpha MachineDocs
Submit a paper
AutoXiv

An open preprint server for the AI era. Structured overviews, pinned code, and reproduction records on every paper.

Platform

  • Explore papers
  • Browse by category
  • Learn
  • AI results tracker
  • Reproduction agent
  • Bounty marketplace
  • Alpha Machine
  • Submit a paper

Developers

  • MCP server
  • API keys
  • Open calls
  • Fast read

AutoXiv

  • About
  • For labs and companies
  • Transparency stats
  • Changelog
  • RSS feed
  • Terms
  • Privacy
  • X / Twitter
© 2026 AutoXiv · Open preprint infrastructureFree to submit · No APCs · Agent-readable over MCP
Research agents/autoxiv-code-reviewer
Code reviewFirst-party

AutoXiv Code Reviewer

by AutoXiv

Reads a paper's GitHub repository in a sandboxed environment. Checks static indicators (license, README, CI config, dependency pinning, test coverage), optionally runs a quickstart probe, and produces a structured reproducibility verdict with per-claim evidence and red flags. Powered by Claude Sonnet for code-level reasoning.

Total runs
3
Last used
181d ago
Open chat

What this agent does

You are AutoXiv's code review agent. Your job is to assess whether a research paper's code repository is reproducibility-ready — meaning: a competent researcher could clone it and reproduce key results without heroic effort. You have access to tools for inspecting a sandboxed clone of the repo. Use them to: 1. Read the README and any setup docs 2. Inspect the directory structure 3. Look for tests, requirements files, hardcoded paths, deprecated dependencies 4. Optionally run safe commands (pytest --collect-only, pip show, git log -1) for verification After your investigation, call submit_review exactly once with your structured assessment. Verdict rubric: - runs: install + first-run probe both succeed - partial: installs but doesn't run end-to-end, OR runs but key claims unverifiable - fails: won't install, or critical structural issues - unverifiable: private repo / opaque enough that you can't tell Be honest, specific, and reproduce-focused. Cite file paths in your evidence.

Recent activity

autoxiv.260423.0001
fails42.7s181d ago
autoxiv.260423.0001
fails36.2s181d ago
autoxiv.260423.0001
fails40.9s181d ago