AutoCodeRover
Basic Information
Website: https://autocoderover.dev/
Short description: "AutoCodeRover is a technology we are building for enterprises and developers to maintain reliable and performant software systems through autonomous program improvement." [source]
Intended uses: What does the developer state that the system is intended for?: General-purpose coding and software development
Developer
Website: https://autocoderover.dev/
Legal name: National University of Singapore
Entity type: Academic Institution(s)
Country (location of developer or first author's first affiliation): Singapore [source]
Safety policies: What safety and/or responsibility policies are in place?: Unknown
System Components
Backend model(s): What model(s) are used to power the system?: Variable
Public model specification: Is there formal documentation on the system’s intend...: None
Description of reasoning, planning, and memory implementation: How does the syst...: Model writes a short plan during each step (see figure 1 [source]). Two stages: context retrieval stage (find source of bug) and patch generation stage (fix bug). A "SpecRover" version of AutoCodeRover also "conduct iterative code search accompanied by specification inference" on the purpose of the code to guide improvements [source].
Observation space: What is the system able to observe while 'thinking'?: Uses an abstract syntax tree to represent repositories [source]
Action space/tools: What direct actions can the system take?: Specialized search functions, writing code [source]
User interface: How do users interact with the system?: Unknown
Development cost and compute: What is known about the development costs?: Unknown
Guardrails & Oversight
Accessibility of components
Weights: Are model parameters available?: N/A; backends various models
Data: Is data available?: N/A; backends various models
Code: Is code available?: Closed source
Documentation: Is documentation available?: Available [source]
Scaffolding: Is system scaffolding available?: Closed source
Controls and guardrails: What notable methods are used to protect against harmfu...: Unknown
Monitoring and shutdown procedures: Are there any notable methods or protocols t...: Unknown
Customer and usage restrictions: Are there know-your-customer measures or other ...: None
Evaluation
Notable benchmark evaluations (e.g., on SWE-Bench Verified): 46.2% on SWE-Bench verified [source]
Bespoke testing (e.g., demos): Demo [source]
Safety: Have safety evaluations been conducted by the developers? What were the ...: None
Publicly reported external red-teaming or comparable auditing
Personnel: Who were the red-teamers/auditors?: None
Scope, scale, access, and methods: What access did red-teamers/auditors have and...: None
Findings: What did the red-teamers/auditors conclude?: None
Ecosystem
Interoperability with other systems: What tools or integrations are available?: None
Usage statistics and patterns: Are there any notable observations about usage?: Unknown
Other notes (if any): --