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.

来源