Ask freely, ship deliberately: an architecture for human-in-the-loop AI product changes

Описание и применение

Butterneck реализует архитектуру, позволяющую неразработчикам запрашивать изменения кода, которые автоматически применяются в локальной среде, мгновенно отображаются в живом предпросмотре, а только разработчик подтверждает и отправляет в продакшн.

Задача

Non‑developers request code changes but lack the ability to review diffs, risking incorrect or unsafe deployments.

Результат

Butterneck’s architecture keeps the developer as the sole gatekeeper to production while allowing non‑developers to request changes that are previewed instantly, reducing manual effort and preventing accidental deployments.

Рабочий процесс

• 1. Developer runs the bridge daemon and connects project folders.
• 2. Requester submits a change via chat widget or Jira ticket with a Butterneck label.
• 3. Bridge starts the coding CLI (Cursor, Claude Code, etc.) as a child process in the target folder.
• 4. Agent edits files locally; the dev server reloads and shows the preview to the requester.
• 5. Agent tags the change with a confidence level.
• 6. Developer reviews the preview, conversation, and edited files.
• 7. Developer commits and merges through the normal pipeline or discards the change.

Доказательства

Coding agents can now change a real codebase from a sentence.

Источник

The request happens next to the thing. The person asking should be looking at the running product, not describing it from memory.

Источник

The preview is the running dev server. The bridge starts the app and the server issues a public share URL that relays traffic over the bridge's WebSocket, including hot‑reload sockets.

Источник

The developer reviews all three, then commits and ships through the team's normal pipeline, with its tests, CI and code review intact. Or discards it.

Источник