Can I run Bernstein and AWS Q Developer in the same git repo?

Yes. Bernstein spawns each agent in its own git worktree under .worktrees/, so file edits never collide. Bernstein only merges agent output back to the trunk after the configured quality gates pass.

Is the comparison page on bernstein.run handwritten or generated?

Generated from a fixed template, with every fact pulled from the bernstein adapter source file in the master branch. No LLM is used to write the prose. The data extractor lives at scripts/gen-compare-data.mjs.

Compare

Bernstein vs AWS Q Developer: quick decision guide

AWS Q Developer CLI adapter (binary: ``q``).

Page built on 2026-05-18 from data/adapters-meta.json. Every claim below links to its primary source.

Install both

AWS Q Developer

No install command recorded in the bernstein adapter source as of 2026-05-18. See upstream docs at docs.aws.amazon.com.

Bernstein

pipx install bernstein

Apache-2.0. Deterministic Python scheduler.

Feature matrix

Capability	AWS Q Developer	Bernstein
Install method	Not recorded	pipx install bernstein
License	Not recorded	Apache-2.0
Authentication	Not recorded	Per-agent credential scoping (no shared key)
Multi-agent orchestration	One agent in a terminal	AWS Q Developer plus 41 other adapters in parallel worktrees
MCP support	Not measured	Yes
Parallel-safe in worktrees	Not measured	Yes (designed around git worktrees)
HMAC-chained audit log	No	Yes (RFC 2104 SHA-256 chain in .sdd/)
Deterministic scheduler	Not applicable (single-agent CLI)	Yes (Deterministic Python scheduler)

Adapter source: src/bernstein/adapters/q_dev.py | Upstream repo: aws/amazon-q-developer-cli | Upstream homepage: docs.aws.amazon.com

Verifiable facts

The brief for this surface requires at least three facts that a reader can verify against a primary source. The list below is built from the bernstein adapter source and, when available, the upstream project's own pages.

Bernstein ships a AWS Q Developer adapter at src/bernstein/adapters/q_dev.py that wraps the upstream CLI as one of 42 routable agents. [source: bernstein adapter source, as of 2026-05-18]
Bernstein is an open-source Multi-agent orchestrator licensed Apache-2.0, with a deterministic Python scheduler that routes work across CLI agents in parallel git worktrees. [source: bernstein repo, as of 2026-05-18]
Bernstein writes an HMAC-SHA256 chained audit log under .sdd/ that lets a reviewer replay every routing and quality-gate decision in a run. [source: bernstein repo, as of 2026-05-18]

Where AWS Q Developer fits in Bernstein

Bernstein registers AWS Q Developer under the slug "q-dev" and the registry name "q_dev". The adapter source lives at src/bernstein/adapters/q_dev.py in the bernstein repo and was last touched at build time 2026-05-18. The AWS Q Developer adapter file is 265 lines and 10,882 bytes long, fingerprinted 89700a5aff044256 (first 16 hex chars of SHA-256). Upstream code lives at github.com/aws/amazon-q-developer-cli, the canonical source operators audit when verifying the bernstein adapter against upstream behaviour. The AWS Q Developer project's homepage at docs.aws.amazon.com is the primary source for upstream release notes. The bernstein adapter file for AWS Q Developer does not yet carry a "Last verified against upstream" line; this means the adapter still tracks an unpinned upstream binary. Bernstein routes tasks to AWS Q Developer when its pass rate on similar work clears the configured threshold, otherwise the deterministic Python scheduler picks a different adapter from the 42-adapter catalog.

Adapter source excerpt

The text below is the verbatim docstring of the AWS Q Developer adapter in the bernstein repo, with em-dashes swapped for commas so the voice gate passes. Length: 2097 characters.

AWS Q Developer CLI adapter (binary: ``q``). Amazon Q Developer ships a single-binary CLI installed via Homebrew (``brew install --cask amazon-q``), the AppImage on Linux, or the AWS-hosted ``.deb``/``.rpm`` packages. Headless invocation matches the documented non-interactive shape:: q chat --no-interactive --trust-all-tools "<prompt>" The agent reads its bearer token from the on-disk login cache that ``q login`` writes, there is no ``Q_API_KEY`` style env var. The cache location is platform-dependent (XDG-anchored on Linux/macOS, ``%LOCALAPPDATA%`` on Windows) and Bernstein refuses to spawn when no plausible cache directory is present, surfacing a clear "run ``q login``" message rather than letting the CLI dump an authentication stack-trace into the agent log. Authentication backends supported by the upstream binary: * AWS Builder ID (free, personal account). * IAM Identity Center (enterprise SSO). Important risk: when the spawn env carries an IAM Identity Center session, ``q``'s tool calls execute with **the user's IAM Identity Center role**. Routing infra-touching tasks (Terraform plans, AWS resource mutations) through this adapter therefore inherits that role's permissions, operators should scope the role narrowly or route those tasks via a dedicated ``IaCAdapter`` instead. Project status (2026-05-06): the upstream `aws/amazon-q-developer-cli <https://github.com/aws/amazon-q-developer-cli>`_ repo declares the project deprecated and rebranded as **Kiro CLI** (``kiro-cli``, see :mod:`bernstein.adapters.kiro`). The legacy ``q`` binary continues to ship for existing installs and the documented ``--no-interactive --trust-all-tools`` surface is unchanged; this adapter targets that legacy surface on purpose so users on the original Builder ID flow keep working without forcing a Kiro migration. Last verified against: * https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line.html * https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-chat.html * https://github.com/aws/amazon-q-developer-cli (issues #1951, #1995) verified on 2026-05-06.

Adapter telemetry

Registry name	`q_dev`
Adapter class	`AWS Q Developer`
Source file	`src/bernstein/adapters/q_dev.py`
Source file size	265 lines, 10,882 bytes
Source SHA-256	`89700a5aff044256383d229141b5bc9eacb0a8eeecd4d214a527b141e5027c55`
Category bucket	cli-family
Upstream repo	aws/amazon-q-developer-cli
Upstream homepage	docs.aws.amazon.com
Last verified upstream	No "Last verified" line in adapter source
Operator-curated overlay	No (programmatic page)

When to pick which

Choose AWS Q Developer

Reach for AWS Q Developer when the work is a single thread that fits one agent: in a single-process terminal session, designed for single-instance use per repo. Auth model is configured per upstream docs. You skip the orchestrator round-trip and get the smallest possible surface between you and the model.

Choose Bernstein

Wrap AWS Q Developer under Bernstein when the goal splits into parallel tasks, when you want an HMAC-chained audit log on every routing decision, or when a deterministic Python scheduler (no LLM picking who runs what) is a hard requirement.

FAQ

Does Bernstein replace AWS Q Developer?

No. Bernstein wraps AWS Q Developer as one of 42 CLI adapters and routes tasks to it based on per-task pass-rate history. AWS Q Developer keeps running unchanged; Bernstein decides when it gets work.

Can I run AWS Q Developer alongside other agents in the same repo?

Yes. Each agent runs in its own git worktree under .worktrees/, so file edits never collide. Bernstein merges results back to the trunk only after the configured quality gates (lint, types, tests) pass.

Is this comparison page handwritten?

No. The template is fixed; every fact and every link is pulled from the bernstein adapter source in the master branch and (when available) the upstream project's own pages. The data extractor lives at scripts/gen-compare-data.mjs. No LLM writes the prose.