Blog
Notes from the Butterneck team
How product teams hand change requests to AI, and why a developer still decides what goes live. RSS feed.
Butterneck is a tool for AI change requests. A product person requests a change to a live web app and checks it on a live preview: the AI coding agent the developer already uses runs on the developer's computer, no pull request is opened, and a developer decides first. It is not a project-management or task-board tool.
AI tools that let non-developers change an existing web app (2026)
Compare AI tools that let PMs and designers change an existing web app: who asks, where the agent runs, PR or no PR, Jira, and published prices (Oct 2026).
Live preview before the PR: how PMs can review a change before anyone opens a pull request
Preview an AI coding agent's change on a live copy before anyone opens a pull request: what the PM checks, who decides, and how it differs from PR previews.
A 4-week pilot to let PMs request live changes: the proposal to send your engineering lead
A copyable one-page proposal for a 4-week pilot where PMs ask an AI coding agent for small changes on a live preview and a developer decides what ships.
How to write a change request for an AI coding agent: a template for PMs
A five-line AI change request template: how PMs and designers can prompt an AI coding agent to change an existing app, and what to leave to a developer.
Claude Code for product managers: use your team's Claude Code or Cursor without a terminal
PMs don't need a terminal: ask for a change on a live preview, your developer's own Claude Code or Cursor makes it, and a developer decides what ships.
Clogless alternative: an honest comparison with Butterneck
Clogless vs Butterneck for product teams: cloud sandbox and PR vs a live preview your developer reviews. Plus other Clogless alternatives, from public info.
The AI PR review bottleneck: why AI pull requests need an owner (2026 data)
The AI PR review bottleneck in numbers: LinearB (8.1M PRs), CircleCI, DX and a 196,212-PR CMU/Stanford study. Why AI PRs wait, and what an owner changes.
What non-engineers can ask AI to change: a policy template for product teams
A copyable policy for PMs, designers and support leads who ask an AI coding agent for changes: what they can ask for, what needs an engineer, and review tiers.
Should product managers ship code? A better middle ground
Should PMs ship code with AI? A Harvard study finds AI agents slow code review. A calmer option: PMs ask on a live preview, and a developer decides what ships.
Itera alternative: an honest comparison with Butterneck
How Itera and Butterneck compare for product teams: scope, where the agent runs, PRs vs previews, Jira and pricing. Plus other Itera alternatives.
Small changes stuck in the backlog? How PMs can change a live app without waiting on engineering
Small product changes sit in the backlog because of the relay, not the code. Ask on a live preview, an AI coding agent edits it, a developer decides what ships.
Jira ticket to pull request with AI: check a live preview before anyone opens the PR
Label a Jira ticket, an AI coding agent makes the change on a live copy, the requester checks the preview, and a developer decides whether to open a PR.
AI change requests for product teams: a practical guide
What AI change requests are, how product teams automate the request-to-preview handoff safely on a live copy, what guardrails to check, and a rollout plan.
How Butterneck runs an AI coding agent in a sandbox on your own machine
How Butterneck runs Cursor, Claude Code or Antigravity on a developer's computer: folder isolation, .env guardrails, per-turn rollback and preview links.
Ask freely, ship deliberately: an architecture for human-in-the-loop AI product changes
Why non-developer requests to coding agents should stop short of auto-merge, and the live-preview, no-merge architecture Butterneck uses.
Human-in-the-loop AI coding: why Butterneck never merges
Human-in-the-loop AI coding with a gate for the person who asked: they check the change on a live preview, and a developer decides. No auto PR or merge.
Share your local app with stakeholders without deploying it
Share localhost with a PM or stakeholder without deploying: a live link to the app on your computer, a chat to ask for changes, and AI edits on the preview.