AutoResearchClaw

repository·main·Indexed 12 days ago

https://github.com/aiming-lab/autoresearchclaw

An autonomous and collaborative research pipeline designed to transform research ideas into conference-ready academic papers. It features multi-agent subsystems for code generation, benchmarking, and figure creation, supporting both fully autonomous (rc_full) and human-in-the-loop (rc_copilot) modes. The project includes ARC-Bench, a 55-topic benchmark spanning ML, high-energy physics, quantum, biology, and statistics, and provides integration adapters for baselines such as AI Scientist v2, AgentLaboratory, and AIDE ML.

Tokens
116K
Snippets
267
Records
422
Agent score
93%

What's inside AutoResearchClaw

  1. Overview of AutoResearchClaw

    main

    AutoResearchClaw is an autonomous, collaborative, and self-evolving research system designed to transform a research idea into a complete paper. It supports two primary modes of operation:

    1. Fully Autonomous Mode: Operates without human intervention to conduct research and write papers.
    2. Co-Pilot Mode: Allows for human-AI collaboration at key decision points (Human-in-the-Loop).

    The project is compatible with OpenClaw and provides a framework for generating research papers across various domains such as mathematics, statistics, biology, computer science, NLP, RL, computer vision, and robustness. It is built with Python 3.11+ and is documented in several languages.

  2. Overview of ARC-Bench Baselines

    main

    ARC-Bench baselines provide self-contained framework integrations for research benchmarking. The directory structure is organized as follows:

    • adapters/: Contains FrameworkAdapter implementations (one .py file per baseline). These adapters subclass base.FrameworkAdapter and transform framework outputs into a standard submission/ directory format compatible with scripts/judge.py.
    • external/: Contains upstream framework clones (these are gitignored and must be manually installed using the provided setup steps).
    • interventions/: Contains scripted Human-In-The-Loop (HITL) JSON files (e.g., T01-T25) used by rc_copilot. These are auto-derived from rc_full failure modes via scripts/hitl_suggestor.py.
  3. Overview of ARC-Bench

    main

    ARC-Bench is a 55-topic open-ended autonomous-research benchmark spanning five domains: ML (25), high-energy physics (10), quantum (10), biology (7), and statistics (3).

    Each topic is defined by a manifest containing a research question, synthesis, conditions, metrics, datasets, and hypotheses. Frameworks participating in the benchmark must follow a workflow of: code $\rightarrow$ measurements $\rightarrow$ claims $\rightarrow$ writeup. Scoring is performed via rubric-graded multi-criteria audits.

  4. Overview of AutoResearchClaw capabilities

    main

    AutoResearchClaw is an autonomous and collaborative research pipeline designed to turn a single research idea into a conference-ready paper. It supports several key paradigms:

    • Fully Autonomous: A 23-stage pipeline that requires no human intervention.
    • Co-Pilot (Human-in-the-Loop): A collaborative mode that allows humans to intervene at key decision points. It includes 6 intervention modes: full-auto, gate-only, checkpoint, step-by-step, co-pilot, and custom.
    • Multi-Domain Expertise: Specialized agents for domains such as High Energy Physics (using ColliderAgent), Biology (using COBRApy), and Statistics.
    • Skill Extensibility: Users can install custom skills via researchclaw skills install or by placing a SKILL.md file in .claude/skills/.
  5. Critical Security and Integrity Risks in AutoResearchClaw

    main

    A recent code audit (2026-07-03) identified several high-priority (P0/P1) risks that end-users should be aware of when running the research pipeline. These risks primarily involve the potential for silent failures in anti-fabrication guards and security vulnerabilities in sandbox/server environments.

    Key Risk Areas:

    • Anti-Fabrication Bypass: Certain citation verification and data integrity checks (e.g., in literature/verify.py and pipeline/paper_verifier.py) may be bypassed by specific formatting (like using double quotes in BibTeX or specific comment patterns in text).
    • Sandbox Security: In some configurations, the default sandbox mode may run LLM-generated code on the host Python environment without sufficient isolation. Ensure you are using a secure, isolated environment when running experimental code generation.
    • Silent Failures: Many components use broad except Exception: pass blocks, which can hide critical failures such as LLM connection issues, data source unavailability, or failed human-in-the-loop (HITL) approvals.
    • Data Integrity: There are known issues where the system might incorrectly report a 1.0 integrity score if network errors cause all citations to be marked as SKIPPED.
  6. Researchclaw capabilities across domains

    main

    Researchclaw is capable of generating high-quality research papers across diverse scientific and technical domains, including:

    • Mathematics & Statistics: Random Matrix Theory, Econometrics, and Probability.
    • Sciences: Epidemiological Modeling (SIR/SEIR models) and Biology.
    • Computing & Engineering: Numerical Linear Algebra and Preconditioning strategies.
    • Machine Learning & AI:
      • NLP / PEFT: Parameter-Efficient Fine-Tuning (e.g., LoRA rank allocation).
      • Reinforcement Learning: Count-based exploration and state abstraction.
      • Computer Vision: Efficient Vision Transformers (ViT) and token merging.
      • Robustness / Knowledge Distillation: Contrastive feature alignment and distribution shift robustness.
  7. Key features of AutoResearchClaw

    main

    AutoResearchClaw provides a suite of tools for autonomous and collaborative research:

    • Multi-source Literature: Pulls from OpenAlex, Semantic Scholar, and arXiv with automated deduplication.
    • 4-Layer Citation Verification: Validates arXiv ID $\rightarrow$ CrossRef/DataCite DOI $\rightarrow$ Semantic Scholar title match $\rightarrow$ LLM relevance assessment to remove hallucinated references.
    • Hardware-Aware Execution: Automatically detects NVIDIA CUDA, Apple MPS, or CPU to adapt code generation and experiment scope.
    • OpenCode Beast Mode: Automatically directs complex experiments to OpenCode for multi-file project generation.
    • Isolated Experimentation: Uses AST-verified code, immutable frameworks, and iterative optimization (up to 10 rounds) with self-healing capabilities.
    • Conference-Level Writing: Supports NeurIPS, ICML, and ICLR templates (Markdown $\rightarrow$ LaTeX) with full math, tables, and citations.
    • Cost Guardrails: Monitors budget with configurable thresholds (50%/80%/100%) and halts execution if exceeded.
    • Reproducibility: Uses SHA256 checksums for all stage outputs and immutable data tracking.
  8. Understand the ARC-Bench paper-quality meta-rubric

    main

    The ARC-Bench evaluation uses a two-layer scoring system:

    1. Science Rubric: Per-topic rubrics (found in config/{ml,physics,biology}/rubrics/*.json) that grade if the agent ran the experiment correctly and produced valid scientific results.
    2. Paper-Quality Meta-Rubric: A manual layer (defined in config/_meta_paper_quality.json) that grades the deliverable's presentation.

    Combined, the overall score is approximately 54% science and 46% paper-quality. The meta-rubric consists of 19 leaves across 4 buckets:

    BucketLeavesWeight
    paper-contentabstract / intro / method-clarity / results-grounded / discussion / citations30
    code-orchestrationmodular / reproducible / readable / no-dead-code18
    visual-layoutaxes / legend / caption / figure-relevance / color-accessibility17
    content-accuracyno-fabrication (8) / correct-units / claim-strength / internal-consistency21
  9. Expected feedback directory structure

    main

    The analysis tool expects tester feedback to be organized in the feedback_inbox/ directory. Each sub-directory represents one tester and should ideally contain:

    • Feedback Document: A text file (e.g., .md, .txt, .docx, .pdf) containing the tester's report.
    • Screenshots (Optional): A screenshots/ folder containing visual evidence of errors.
    • Artifacts (Optional): A compressed archive (e.g., .zip, .tar.gz) containing the pipeline's output, including error logs, stage-specific JSON files (stage_*.json), and metadata (run_meta.json).
    feedback_inbox/
    ├── tester_alice/
    │   ├── 反馈文档.md              # Feedback document
    │   ├── screenshots/             # Optional screenshots folder
    │   │   ├── error1.png
    │   │   └── stage12_fail.png
    │   └── artifacts.zip            # Pipeline output archive
    ├── tester_bob/
    │   ├── feedback.md
    │   └── deliverables.tar.gz
    └── ...
  10. Use ACP-compatible agents as LLM backends

    main

    AutoResearchClaw supports the Agent Client Protocol (ACP). This allows you to use any ACP-compatible coding agent (like Claude Code, Copilot CLI, etc.) as the LLM backend without needing a direct API key in the config. The agent handles authentication via acpx and maintains a persistent session across the 23 pipeline steps.

    To use an ACP agent, set the llm.provider to "acp" and specify the agent name under llm.acp.

    Supported Agents:

    • claude (Anthropic)
    • codex (OpenAI)
    • gh (GitHub Copilot CLI)
    • gemini (Google)
    • opencode (SST)
    • kimi (Moonshot)
    # config.yaml — exemple ACP
    llm:
      provider: "acp"
      acp:
        agent: "claude"   # N'importe quel agent CLI compatible ACP
        cwd: "."          # Repertoire de travail pour l'agent
      # Pas besoin de base_url ou api_key — l'agent gere sa propre authentification.
  11. How the Researchclaw autonomous pipeline works

    main

    Researchclaw operates through an autonomous pipeline that traverses 23 stages to generate a complete research paper (in NeurIPS PDF format) without human intervention. The process follows this sequence:

    1. Idea: Conceptualization of the research topic.
    2. Literature: Collection of relevant papers (typically 300–470 papers).
    3. Hypothesis: Experiment design and formulation.
    4. Code: Implementation of the research logic (typically 2K–15K lines of code).
    5. Execute: Running experiments in a sandbox environment with iterative refinement.
    6. Write: Drafting the paper, including review and audit stages.
    7. Paper: Final generation of the research paper.

    The pipeline includes iterative self-healing, multi-agent peer review, and citation verification to ensure quality.