Amazon Q Developer

Basic Information

Short description: A general purpose coding agent [source]
Intended uses: What does the developer state that the system is intended for?: General purpose software development tasks
Date(s) deployed: November 28, 2023 [source]

Developer

Legal name: Amazon.com, Inc [source]
Entity type: Corporation [source]
Country (location of developer or first author's first affiliation): Incorporation: Delaware, USA (AMAZON.COM INC (2620453)) [source]. HQ: Seattle [source]
Safety policies: What safety and/or responsibility policies are in place?: Amazon's Responsible AI policy [source]

System Components

Backend model(s): What model(s) are used to power the system?: Amazon (Titan models), Anthropic, AI21 Labs, Cohere, Meta, Mistral AI, Stability AI [source]
Public model specification: Is there formal documentation on the system’s intend...: Available [source]
Description of reasoning, planning, and memory implementation: How does the syst...: Unknown
Observation space: What is the system able to observe while 'thinking'?: System can access user's input text, codebases, and data on AWS [source].
Action space/tools: What direct actions can the system take?: System is able to write code, natural language responses, use AWS resources, and leverage third-party integrations [source] [source].
User interface: How do users interact with the system?: Amazon Q can be used on code editors, like VS Code, or using command line interface [source]
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...: Bedrock has the option of "returning control" to the developer by allowing them to decide whether to execute actions in their own applications [source]. There are also relevant AWS security measures [source].
Monitoring and shutdown procedures: Are there any notable methods or protocols t...: Users can access AWS CloudTrail and Amazon Cloudwatch to monitor Amazon Q [source].
Customer and usage restrictions: Are there know-your-customer measures or other ...: None

Evaluation

Notable benchmark evaluations (e.g., on SWE-Bench Verified): 55% on SWE-Bench verified [source]
Bespoke testing (e.g., demos): None
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?: Documentation discusses integrations [source].
Usage statistics and patterns: Are there any notable observations about usage?: Unknown
Other notes (if any): --