<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Butterneck</title>
    <description>The latest articles on DEV Community by Butterneck (@butterneck).</description>
    <link>https://dev.to/butterneck</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4210715%2F02e74805-34c4-429e-821c-063d68ab1d3f.png</url>
      <title>DEV Community: Butterneck</title>
      <link>https://dev.to/butterneck</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/butterneck"/>
    <language>en</language>
    <item>
      <title>AI change requests for support teams: fix the labels behind repeat tickets</title>
      <dc:creator>Butterneck</dc:creator>
      <pubDate>Thu, 19 Nov 2026 11:20:56 +0000</pubDate>
      <link>https://dev.to/butterneck/ai-change-requests-for-support-teams-fix-the-labels-behind-repeat-tickets-f35</link>
      <guid>https://dev.to/butterneck/ai-change-requests-for-support-teams-fix-the-labels-behind-repeat-tickets-f35</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.butterneck.com/blog/ai-change-requests-for-support-teams" rel="noopener noreferrer"&gt;butterneck.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Support teams see the same confusing label, missing hint or unclear error message over and over. Each ticket is small. Together they fill the queue, and each one still waits for someone to change the wording in the app.&lt;/p&gt;

&lt;p&gt;Many of those tickets are product wording, not a new feature and not a data or permissions problem. This post is about who can ask for that kind of change, how to check it on a live preview, and what still stays with a developer. We make Butterneck, which is built this way, so we describe its flow below. The same split — the person who asked checks the preview, a developer decides what ships — works with any setup that can show the support lead a running copy of the app.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;In short:&lt;/strong&gt; Support leads can ask for a small wording change — a confusing label, a missing hint, an unclear error message or an empty state — on a live preview of the existing app. In Butterneck they open a share link, type the request in the chat beside the preview, and can attach a customer's screenshot. The developer's own coding agent edits the project on a developer's connected computer, the preview updates, and the person who asked checks the result. A developer reviews the change and decides what ships. Butterneck never commits, pushes, opens a pull request, merges or deploys. A Jira ticket labeled &lt;code&gt;butterneck&lt;/code&gt; can start the same flow. When the ticket is a bug report, let the person who reported it check the fix on the preview before a developer ships it.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Which support tickets are really product wording
&lt;/h2&gt;

&lt;p&gt;The tickets that fit are the ones you can see on a screen you can open in a preview: the button that says the wrong thing, the form field with no hint, the error message nobody understands, the empty state that doesn't say what to do next. They show up as repeat contacts because customers hit the same wording and ask the same question.&lt;/p&gt;

&lt;p&gt;Those changes belong in the app, not only in a help article. A support lead who already knows the ticket can describe what the screen should say. What they cannot decide is whether the change is safe to ship. Shared components, tests, translations, and anything near sign-in, billing, refunds, permissions or customer data stay with a developer, as we already say in our &lt;a href="https://www.butterneck.com/blog/ai-change-requests-for-product-teams" rel="noopener noreferrer"&gt;guide to AI change requests for product teams&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If the cause isn't on the screen — data from another system, payments, permissions, something that only happens sometimes — leave it to a developer. That line is the same one in &lt;a href="https://www.butterneck.com/blog/how-to-write-a-change-request-for-ai#what-to-leave-to-a-developer" rel="noopener noreferrer"&gt;how to write a change request for an AI coding agent&lt;/a&gt; and in &lt;a href="https://www.butterneck.com/blog/reporter-checks-the-fix" rel="noopener noreferrer"&gt;let the reporter check the fix before it ships&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works in Butterneck
&lt;/h2&gt;

&lt;p&gt;A developer connects a computer that already has the project. The running app gets a share link. The support lead opens that link in a browser and types the change in the chat beside the live preview. A customer's screenshot can be attached. The coding agent the developer already uses (Cursor, Claude Code or Antigravity) edits the real project on a developer's connected computer, and the preview updates on the same link.&lt;/p&gt;

&lt;p&gt;The support lead checks the wording on the running screen: the exact text, the spacing around it, and a phone-sized width, and that nothing else on the page moved. If it's off, they ask again on the same request. When it's right, they say so in writing where they asked. A developer then reads the diff and decides what ships. Butterneck never commits, pushes, opens a pull request, merges or deploys.&lt;/p&gt;

&lt;p&gt;The same request can start from Jira. Add the label &lt;code&gt;butterneck&lt;/code&gt; and assign the ticket to a teammate whose Jira account is mapped to a computer that has the project. The ticket becomes the request, and a preview link is posted back when the AI is done. If the assignee isn't mapped, nothing starts. Details are in &lt;a href="https://www.butterneck.com/blog/ai-change-requests-in-jira" rel="noopener noreferrer"&gt;AI change requests in Jira&lt;/a&gt; and on the &lt;a href="https://www.butterneck.com/integrations/jira" rel="noopener noreferrer"&gt;Jira integration&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Let the reporter check the fix
&lt;/h2&gt;

&lt;p&gt;When the ticket is a bug report, the person who reported it is the one who already knows what "fixed" looks like. Let them check the fix on the preview before a developer ships it. If the reporter is a customer, not someone on the team, a support lead or teammate who can reproduce the bug does that check. The customer's later reply in your usual support thread can still matter, but the cheap check is the one done on the preview.&lt;/p&gt;

&lt;p&gt;That is the subject of &lt;a href="https://www.butterneck.com/blog/reporter-checks-the-fix" rel="noopener noreferrer"&gt;let the reporter check the fix before it ships&lt;/a&gt;. The reporter's sign-off means "this is the fix I was asking for", not "ship it". A developer still decides what goes live.&lt;/p&gt;

&lt;h2&gt;
  
  
  What stays with a developer
&lt;/h2&gt;

&lt;p&gt;Keep anything that touches billing, refunds, permissions or customer data with a developer. The same is true of sign-in, shared components, tests and translations. The support lead's job is to confirm the wording on the preview is what they meant. The developer's job is to decide whether the change is safe to ship.&lt;/p&gt;

&lt;p&gt;For why a developer still owns that last step, see &lt;a href="https://www.butterneck.com/blog/human-in-the-loop-ai-coding" rel="noopener noreferrer"&gt;human-in-the-loop AI coding&lt;/a&gt; and &lt;a href="https://www.butterneck.com/blog/ai-prs-need-an-owner" rel="noopener noreferrer"&gt;why AI pull requests need an owner&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to write the request
&lt;/h2&gt;

&lt;p&gt;Write what you see, what you expected and where, and attach a screenshot. The five-line template in &lt;a href="https://www.butterneck.com/blog/how-to-write-a-change-request-for-ai" rel="noopener noreferrer"&gt;how to write a change request for an AI coding agent&lt;/a&gt; works here: the "Now" line is the current wording or the bug, the "Want" line is what it should say, and the "Check" line is how you'll know it's right. If the first result is still off, say exactly what's still wrong on the same request instead of starting a new one.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Does a support lead need an account to look at the preview, and who can send a request?
&lt;/h3&gt;

&lt;p&gt;Viewers do not need an account. They open a share link in a browser, or a Jira label starts the request. The developer chooses who can send: a named list, or anyone with the link. Share links are unlisted, not a private vault. Anyone with the link can open that preview. Someone who is not allowed can request access, and you decide.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does Butterneck open a pull request?
&lt;/h3&gt;

&lt;p&gt;No. Butterneck never commits, pushes, opens a pull request, merges or deploys. The person who asked checks the change on the live preview. A developer reviews the diff and publishes it the way the team already does, which can include a pull request, or they drop it.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is customer data in the preview?
&lt;/h3&gt;

&lt;p&gt;The preview is the app running on a developer's connected computer. Keep production secrets and production data off that computer, and use development keys and seed data. Anything that touches customer data stays with a developer. Who can send a request, and what the share link exposes, are on the &lt;a href="https://www.butterneck.com/security" rel="noopener noreferrer"&gt;Security&lt;/a&gt; page.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://calendar.app.google/p2McAaz4ZwXBiG5m9" rel="noopener noreferrer"&gt;Book a 30-minute demo&lt;/a&gt; and bring a repeat ticket about a label or error message. We will run it on a live copy. Or see &lt;a href="https://www.butterneck.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt; and try a request on the &lt;a href="https://app.butterneck.com/trial" rel="noopener noreferrer"&gt;sample shop&lt;/a&gt; before connecting a computer. The wider process is in &lt;a href="https://www.butterneck.com/blog/ai-change-requests-for-product-teams" rel="noopener noreferrer"&gt;AI change requests for product teams&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productmanagement</category>
      <category>customersupport</category>
      <category>webdev</category>
    </item>
    <item>
      <title>AI change requests: vibe coding for teams with a review step</title>
      <dc:creator>Butterneck</dc:creator>
      <pubDate>Thu, 05 Nov 2026 05:36:33 +0000</pubDate>
      <link>https://dev.to/butterneck/vibe-coding-for-teams-how-to-let-the-whole-product-team-ask-for-changes-safely-3hea</link>
      <guid>https://dev.to/butterneck/vibe-coding-for-teams-how-to-let-the-whole-product-team-ask-for-changes-safely-3hea</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.butterneck.com/blog/vibe-coding-for-teams" rel="noopener noreferrer"&gt;butterneck.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;"Vibe coding" started as a solo habit: describe what you want, let an AI coding agent write it, look at the result, and keep going without reading every line. For a weekend project that is fine. For a product a team already ships to customers, it raises fair questions. Who is allowed to ask? Who checks the result? Who decides what goes live?&lt;/p&gt;

&lt;p&gt;This post is about vibe coding for teams: keeping the fast "describe it and see it" loop, and adding the few rules a shared codebase needs. We make Butterneck, so we explain how it does this near the end. The rules work with any setup.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Vibe coding for teams, in short:&lt;/strong&gt; Let anyone on the product team describe a change in plain words and see it on a running copy of the app, but keep one person who reads the change and decides whether it ships. In Butterneck the request is made on a live preview, the coding agent a developer already uses (Claude Code, Cursor or Antigravity) edits the project on a developer's connected computer, and a developer still decides what ships.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  What changes when vibe coding moves from one person to a team
&lt;/h2&gt;

&lt;p&gt;When one developer vibe codes, the person asking, the person checking and the person shipping are the same. On a team they split apart:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The person asking&lt;/strong&gt; is often a PM, designer or support lead who can describe the change but can't read the diff.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The person checking&lt;/strong&gt; needs to see the change on the real screen, not in a code review.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The person shipping&lt;/strong&gt; is a developer who knows the codebase, the tests and the release process.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Most problems with vibe coding on teams come from merging those roles by accident: a non-developer's change going live with nobody reading it, or a developer reviewing a diff with no idea whether it is what the requester meant.&lt;/p&gt;

&lt;p&gt;Atlassian sees the cost of that from the developer side. Its 2026 developer experience research found that 26% of developers say AI saves them 10 or more hours a week, down from 68% in 2025, and 49% now spend four or more hours a week managing AI. Its conclusion: "When agents can generate code, designs, and prototypes in minutes, the bottleneck moves to deciding what’s worth building and whether it’s good enough" (&lt;a href="https://www.atlassian.com/blog/how-we-build/3-lessons-from-rebuilding-atlassians-product-development-lifecycle-for-people-and-agents" rel="noopener noreferrer"&gt;Atlassian, 10 November 2026&lt;/a&gt;). Keeping the three roles apart is how a team puts each of those decisions with the right person.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four rules for team vibe coding
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Write down who can ask, and for what.&lt;/strong&gt; Copy, layout, empty states and small UI fixes are good candidates. Auth, payments, data models and anything security-related need an engineer from the start. Our &lt;a href="https://www.butterneck.com/blog/ai-change-request-policy-template" rel="noopener noreferrer"&gt;AI change request policy template&lt;/a&gt; is a starting point.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Show the change before anyone reviews code.&lt;/strong&gt; The requester should check it on a running copy of the app. See &lt;a href="https://www.butterneck.com/blog/live-preview-before-pull-request" rel="noopener noreferrer"&gt;live preview before the pull request&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep a developer at the last step.&lt;/strong&gt; A developer reads the conversation and the diff, then commits, opens the PR, or throws it away. That is the review your team already has.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep it small and reversible.&lt;/strong&gt; One request, one change. Bigger work goes through the normal ticket and planning flow.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Vibe coding tools: where team features matter
&lt;/h2&gt;

&lt;p&gt;Most vibe coding tools are built for one person driving the agent. When you compare them for a team, ask:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Does it work on the app you already have, or does it start a new project?&lt;/li&gt;
&lt;li&gt;Who can send requests, and can you limit that to a list of people?&lt;/li&gt;
&lt;li&gt;Where is the change checked: on a running copy, in a diff, or after deploy?&lt;/li&gt;
&lt;li&gt;What does the tool do at the end: edit files, commit, open a PR, or deploy?&lt;/li&gt;
&lt;li&gt;Whose AI subscription runs the work, and do its terms allow team use?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For a longer side-by-side of tools that change an existing app, see &lt;a href="https://www.butterneck.com/blog/tools-for-non-developers-to-change-an-existing-app" rel="noopener noreferrer"&gt;tools for non-developers to change an existing app&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Butterneck does vibe coding for teams
&lt;/h2&gt;

&lt;p&gt;Butterneck calls these requests AI change requests. A developer connects a computer that already has the project and a coding CLI signed in: Claude Code (&lt;code&gt;claude&lt;/code&gt;), Cursor's CLI (&lt;code&gt;agent&lt;/code&gt;) or Antigravity (&lt;code&gt;agy&lt;/code&gt;).&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The app runs on that computer's dev server, and Butterneck gives it a share link.&lt;/li&gt;
&lt;li&gt;The developer chooses who can send requests: a list of people, or anyone with the link.&lt;/li&gt;
&lt;li&gt;A teammate opens the link and types the change into a chat next to the screen they mean. Or someone labels a Jira ticket &lt;code&gt;butterneck&lt;/code&gt;; see the &lt;a href="https://www.butterneck.com/integrations/jira" rel="noopener noreferrer"&gt;Jira integration&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;The coding CLI edits the connected project, and the preview updates on the same link.&lt;/li&gt;
&lt;li&gt;A developer reviews the change and the conversation and ships it the usual way, or discards it.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Butterneck does not commit, push or open a pull request, and it never merges or deploys. A developer decides what ships.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;See it before you set anything up:&lt;/strong&gt; &lt;a href="https://app.butterneck.com/trial" rel="noopener noreferrer"&gt;try a request on a sample shop&lt;/a&gt; before connecting a computer. If you're not signed in, you're asked to create a free account first. On your own project, the edit runs on a developer's connected computer, and a developer still decides what ships.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to know before you try this
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Your AI provider's terms apply.&lt;/strong&gt; The coding CLI on the connected computer sends code context to its own provider, under that provider's terms. The signed-in plan has to allow use on your team's behalf.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Not everything stays on the computer.&lt;/strong&gt; Files are edited on the connected computer, but chat messages and preview traffic go through Butterneck.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;.env&lt;/code&gt; is a guardrail, not a hard block.&lt;/strong&gt; Secret settings files are on an ignore list the AI is told to stay out of. That is an instruction, so keep production secrets off that computer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The computer has to be on&lt;/strong&gt; for the preview to load and for work to start.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What is vibe coding for teams?
&lt;/h3&gt;

&lt;p&gt;It is vibe coding with roles: anyone on the product team can describe a change in plain words and see it on a running copy of the app, and a developer reviews the change and decides whether it ships. It keeps the fast loop and adds a written policy and a review step.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is vibe coding safe for a production codebase?
&lt;/h3&gt;

&lt;p&gt;It can be, if the change is checked by the person who asked and reviewed by a developer before it goes live, and if requests that touch auth, payments or data go to an engineer first. Keep production secrets off the machine the AI works on.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which vibe coding tools work for teams?
&lt;/h3&gt;

&lt;p&gt;Look for tools that work on your existing app, let you choose who can send requests, show the change on a running copy, and leave the release decision to a developer. Butterneck is one option: requests are made on a live preview, and the developer's own Claude Code, Cursor or Antigravity makes the edit on a developer's connected computer.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does Butterneck open pull requests?
&lt;/h3&gt;

&lt;p&gt;No. It edits files in the connected project and stops. A developer decides whether to commit, open a pull request, or discard it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://calendar.app.google/p2McAaz4ZwXBiG5m9" rel="noopener noreferrer"&gt;Book a 30-minute demo&lt;/a&gt; and we'll run a real request with your team, or see &lt;a href="https://www.butterneck.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt; and start on the free Starter plan.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productmanagement</category>
      <category>productivity</category>
      <category>webdev</category>
    </item>
    <item>
      <title>AI change requests: agentic coding for product teams</title>
      <dc:creator>Butterneck</dc:creator>
      <pubDate>Thu, 05 Nov 2026 05:36:21 +0000</pubDate>
      <link>https://dev.to/butterneck/agentic-coding-for-product-teams-what-it-is-and-how-non-developers-can-use-it-29af</link>
      <guid>https://dev.to/butterneck/agentic-coding-for-product-teams-what-it-is-and-how-non-developers-can-use-it-29af</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.butterneck.com/blog/agentic-coding-for-product-teams" rel="noopener noreferrer"&gt;butterneck.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;"Agentic coding" is the word for AI that doesn't just suggest the next line, but takes a task, reads the codebase, edits several files, runs commands and checks its own work. Claude Code, Cursor's agent and Antigravity all work this way. For developers it changes how work gets done. For the rest of the product team, it raises a new question: if the agent can do the edit, does a PM or designer still have to wait in the backlog for a small change?&lt;/p&gt;

&lt;p&gt;This post explains agentic coding in plain terms, what it does well and badly, and how non-developers can use it without a terminal. We make Butterneck, so we say how it fits near the end.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Agentic coding, in short:&lt;/strong&gt; An AI coding agent takes a goal in plain words, plans the steps, edits files across the project and checks the result, instead of completing one line at a time. In Butterneck, a PM or designer can give that goal on a live preview of the app, the coding agent a developer already uses makes the edit on a developer's connected computer, and a developer still decides what ships.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Agentic coding vs AI autocomplete
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;AI autocomplete&lt;/th&gt;
&lt;th&gt;Agentic coding&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;What you give it&lt;/td&gt;
&lt;td&gt;The code you're typing&lt;/td&gt;
&lt;td&gt;A task in plain words&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;What it does&lt;/td&gt;
&lt;td&gt;Suggests the next lines&lt;/td&gt;
&lt;td&gt;Reads the project, plans, edits several files, can run commands&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who drives it&lt;/td&gt;
&lt;td&gt;A developer, line by line&lt;/td&gt;
&lt;td&gt;A developer, or anyone allowed to send it a task&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;What you check&lt;/td&gt;
&lt;td&gt;Each suggestion&lt;/td&gt;
&lt;td&gt;The finished change&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The shift matters because the input is now plain language. Plain language is something a PM, designer or support lead can already write.&lt;/p&gt;

&lt;h2&gt;
  
  
  What agentic coding is good at, and where it needs a person
&lt;/h2&gt;

&lt;p&gt;Good fits are small, well-described changes on an app that already runs: copy, layout, a clearer error message, an empty state, a missing field on a form. The agent can find the right files faster than someone new to the codebase.&lt;/p&gt;

&lt;p&gt;It needs a person when the request is ambiguous, when the change touches auth, payments or data, or when "correct" depends on context the agent can't see. That is why most teams keep two checks: the person who asked confirms it's what they meant, and a developer reviews the diff. Read more in &lt;a href="https://www.butterneck.com/blog/human-in-the-loop-ai-coding" rel="noopener noreferrer"&gt;human-in-the-loop AI coding&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How non-developers can use agentic coding today
&lt;/h2&gt;

&lt;p&gt;There are two common ways:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Run the agent yourself.&lt;/strong&gt; Get a seat for Claude Code or Cursor, access to the repo and a way to run the app. It suits PMs who want to learn the codebase; see &lt;a href="https://www.butterneck.com/blog/claude-code-for-product-managers" rel="noopener noreferrer"&gt;Claude Code for product managers&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ask on a running app and let a developer's agent do the edit.&lt;/strong&gt; No repo, terminal or AI seat for the requester. A developer still reviews and ships.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  How Butterneck uses agentic coding
&lt;/h2&gt;

&lt;p&gt;A developer connects a computer that already has the project and a coding CLI signed in: Claude Code (&lt;code&gt;claude&lt;/code&gt;), Cursor's CLI (&lt;code&gt;agent&lt;/code&gt;) or Antigravity (&lt;code&gt;agy&lt;/code&gt;). The app runs on that computer's dev server, and Butterneck gives it a share link.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A teammate opens the link and types the request in a chat next to the screen they mean, or labels a Jira ticket &lt;code&gt;butterneck&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;The agent edits the connected project, and the preview updates on the same link.&lt;/li&gt;
&lt;li&gt;If a turn goes wrong it can be stopped, and its file changes are usually rolled back (if not, the chat says so).&lt;/li&gt;
&lt;li&gt;A developer reads the conversation, checks the change, and ships it through the team's normal process, or discards it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Butterneck does not commit, push or open a pull request, and it never merges or deploys. We call these requests AI change requests; see &lt;a href="https://www.butterneck.com/blog/ai-change-requests-for-product-teams" rel="noopener noreferrer"&gt;AI change requests for product teams&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;See it before you set anything up:&lt;/strong&gt; &lt;a href="https://app.butterneck.com/trial" rel="noopener noreferrer"&gt;try a request on a sample shop&lt;/a&gt; before connecting a computer. If you're not signed in, you're asked to create a free account first. On your own project, the edit runs on a developer's connected computer, and a developer still decides what ships.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to know before you try this
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Your AI provider's terms apply.&lt;/strong&gt; The coding CLI on the connected computer sends code context to its own provider, under that provider's terms. The signed-in plan has to allow use on your team's behalf.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Not everything stays on the computer.&lt;/strong&gt; Files are edited on the connected computer, but chat messages and preview traffic go through Butterneck.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;.env&lt;/code&gt; is a guardrail, not a hard block.&lt;/strong&gt; Secret settings files are on an ignore list the AI is told to stay out of. That is an instruction, so keep production secrets off that computer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The computer has to be on&lt;/strong&gt; for the preview to load and for work to start.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What is agentic coding?
&lt;/h3&gt;

&lt;p&gt;Agentic coding is when an AI coding agent takes a task in plain words, reads the project, plans the steps, edits several files and checks the result, rather than suggesting one line at a time. Claude Code, Cursor's agent and Antigravity are examples.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can non-developers use agentic coding?
&lt;/h3&gt;

&lt;p&gt;Yes. They can run an agent themselves if they have repo access and a seat, or ask for a change on a running copy of the app and let a developer's agent do the edit. Either way, a developer should still review the change and decide what ships.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is there an AI coding agent for PMs and designers, not only developers?
&lt;/h3&gt;

&lt;p&gt;Yes, if the agent stays with a developer. With Butterneck, a PM or designer opens a share link to the running app, asks for the change in plain words, and sees it on the live preview. The edit is made by the coding agent signed in on a developer's connected computer (Claude Code, Cursor's agent CLI or Antigravity), and a developer reviews the change and decides what ships. Butterneck does not commit, push, open a pull request, merge or deploy. For the designer's side, see &lt;a href="https://www.butterneck.com/blog/how-non-engineers-can-ship-frontend-changes-as-pull-requests" rel="noopener noreferrer"&gt;how non-engineers can ship frontend changes as pull requests&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does agentic coding replace code review?
&lt;/h3&gt;

&lt;p&gt;No. The agent can check its own work, but someone still needs to confirm the change is what was asked for and a developer needs to decide whether it ships.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which coding agents does Butterneck work with?
&lt;/h3&gt;

&lt;p&gt;Claude Code, Cursor's agent CLI and Antigravity, signed in on the developer's connected computer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://calendar.app.google/p2McAaz4ZwXBiG5m9" rel="noopener noreferrer"&gt;Book a 30-minute demo&lt;/a&gt;, or see &lt;a href="https://www.butterneck.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt; and start on the free Starter plan.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productmanagement</category>
      <category>productivity</category>
      <category>webdev</category>
    </item>
    <item>
      <title>AI change requests: AI app builder vs your existing app</title>
      <dc:creator>Butterneck</dc:creator>
      <pubDate>Thu, 05 Nov 2026 05:35:42 +0000</pubDate>
      <link>https://dev.to/butterneck/ai-app-builder-or-change-the-app-you-already-have-how-product-teams-should-choose-1f1h</link>
      <guid>https://dev.to/butterneck/ai-app-builder-or-change-the-app-you-already-have-how-product-teams-should-choose-1f1h</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.butterneck.com/blog/ai-app-builder-vs-changing-your-existing-app" rel="noopener noreferrer"&gt;butterneck.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;AI app builders have become a popular kind of AI tool. You describe an app, and the builder generates it, hosts it and lets you keep refining it by chat. For a new idea, a prototype or an internal tool, that is often the quickest path there is.&lt;/p&gt;

&lt;p&gt;Many product teams have a different problem. They already have an app, with customers, a codebase, tests and a release process. What they need is not a new app but small changes to the one they ship. This post compares the two paths and helps you pick. We make Butterneck, which is built for the second one, so we are not neutral.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;AI app builder vs changing your existing app, in short:&lt;/strong&gt; Use an AI app builder when you're starting something new and are happy for the builder to generate and host it. When the product already exists, change it where it lives: in Butterneck, a PM asks on a live preview of the running app, the coding agent a developer already uses edits the existing project on a developer's connected computer, and a developer still decides what ships.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  What an AI app builder is good for
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;New products and prototypes.&lt;/strong&gt; Going from an idea to something clickable in an afternoon.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Internal tools.&lt;/strong&gt; Dashboards, forms and admin screens that don't need to fit an existing codebase.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;People without a development team.&lt;/strong&gt; Many builders also handle hosting and other infrastructure, so there is less to set up.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where an AI app builder is a poor fit
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;You already have the app.&lt;/strong&gt; Rebuilding it inside a builder means a second codebase, or a migration. Some builders can now import an existing repository and work on a branch of it; check who reviews each change and whether the builder can merge it for you.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Your release process matters.&lt;/strong&gt; Branch rules, CI, code review and a deploy pipeline belong to the app you already run.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The change is small.&lt;/strong&gt; A copy change or layout fix on a live product doesn't need a new project.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Side by side
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;AI app builder&lt;/th&gt;
&lt;th&gt;Change the existing app (Butterneck)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Starting point&lt;/td&gt;
&lt;td&gt;A prompt, usually a new project&lt;/td&gt;
&lt;td&gt;The app your team already runs&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Where the code lives&lt;/td&gt;
&lt;td&gt;Usually in the builder, often with an export or sync option&lt;/td&gt;
&lt;td&gt;Your existing project, on the developer's connected computer&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who makes the edit&lt;/td&gt;
&lt;td&gt;The builder's own AI&lt;/td&gt;
&lt;td&gt;The developer's own Claude Code, Cursor or Antigravity&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Where the change is checked&lt;/td&gt;
&lt;td&gt;The builder's preview&lt;/td&gt;
&lt;td&gt;A live preview of the developer's running dev server&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who decides what ships&lt;/td&gt;
&lt;td&gt;Depends on the builder and your setup&lt;/td&gt;
&lt;td&gt;A developer, through your normal process&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Good for&lt;/td&gt;
&lt;td&gt;New apps, prototypes, internal tools&lt;/td&gt;
&lt;td&gt;Small changes to a product that already runs&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Check each builder's own docs for how it handles code ownership, Git and hosting; they differ.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Butterneck changes the app you already have
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;A developer installs the Butterneck connector on a computer with the project and a coding CLI signed in.&lt;/li&gt;
&lt;li&gt;They start the app; Butterneck gives the running dev server a share link.&lt;/li&gt;
&lt;li&gt;A PM or designer opens the link and types the change next to the screen they mean.&lt;/li&gt;
&lt;li&gt;The coding agent edits the existing project, and the preview updates.&lt;/li&gt;
&lt;li&gt;A developer reviews the change and ships it the usual way, or throws it away.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Butterneck does not commit, push or open a pull request, and it never merges or deploys. For more tools in this category, see &lt;a href="https://www.butterneck.com/blog/tools-for-non-developers-to-change-an-existing-app" rel="noopener noreferrer"&gt;tools for non-developers to change an existing app&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;See it before you set anything up:&lt;/strong&gt; &lt;a href="https://app.butterneck.com/trial" rel="noopener noreferrer"&gt;try a request on a sample shop&lt;/a&gt; before connecting a computer. If you're not signed in, you're asked to create a free account first. On your own project, the edit runs on a developer's connected computer, and a developer still decides what ships.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to know before you try this
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Your AI provider's terms apply.&lt;/strong&gt; The coding CLI on the connected computer sends code context to its own provider, under that provider's terms. The signed-in plan has to allow use on your team's behalf.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Not everything stays on the computer.&lt;/strong&gt; Files are edited on the connected computer, but chat messages and preview traffic go through Butterneck.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;.env&lt;/code&gt; is a guardrail, not a hard block.&lt;/strong&gt; Secret settings files are on an ignore list the AI is told to stay out of. That is an instruction, so keep production secrets off that computer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The computer has to be on&lt;/strong&gt; for the preview to load and for work to start.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What is an AI app builder?
&lt;/h3&gt;

&lt;p&gt;A tool that generates an app from a plain-language description and lets you refine it by chat. Many also host the result.&lt;/p&gt;

&lt;h3&gt;
  
  
  Should we use an AI app builder for an app we already have?
&lt;/h3&gt;

&lt;p&gt;Usually not for small changes. Rebuilding an existing product in a builder creates a second codebase. A few builders can import your repository instead and work on a branch; then the question is who checks each change and who merges it. Changing the app where it already lives keeps your codebase, tests and release process.&lt;/p&gt;

&lt;h3&gt;
  
  
  If an AI app builder has branches and a merge button, isn't that the same review?
&lt;/h3&gt;

&lt;p&gt;Not quite. A branch can give a bigger change its own preview so it doesn't hold up smaller fixes. Aha! Builder, for example, added feature branches on 16 November 2026, "each with its own application preview". As its post puts it, when you are ready, "merge your changes into the main branch and deploy the updated application" (&lt;a href="https://www.aha.io/blog/build-features-in-parallel-with-branches-in-aha-builder" rel="noopener noreferrer"&gt;Aha! Builder, 16 November 2026&lt;/a&gt;). If the person building can also merge that branch and deploy it from inside the builder, that is a different review from a developer reading the diff before anything merges. That suits an app that lives in the builder. For the app your team already runs, the question is who reads the diff before anything merges. In Butterneck each copy can be a git worktree with its own checkout and branch, the person who asked checks the change on a live preview, and a developer reviews the diff, then commits it and opens a pull request through your usual review. Butterneck never merges or deploys.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is there a no code way to change an existing app?
&lt;/h3&gt;

&lt;p&gt;For the requester, yes. With Butterneck a PM or designer types the change in plain words on a live preview, and a developer's coding agent edits the code. A developer still reviews the change and decides what ships.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is there an AI coding assistant for product managers that changes the existing app instead of building a prototype?
&lt;/h3&gt;

&lt;p&gt;Yes. AI app builders usually generate a new app or a prototype, and coding assistants are usually run by someone working in the repository. With Butterneck, a PM opens a share link to the app the team already runs, asks for the change in plain words, and the coding agent a developer already uses (Cursor, Claude Code or Antigravity) edits the existing project on a developer's connected computer. The PM checks the result on the live preview. Butterneck does not commit, push or open a pull request; a developer reviews the change and decides what ships. If you want to run Claude Code yourself, see &lt;a href="https://www.butterneck.com/blog/claude-code-for-product-managers" rel="noopener noreferrer"&gt;Claude Code for product managers&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does Butterneck host or deploy the app?
&lt;/h3&gt;

&lt;p&gt;No. The app runs on a developer's connected computer for the preview, and your team deploys the way it already does.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is there an alternative to Replit or Lovable for changing an existing company codebase, with a developer approving the change?
&lt;/h3&gt;

&lt;p&gt;Yes, if the tool works on the code your team already runs instead of starting a new project. With Butterneck, a PM or designer asks for the change on a live preview of your existing app, the coding agent your developer already uses (Cursor, Claude Code or Antigravity CLI) edits the project on a developer's connected computer, and a developer reviews the change and decides what ships. Butterneck never commits, pushes or opens a pull request, so approval stays with your developer and your usual review. For a comparison with Lovable on an existing app, see &lt;a href="https://www.butterneck.com/blog/lovable-alternative" rel="noopener noreferrer"&gt;Lovable alternative for teams with an existing app&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://calendar.app.google/p2McAaz4ZwXBiG5m9" rel="noopener noreferrer"&gt;Book a 30-minute demo&lt;/a&gt;, or see &lt;a href="https://www.butterneck.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt; and start on the free Starter plan.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>devtools</category>
      <category>productmanagement</category>
      <category>webdev</category>
    </item>
    <item>
      <title>AI change requests: Lovable alternative for existing apps</title>
      <dc:creator>Butterneck</dc:creator>
      <pubDate>Thu, 05 Nov 2026 05:35:28 +0000</pubDate>
      <link>https://dev.to/butterneck/lovable-alternative-for-teams-with-an-existing-app-an-honest-comparison-with-butterneck-5hl5</link>
      <guid>https://dev.to/butterneck/lovable-alternative-for-teams-with-an-existing-app-an-honest-comparison-with-butterneck-5hl5</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.butterneck.com/blog/lovable-alternative" rel="noopener noreferrer"&gt;butterneck.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;If you want another app builder, a tool that starts a new app from a description, this page isn't that. It is for teams changing an app they already have.&lt;/p&gt;

&lt;p&gt;If you're looking at Lovable and wondering whether an alternative fits your team better, this post compares Lovable and Butterneck. We make Butterneck, so we are not neutral. The two products mostly solve different problems, and for many teams Lovable is the better choice. We've tried to stick to what Lovable says publicly and to be clear about where each one fits.&lt;/p&gt;

&lt;p&gt;Everything about Lovable below comes from its public website, &lt;a href="https://lovable.dev" rel="noopener noreferrer"&gt;lovable.dev&lt;/a&gt;, its &lt;a href="https://docs.lovable.dev/integrations/github" rel="noopener noreferrer"&gt;GitHub integration docs&lt;/a&gt;, and its &lt;a href="https://docs.lovable.dev/features/projects/import-project" rel="noopener noreferrer"&gt;import guide&lt;/a&gt;, as read on 18 November 2026. Lovable changes quickly, so check its site for current details.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Lovable vs Butterneck, in short:&lt;/strong&gt; Lovable is an AI app builder: you describe what you want and it builds, hosts and runs the app, with optional two-way sync to a new GitHub repository. Butterneck is for teams whose app already exists: a PM asks for a change on a live preview of the running app, the coding agent a developer already uses edits the existing project on a developer's connected computer, Butterneck does not commit, push or open a pull request, and a developer decides what ships.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  What Lovable says it does
&lt;/h2&gt;

&lt;p&gt;Lovable's home page says "If you can describe it, you can build it" and describes creating, running and managing "entire products and businesses from scratch". You describe what you want in plain language and Lovable builds it with you in real time. Lovable says it handles "hosting, SSL, and backend infrastructure", along with authentication, payments and integrations.&lt;/p&gt;

&lt;p&gt;On code, its GitHub docs say that "your project code is stored and managed inside the Lovable platform", and that you can export and two-way sync it with GitHub. A few details from those docs matter for teams with an existing codebase:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Git sync "always creates a new repository"; connecting a project to a repository that already exists isn't supported.&lt;/li&gt;
&lt;li&gt;To start from code you already have, the docs say to download the repository as a ZIP and import it, which "copies the code into a new project". Lovable's import guide says it then rebuilds the app "on TanStack Start" and moves the database and the app's users to Lovable's built-in backend; passwords and sessions don't carry over.&lt;/li&gt;
&lt;li&gt;Lovable "only edits and syncs one branch at a time", and its commits are authored by the Lovable GitHub app identity.&lt;/li&gt;
&lt;li&gt;Its GitHub app can open and update pull requests.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where Lovable is likely the better pick
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;You're building a new product, prototype or internal tool.&lt;/li&gt;
&lt;li&gt;You want hosting and backend infrastructure handled for you.&lt;/li&gt;
&lt;li&gt;You don't have a developer computer that can run the project and stay on.&lt;/li&gt;
&lt;li&gt;You're happy for the app's code to start and live in Lovable, synced to GitHub if you want.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where Butterneck fits instead
&lt;/h2&gt;

&lt;p&gt;Butterneck is built for a team whose app already runs, with its own repo, tests and release process, that wants non-developers to ask for small changes without a second codebase.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A developer connects a computer that already has the project and a coding CLI signed in: Claude Code, Cursor's CLI or Antigravity.&lt;/li&gt;
&lt;li&gt;The app runs on that computer's dev server, and Butterneck gives it a share link.&lt;/li&gt;
&lt;li&gt;A PM or designer opens the link and asks for the change in a chat next to the screen they mean, or labels a Jira ticket.&lt;/li&gt;
&lt;li&gt;The coding CLI edits the existing project, and the preview updates.&lt;/li&gt;
&lt;li&gt;A developer reviews the change and ships it through the team's normal process, or discards it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Butterneck does not host your app, and it does not commit, push, open pull requests, merge or deploy.&lt;/p&gt;

&lt;h2&gt;
  
  
  Side by side
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Lovable (per its public site and docs)&lt;/th&gt;
&lt;th&gt;Butterneck&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Starting point&lt;/td&gt;
&lt;td&gt;A plain-language description; projects start in Lovable&lt;/td&gt;
&lt;td&gt;The app your team already runs&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Existing code&lt;/td&gt;
&lt;td&gt;Import rebuilds the code as a new Lovable project (TanStack Start) and moves the database and users to Lovable's backend; Git sync creates a new repo&lt;/td&gt;
&lt;td&gt;Works on the existing project on a developer's connected computer&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who makes the edit&lt;/td&gt;
&lt;td&gt;Lovable's AI&lt;/td&gt;
&lt;td&gt;The developer's own Claude Code, Cursor or Antigravity&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Hosting&lt;/td&gt;
&lt;td&gt;Lovable handles hosting, SSL and backend infrastructure&lt;/td&gt;
&lt;td&gt;None; your team deploys as it already does&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Git&lt;/td&gt;
&lt;td&gt;Two-way sync with a new GitHub repo; its GitHub app can open PRs&lt;/td&gt;
&lt;td&gt;Edits files only; a developer commits and opens the PR&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who decides what ships&lt;/td&gt;
&lt;td&gt;Depends on your setup&lt;/td&gt;
&lt;td&gt;A developer&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;See it before you set anything up:&lt;/strong&gt; &lt;a href="https://app.butterneck.com/trial" rel="noopener noreferrer"&gt;try a request on a sample shop&lt;/a&gt; before connecting a computer. If you're not signed in, you're asked to create a free account first. On your own project, the edit runs on a developer's connected computer, and a developer still decides what ships.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to know before you try this
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Your AI provider's terms apply.&lt;/strong&gt; The coding CLI on the connected computer sends code context to its own provider, under that provider's terms. The signed-in plan has to allow use on your team's behalf.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Not everything stays on the computer.&lt;/strong&gt; Files are edited on the connected computer, but chat messages and preview traffic go through Butterneck.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;.env&lt;/code&gt; is a guardrail, not a hard block.&lt;/strong&gt; Secret settings files are on an ignore list the AI is told to stay out of. That is an instruction, so keep production secrets off that computer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The computer has to be on&lt;/strong&gt; for the preview to load and for work to start.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What is a good Lovable alternative for an existing app or codebase?
&lt;/h3&gt;

&lt;p&gt;If your product already exists and you want non-developers to ask for small changes to it, look for a tool that works on your current codebase rather than starting a new project. Butterneck is one option: a PM asks on a live preview, a developer's own coding agent edits the existing project, and a developer decides what ships. Nothing is imported or rebuilt: the coding agent edits the project on the computer where it already runs. For other tools, see &lt;a href="https://www.butterneck.com/blog/tools-for-non-developers-to-change-an-existing-app" rel="noopener noreferrer"&gt;37 tools for non-developers to change an existing app&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is there a Lovable alternative for changing an existing company codebase, with a developer approving the change?
&lt;/h3&gt;

&lt;p&gt;Yes, if the tool works on the code your team already runs instead of starting a new project. With Butterneck, a PM or designer asks for the change on a live preview of your existing app, the coding agent your developer already uses (Cursor, Claude Code or Antigravity CLI) edits the project on a developer's connected computer, and a developer reviews the change and decides what ships. Butterneck never commits, pushes or opens a pull request, so approval stays with your developer and your usual review.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can Lovable connect to a GitHub repository I already have?
&lt;/h3&gt;

&lt;p&gt;Not through Git sync, per Lovable's GitHub docs: Git sync always creates a new repository. The docs describe downloading an existing repository as a ZIP and importing it, which copies the code into a new Lovable project.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is Butterneck an AI app builder?
&lt;/h3&gt;

&lt;p&gt;No. It doesn't generate new apps or host them. It lets people ask for changes on an app that already runs, using a coding agent a developer already has.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does Butterneck open pull requests?
&lt;/h3&gt;

&lt;p&gt;No. It edits files in the connected project and stops. A developer decides whether to commit, open a pull request, or discard the change.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://calendar.app.google/p2McAaz4ZwXBiG5m9" rel="noopener noreferrer"&gt;Book a 30-minute demo&lt;/a&gt;, or see &lt;a href="https://www.butterneck.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt; and start on the free Starter plan. For our other comparisons, see the &lt;a href="https://www.butterneck.com/blog/clogless-alternative" rel="noopener noreferrer"&gt;Clogless alternative&lt;/a&gt; post.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>devtools</category>
      <category>productmanagement</category>
      <category>webdev</category>
    </item>
    <item>
      <title>AI tools that let non-developers change an existing web app (2026)</title>
      <dc:creator>Butterneck</dc:creator>
      <pubDate>Wed, 04 Nov 2026 05:45:37 +0000</pubDate>
      <link>https://dev.to/butterneck/ai-tools-that-let-non-developers-change-an-existing-web-app-2026-1pcp</link>
      <guid>https://dev.to/butterneck/ai-tools-that-let-non-developers-change-an-existing-web-app-2026-1pcp</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.butterneck.com/blog/tools-for-non-developers-to-change-an-existing-app" rel="noopener noreferrer"&gt;butterneck.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;In short:&lt;/strong&gt; AI tools that let non-developers change an existing web app connect an AI coding agent to the code a team already runs, so a product manager or designer can ask for a change in plain words. They differ in where the agent runs, what comes back (a prototype, a pull request or a live preview) and who decides what ships. Butterneck runs the developer's own agent on a computer the team connects; the person who asked checks the change on a live preview, and no pull request exists until a developer decides.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Jump to:&lt;/strong&gt; At a glance · How to choose · The tools, one by one · Butterneck · FAQ&lt;/p&gt;

&lt;p&gt;Last checked: 29 October to 19 November 2026. Most price cells say when we read them, and each row links to the page we read; the per-tool check dates are at the end of the post. "Not on the pages we read" means we didn't find it there, not that the product lacks it.&lt;/p&gt;

&lt;p&gt;Product managers, designers, support staff and founders increasingly want to change the app their team already runs, not build a new one. The AI tools below all work on an existing codebase, but they act at different moments: some give you a prototype, some open a pull request for you, some start after a pull request exists, and some stop before one. We make Butterneck, which is listed too; we've tried to describe every tool in its own words and say where each is the better pick.&lt;/p&gt;

&lt;p&gt;Butterneck isn't affiliated with, endorsed by or sponsored by any other tool listed here. Product names and trademarks belong to their owners and are used only to identify the products.&lt;/p&gt;

&lt;h2&gt;
  
  
  At a glance
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Tool&lt;/th&gt;
&lt;th&gt;Who it's for (their words)&lt;/th&gt;
&lt;th&gt;Where the work happens&lt;/th&gt;
&lt;th&gt;What you get back&lt;/th&gt;
&lt;th&gt;Jira&lt;/th&gt;
&lt;th&gt;Published price&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://www.butterneck.com" rel="noopener noreferrer"&gt;Butterneck&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Product teams: anyone who asks for a change, plus the developer who decides&lt;/td&gt;
&lt;td&gt;The developer's agent, on a computer the team connects&lt;/td&gt;
&lt;td&gt;A live preview the requester checks; no PR until a developer decides&lt;/td&gt;
&lt;td&gt;Yes (label and assign a ticket)&lt;/td&gt;
&lt;td&gt;Starter free; Pro USD 19 per person/month (20% off billed annually); one-month Pro trial&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://useronda.com/" rel="noopener noreferrer"&gt;ronda&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;"Marketing, design, and product"&lt;/td&gt;
&lt;td&gt;An isolated live sandbox running your dev server&lt;/td&gt;
&lt;td&gt;"ronda writes the code and opens a pull request. Engineering reviews and merges."&lt;/td&gt;
&lt;td&gt;Not on the pages we read&lt;/td&gt;
&lt;td&gt;Free $0; Starter $9/month; no AI markup. No key needed when you use it from ChatGPT or Claude; the web editor needs your own Anthropic key (as of Nov 11, 2026, per &lt;a href="https://useronda.com/pricing" rel="noopener noreferrer"&gt;ronda's pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://refinar.ai/en/for/product-managers" rel="noopener noreferrer"&gt;Refinar&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Product managers (its /for/product-managers page)&lt;/td&gt;
&lt;td&gt;"A copy of the live app"&lt;/td&gt;
&lt;td&gt;"Publish it or send it to engineering"; risky changes go to a developer first as a draft PR&lt;/td&gt;
&lt;td&gt;Not on the pages we read&lt;/td&gt;
&lt;td&gt;"From $25 a month" for 250 credits (as of Oct 29, 2026, per &lt;a href="https://refinar.ai/en/pricing" rel="noopener noreferrer"&gt;Refinar's pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://fix.dog/" rel="noopener noreferrer"&gt;Fixdog&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;"PMs, designers, operators"&lt;/td&gt;
&lt;td&gt;"Directly on their live product"&lt;/td&gt;
&lt;td&gt;It "auto-generates a PR. Eng reviews and merges."&lt;/td&gt;
&lt;td&gt;Not on the page we read&lt;/td&gt;
&lt;td&gt;No public price found&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://clogless.ai/" rel="noopener noreferrer"&gt;Clogless&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Product teams handing work to engineering&lt;/td&gt;
&lt;td&gt;"A live sandbox on your real codebase", in its cloud&lt;/td&gt;
&lt;td&gt;A pull request it opens with your Git provider&lt;/td&gt;
&lt;td&gt;Yes (one of six ticketing tools, per its &lt;a href="https://clogless.ai/ticket-to-pull-request" rel="noopener noreferrer"&gt;ticket-to-PR page&lt;/a&gt;)&lt;/td&gt;
&lt;td&gt;$99/month Starter, $489/month Team, billed annually (as of Oct 29, 2026, per &lt;a href="https://clogless.ai/pricing" rel="noopener noreferrer"&gt;Clogless's pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://www.revyse.dev/" rel="noopener noreferrer"&gt;Revyse&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;"Founders, designers, product, QA, developers and agencies"&lt;/td&gt;
&lt;td&gt;Your running Next.js app (an overlay in your dev server or on your live site), or a safe copy from its dashboard&lt;/td&gt;
&lt;td&gt;A change on its own branch with a pull request and a preview; it reaches production the way the project chose, with or without a reviewer ("Revyse merges; your host deploys")&lt;/td&gt;
&lt;td&gt;Not on the pages we read&lt;/td&gt;
&lt;td&gt;Free (150 credits a month, one project, just you); Starter $19, Pro $49 and Business $99 a month, by credits (as of Nov 11, 2026, per &lt;a href="https://www.revyse.dev/pricing" rel="noopener noreferrer"&gt;Revyse's pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://revise.build/" rel="noopener noreferrer"&gt;Revise&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;People who want to edit "your existing website without writing code"; Pro is "For teams with a frontend bottleneck"&lt;/td&gt;
&lt;td&gt;"A separate preview" in its cloud workspace, connected to GitHub, GitLab or Bitbucket&lt;/td&gt;
&lt;td&gt;"A pull or merge request" your developer reviews and merges; it "does not automatically publish the change"&lt;/td&gt;
&lt;td&gt;Not on the pages we read&lt;/td&gt;
&lt;td&gt;Free one-time $0.50 AI + $0.50 workspace budget; Pro $29 per editor per month, but "Paid subscriptions and top-ups are not available yet" (as of Nov 6, 2026, per &lt;a href="https://revise.build/pricing" rel="noopener noreferrer"&gt;Revise's pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://plusma.ai/" rel="noopener noreferrer"&gt;Plusma&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;PMs and designers ("No terminal, no IDE")&lt;/td&gt;
&lt;td&gt;"An instant preview environment" built from your GitHub repo&lt;/td&gt;
&lt;td&gt;"A clean pull request… ready for your engineering team to review and merge"&lt;/td&gt;
&lt;td&gt;Not on the page we read&lt;/td&gt;
&lt;td&gt;No public price found&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://productmind.ai/product/produtyping-and-coding-sessions/" rel="noopener noreferrer"&gt;Productmind&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Product teams; its PM page says "Hand engineering a pull request, not a ticket."&lt;/td&gt;
&lt;td&gt;"an isolated sandbox" in Productmind's cloud, or on your own machine with the Productmind CLI, where it "orchestrates your own Claude Code or Codex agent"&lt;/td&gt;
&lt;td&gt;"The agent opens a pull request, a change your engineers can review and merge"; "Productmind never merges a pull request on its own"&lt;/td&gt;
&lt;td&gt;Not on the pages we read&lt;/td&gt;
&lt;td&gt;Early: pay-as-you-go, no monthly fee; Start €49.99/user/month; Scale €99.99/user/month; 20% off yearly; usage paid from a balance you top up; prices exclude VAT (as of Nov 11, 2026, per &lt;a href="https://productmind.ai/pricing/" rel="noopener noreferrer"&gt;Productmind's pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://vixentio.ai/" rel="noopener noreferrer"&gt;Vixentio&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;"Many agents. One team."&lt;/td&gt;
&lt;td&gt;A multiplayer workspace: isolated cloud sandboxes or teammates' Macs, running Claude Code, Codex and Gemini CLI in parallel&lt;/td&gt;
&lt;td&gt;Named Design, Product and Technical sign-offs; an editor then publishes a branch and the Vixentio GitHub App opens a pull request. "Merging stays your team's decision on GitHub."&lt;/td&gt;
&lt;td&gt;Not on the pages we read (a Jira logo appears on the home page)&lt;/td&gt;
&lt;td&gt;Free $0 for viewers and commenters; Team $39.99 per editor seat a month (an editor seat is needed to start a task); Pro $29.99 and Max $79.99 a month; yearly 20% off; 14-day Team trial (as of Nov 11, 2026, per &lt;a href="https://vixentio.ai/pricing" rel="noopener noreferrer"&gt;Vixentio's pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;a href="https://autonomyai.io/solutions/product-managers/" rel="noopener noreferrer"&gt;Fei Studio&lt;/a&gt; (AutonomyAI)&lt;/td&gt;
&lt;td&gt;Product managers (its /solutions/product-managers page)&lt;/td&gt;
&lt;td&gt;Its own app, no IDE or terminal (&lt;a href="https://autonomyai.io/compare/" rel="noopener noreferrer"&gt;compare page&lt;/a&gt;), or from Claude Code, Cursor or another MCP client (&lt;a href="https://autonomyai.io/product-updates/fei-studio-now-works-inside-claude-code-cursor-and-any-ai-agent/" rel="noopener noreferrer"&gt;MCP announcement&lt;/a&gt;); the change is "Rendered in the real app"&lt;/td&gt;
&lt;td&gt;"A merge-ready pull request in your real codebase — your engineers approve every merge"&lt;/td&gt;
&lt;td&gt;Pulls a Jira issue in by ID or URL as the instructions (&lt;a href="https://help.autonomyai.io/articles/2675572398-do-you-integrate-jira-to-get-relevant-context" rel="noopener noreferrer"&gt;help article&lt;/a&gt;)&lt;/td&gt;
&lt;td&gt;Priced "per task", not per seat (&lt;a href="https://autonomyai.io/compare/" rel="noopener noreferrer"&gt;compare page&lt;/a&gt;); its pricing page wasn't reachable on 29 Oct 2026&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://ovren.ai/" rel="noopener noreferrer"&gt;Ovren&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;"Anyone on the team describes the change. Your developer reviews it"&lt;/td&gt;
&lt;td&gt;"A safe copy of your project", connected through a GitHub App&lt;/td&gt;
&lt;td&gt;"A pull request into your own product, for your team to review", with a live preview of frontend changes; "You or your developer merge it. Ovren never does."&lt;/td&gt;
&lt;td&gt;Not on the page we read&lt;/td&gt;
&lt;td&gt;Free up to 5 changes; Pro "$29 one-time" for up to 50 changes; top-up balance, no subscription (as of Oct 29, 2026, per the pricing answer on &lt;a href="https://ovren.ai/" rel="noopener noreferrer"&gt;Ovren's homepage&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://www.flexenv.com/product-changes" rel="noopener noreferrer"&gt;Flex&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;"Product, operations, and engineering teams"&lt;/td&gt;
&lt;td&gt;A self-hosted runner "in infrastructure your team controls", on your connected repository (a hosted cloud option is "Coming soon")&lt;/td&gt;
&lt;td&gt;"Isolated branches and live previews"; engineers "control the merge"&lt;/td&gt;
&lt;td&gt;Not on the pages we read (Slack, Linear and GitHub are)&lt;/td&gt;
&lt;td&gt;Hobby free (1 member, 3 previews); Starter $60/month (£50) and Team $240/month (£200), unlimited members; your own model keys (as of Oct 29, 2026, per &lt;a href="https://www.flexenv.com/pricing" rel="noopener noreferrer"&gt;Flex's pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://pinappai.com/" rel="noopener noreferrer"&gt;PinAppAI&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Solo founders who "build with v0, Claude Code, or Cursor"; agencies collecting client feedback&lt;/td&gt;
&lt;td&gt;Reviewers pin on the live site; the developer's own agent applies changes&lt;/td&gt;
&lt;td&gt;Edits your agent applies, which reviewers approve or reject on a generated /changes/ page&lt;/td&gt;
&lt;td&gt;Not on the pages we read&lt;/td&gt;
&lt;td&gt;$0 / $9 / $15 per seat (Team, 2-seat min); reviewers free (as of Oct 29, 2026, per &lt;a href="https://pinappai.com/pricing/" rel="noopener noreferrer"&gt;PinAppAI's pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://gethandle.ai/studio" rel="noopener noreferrer"&gt;Handle Studio&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Designers, design engineers, solo founders&lt;/td&gt;
&lt;td&gt;A Mac app (macOS 13+ on Apple Silicon) with your Claude Code, Codex or Rovo Dev agent, on your local repos&lt;/td&gt;
&lt;td&gt;"A clean commit to a remote branch for your team to review"&lt;/td&gt;
&lt;td&gt;Not on the pages we read&lt;/td&gt;
&lt;td&gt;Free and open source&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;a href="https://hexby.ai/" rel="noopener noreferrer"&gt;Hexby&lt;/a&gt; (Locofy)&lt;/td&gt;
&lt;td&gt;"Designers, PMs, and developers working on existing codebases"&lt;/td&gt;
&lt;td&gt;A desktop app that starts your project on your own computer (React, Next.js 13+ or Angular 17+), with your Claude Code, Codex, Cursor, Gemini CLI or GitHub Copilot agent signed in there&lt;/td&gt;
&lt;td&gt;A visual before-and-after review that teammates open "without installing Hexby"; once approved, a hand-off to developers that opens a GitHub pull request&lt;/td&gt;
&lt;td&gt;Not on the pages we read&lt;/td&gt;
&lt;td&gt;Free during beta (as of Oct 30, 2026, per &lt;a href="https://hexby.ai/pricing/" rel="noopener noreferrer"&gt;Hexby's pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;a href="https://help.figma.com/hc/en-us/articles/40775535020695-Make-in-your-local-codebase" rel="noopener noreferrer"&gt;Figma Make&lt;/a&gt; (on your codebase, closed beta)&lt;/td&gt;
&lt;td&gt;Designers and PMs; Figma says designers "who already have access to their company's codebase are best suited" for now&lt;/td&gt;
&lt;td&gt;The Figma Beta desktop app for Mac, on a local repository or one cloned from GitHub; an engineer sets up each repository once&lt;/td&gt;
&lt;td&gt;Local commits on a branch, then "a pull request for your engineering team to review"&lt;/td&gt;
&lt;td&gt;Not on the pages we read&lt;/td&gt;
&lt;td&gt;Closed beta, "available to try for free"; Figma says it won't consume credits during the beta (as of Oct 30, 2026, per Figma's help article and &lt;a href="https://www.figma.com/blog/figma-make-now-on-your-local-code/" rel="noopener noreferrer"&gt;launch post&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://narnia.sh/layrr/" rel="noopener noreferrer"&gt;Layrr&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Developers running a local web app&lt;/td&gt;
&lt;td&gt;A proxy in front of your local dev server, using Claude Code, Codex CLI or Gemini (via Pi)&lt;/td&gt;
&lt;td&gt;It "commits successful edits with a [layrr] prefix"&lt;/td&gt;
&lt;td&gt;Not on the page we read&lt;/td&gt;
&lt;td&gt;Free, open source (MIT, per its &lt;a href="https://github.com/narnia-sh/layrr" rel="noopener noreferrer"&gt;GitHub repo&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://pulsedev.app/" rel="noopener noreferrer"&gt;PulseDev&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;People running a site on their own machine ("On any site you run locally")&lt;/td&gt;
&lt;td&gt;A macOS app on your running local site, using Claude Code, Codex, Gemini CLI or OpenCode&lt;/td&gt;
&lt;td&gt;Source edits that touch your files only after you "approve the diff"&lt;/td&gt;
&lt;td&gt;Not on the page we read&lt;/td&gt;
&lt;td&gt;Free for 1 project; Regular prices: Pro $12/month or $96/year (5-day free trial); Founder Lifetime $149 once for the first 200 buyers; a launch-week promo code was lowering both on Nov 11, 2026 (as of Nov 11, 2026, per the pricing section on &lt;a href="https://pulsedev.app/" rel="noopener noreferrer"&gt;PulseDev's homepage&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://medit.software/" rel="noopener noreferrer"&gt;medit&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Designers, product managers, engineers, and founders (its homepage has a section for each)&lt;/td&gt;
&lt;td&gt;An overlay inside your running app, on the machine where it runs, driving your own Claude Code, Cursor CLI or Codex (or an API key); it opens on other devices on your network (LAN or Tailscale)&lt;/td&gt;
&lt;td&gt;"Every change lands on its own branch with a clean commit"; with a GitHub token, it opens the pull request for you&lt;/td&gt;
&lt;td&gt;Not on the page we read&lt;/td&gt;
&lt;td&gt;Free for personal use; Pro adds PR automation and team access (no price on the page we read, as of Oct 30, 2026)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://modeinspect.com/" rel="noopener noreferrer"&gt;Modeinspect&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Design engineers and product designers&lt;/td&gt;
&lt;td&gt;Cloud design canvas connected to your codebase&lt;/td&gt;
&lt;td&gt;"Every change opens as a normal pull request on a branch"&lt;/td&gt;
&lt;td&gt;Not on the pages we read&lt;/td&gt;
&lt;td&gt;Hobby $0; Pro $20/month per person (as of Oct 29, 2026, per &lt;a href="https://modeinspect.com/pricing" rel="noopener noreferrer"&gt;Modeinspect's pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://www.builder.io/for/product-managers" rel="noopener noreferrer"&gt;Builder.io&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Product managers, with stakeholders commenting&lt;/td&gt;
&lt;td&gt;Builder's visual editor and agent on your Git repo (GitHub, GitLab or Bitbucket), starting from "the Slack thread, Jira ticket, or PRD"&lt;/td&gt;
&lt;td&gt;The change "reaches engineering as code in their own stack, so they can review, merge, and release it"&lt;/td&gt;
&lt;td&gt;Yes, on Team ("Builder Agent in Slack and JIRA")&lt;/td&gt;
&lt;td&gt;Free $0; Pro $24 and Team $40 per user/month billed annually (as of Oct 31, 2026, per &lt;a href="https://www.builder.io/pricing" rel="noopener noreferrer"&gt;Builder.io's pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://www.netlify.com/solutions/prototypes/" rel="noopener noreferrer"&gt;Netlify Agent Runners&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Product managers, designers and developers&lt;/td&gt;
&lt;td&gt;Netlify's cloud, on your Git repository, with Claude Code, OpenAI Codex, Google Antigravity, Meta Muse or OpenCode&lt;/td&gt;
&lt;td&gt;A branch, a deploy preview and a pull request ("Every prompt creates a branch. Every change gets a deploy preview.")&lt;/td&gt;
&lt;td&gt;Not on the pages we read&lt;/td&gt;
&lt;td&gt;Included from the Free plan ($0); Personal $9/month; Pro $20/month with unlimited members; usage is credit-based (as of Nov 19, 2026, per &lt;a href="https://www.netlify.com/pricing/" rel="noopener noreferrer"&gt;Netlify's pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://docs.workshop.ai/solutions/prototyping" rel="noopener noreferrer"&gt;Workshop&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;PMs, designers, founders, researchers&lt;/td&gt;
&lt;td&gt;Cloud, or Desktop with your codebase via GitHub&lt;/td&gt;
&lt;td&gt;"A clickable prototype… with mocked data"&lt;/td&gt;
&lt;td&gt;Not in the docs index&lt;/td&gt;
&lt;td&gt;$0 / $20 / $50 / $200 a month (credits; as of Oct 29, 2026, per &lt;a href="https://workshop.ai/pricing" rel="noopener noreferrer"&gt;Workshop's pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://www.somethingelse.ai/" rel="noopener noreferrer"&gt;Else&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Teams reviewing a PR (engineer, QA, designer, PM)&lt;/td&gt;
&lt;td&gt;A hosted preview environment running your full stack&lt;/td&gt;
&lt;td&gt;Edits in the preview of a PR an engineer already opened&lt;/td&gt;
&lt;td&gt;Not on the homepage&lt;/td&gt;
&lt;td&gt;No public price ("Start for free")&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://synlets.com/" rel="noopener noreferrer"&gt;Synlets&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;PMs, founders, engineering leads&lt;/td&gt;
&lt;td&gt;Its cloud, with your repo cloned at runtime&lt;/td&gt;
&lt;td&gt;"A reviewable pull request"; "nothing is merged without your approval"&lt;/td&gt;
&lt;td&gt;Yes (Jira and Asana integration)&lt;/td&gt;
&lt;td&gt;$79–$999/month (credits), no per-seat fees; free tier (as of Oct 29, 2026, per the pricing section on &lt;a href="https://synlets.com/" rel="noopener noreferrer"&gt;Synlets' homepage&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;a href="https://inspect.com/" rel="noopener noreferrer"&gt;Inspect&lt;/a&gt; (by Ramp; early access)&lt;/td&gt;
&lt;td&gt;Ramp's "engineering, design, and product teams" (Ramp's own use)&lt;/td&gt;
&lt;td&gt;Ramp's cloud ("Inspect runs in the cloud")&lt;/td&gt;
&lt;td&gt;"A visually validated and fully reviewed pull request"&lt;/td&gt;
&lt;td&gt;Not on the pages we read (tasks come from Slack, GitHub, Linear or the web)&lt;/td&gt;
&lt;td&gt;No public price found; early access by application (as of Oct 30, 2026, per &lt;a href="https://ramp.com/blog/introducing-inspect" rel="noopener noreferrer"&gt;Ramp's launch post&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://vson.ai/" rel="noopener noreferrer"&gt;Vision&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;"Technical and nontechnical teammates" building together (its pricing FAQ)&lt;/td&gt;
&lt;td&gt;"An isolated environment" for every change, from your connected GitHub repo, in a shared live session&lt;/td&gt;
&lt;td&gt;"Readable pull requests" an engineer reviews; approved changes ship "with one click"&lt;/td&gt;
&lt;td&gt;Not on the pages we read&lt;/td&gt;
&lt;td&gt;Free $0 ($20 in credits); Individual $25/month; Teams $50 per member per month, usage-based (as of Oct 30, 2026, per &lt;a href="https://vson.ai/pricing" rel="noopener noreferrer"&gt;its pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://remix.one/" rel="noopener noreferrer"&gt;Remix&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Product teams ("multiplayer AI for product teams"); "Your team and AI PM" work together&lt;/td&gt;
&lt;td&gt;"A live copy of your real app", from your connected GitHub repo (or a clone of your website until you connect it)&lt;/td&gt;
&lt;td&gt;Variants that each become "a pull request anyone can review", with the prompts behind it and "a link to run it live"&lt;/td&gt;
&lt;td&gt;Not on the pages we read&lt;/td&gt;
&lt;td&gt;Free (up to 2 collaborators); Pro $29 per seat/month; Teams $99 per seat/month (as of Oct 30, 2026, per &lt;a href="https://remix.one/pricing" rel="noopener noreferrer"&gt;its pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://lightsprint.ai/" rel="noopener noreferrer"&gt;Lightsprint&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;"PMs, designers and ops" (its homepage)&lt;/td&gt;
&lt;td&gt;"a live, shared sandbox" inside its "shared cloud workspace", on your existing codebase&lt;/td&gt;
&lt;td&gt;A PR to GitHub, GitLab or Bitbucket; "engineering controls every merge"&lt;/td&gt;
&lt;td&gt;Yes, on Pro (start a task from Linear, Jira or Slack)&lt;/td&gt;
&lt;td&gt;Free $0 ("5 free tasks and plans weekly"); Pro $40 per seat/month, up to 20 seats (as of Oct 30, 2026, per &lt;a href="https://lightsprint.ai/pricing" rel="noopener noreferrer"&gt;Lightsprint's pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://sparkles.dev/" rel="noopener noreferrer"&gt;Sparkles&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;"anyone on your team"&lt;/td&gt;
&lt;td&gt;"an isolated cloud sandbox" from your connected GitHub repo, with Claude Code, Codex or OpenCode&lt;/td&gt;
&lt;td&gt;"a pull request your team reviews"; you can merge from its app "when everything is green"&lt;/td&gt;
&lt;td&gt;Not on the page we read (Jira is listed among its integrations, as a tool agents can use)&lt;/td&gt;
&lt;td&gt;100 free credits; plans from $50/month (as of Oct 30, 2026, per &lt;a href="https://sparkles.dev/" rel="noopener noreferrer"&gt;Sparkles' homepage&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://alloy.app/cloud-agents" rel="noopener noreferrer"&gt;Alloy&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Product teams ("Product managers and designers use cloud agents to propose real changes as pull requests", per its FAQ)&lt;/td&gt;
&lt;td&gt;"Your product codebase running in the cloud", from your connected GitHub repo; you can "share a link for feedback"&lt;/td&gt;
&lt;td&gt;A pull request you open from the session&lt;/td&gt;
&lt;td&gt;Yes (a Jira integration is listed on every plan, per its pricing page)&lt;/td&gt;
&lt;td&gt;Free $0 (unlimited users, $5 credits per user/month); Pro $20 per user/month (as of Oct 30, 2026, per &lt;a href="https://alloy.app/pricing" rel="noopener noreferrer"&gt;Alloy's pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://docs.kosuke.ai/guides/change-without-code" rel="noopener noreferrer"&gt;Kosuke&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;People on the team who don't write code ("You can change your product without writing code"), once an engineer has imported and deployed the project&lt;/td&gt;
&lt;td&gt;Kosuke's cloud sandboxes, running "your preferred coding agent with your subscription" (Claude Code, Codex, GLM Coding Plan or Kimi Code)&lt;/td&gt;
&lt;td&gt;A pull request: "check it in the Preview, and press Open PR"; "Your engineers review and merge the pull request as usual"&lt;/td&gt;
&lt;td&gt;Jira is listed among its integrations (per &lt;a href="https://docs.kosuke.ai/workspace/personal-integrations" rel="noopener noreferrer"&gt;Your own integrations&lt;/a&gt;); we didn't see how tickets start work&lt;/td&gt;
&lt;td&gt;Starter $20/month and Pro $190/month billed monthly, each with monthly sandbox credits; priced by sandbox hours, and your own coding-agent subscription is required (as of Oct 31, 2026, per &lt;a href="https://kosuke.ai/pricing" rel="noopener noreferrer"&gt;Kosuke's pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://specship.dev/" rel="noopener noreferrer"&gt;Specship&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Founders and small teams&lt;/td&gt;
&lt;td&gt;Connected GitHub repo&lt;/td&gt;
&lt;td&gt;Acceptance criteria, failing tests, code and "review-ready pull requests"; optional auto-merge (beta)&lt;/td&gt;
&lt;td&gt;Planned or in beta (GitHub and ClickUp today)&lt;/td&gt;
&lt;td&gt;"Pricing TBD" (waitlist)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://coderhelm.com/" rel="noopener noreferrer"&gt;CoderHelm&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Engineering teams on GitHub, Jira and AWS&lt;/td&gt;
&lt;td&gt;Hosted, or in your own AWS account&lt;/td&gt;
&lt;td&gt;A pull request on a &lt;code&gt;coderhelm/\&lt;/code&gt; branch; auto-merge off by default&lt;/td&gt;
&lt;td&gt;Yes (label or assign)&lt;/td&gt;
&lt;td&gt;Closed beta; bring your own Anthropic key&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://www.epicraft.dev/" rel="noopener noreferrer"&gt;Epicraft&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;"The PM is the user, not the developer"&lt;/td&gt;
&lt;td&gt;From a Jira ticket assigned to its bot&lt;/td&gt;
&lt;td&gt;A branch and a pull request; "You review the PR in GitHub, approve, merge"&lt;/td&gt;
&lt;td&gt;Yes (assign the ticket to its bot)&lt;/td&gt;
&lt;td&gt;No public price found&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://codeherder.com/for-product-teams" rel="noopener noreferrer"&gt;CodeHerder&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Product people "whose engineers are booked on roadmap work"&lt;/td&gt;
&lt;td&gt;Agents on a device you connect (your machine, or your AWS account), using a coding agent CLI signed in there&lt;/td&gt;
&lt;td&gt;Its agents plan, code, review and merge; "No stage waits for a person by default" (approval gates optional)&lt;/td&gt;
&lt;td&gt;Not on the pages we read&lt;/td&gt;
&lt;td&gt;Free $0; Starter $19/month; Pro $49/month (concurrent agents, not seats), shown as "indicative and not yet billed"; hosted service invite-only (as of Oct 29, 2026, per &lt;a href="https://codeherder.com/pricing" rel="noopener noreferrer"&gt;CodeHerder's pricing page&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Itera is covered below and in our &lt;a href="https://www.butterneck.com/blog/itera-alternative" rel="noopener noreferrer"&gt;Itera alternative&lt;/a&gt; post; we couldn't re-check its site on 29 Oct 2026, so it isn't in the table.&lt;/p&gt;

&lt;h2&gt;
  
  
  The tools, one by one
&lt;/h2&gt;

&lt;h3&gt;
  
  
  ronda
&lt;/h3&gt;

&lt;p&gt;"Small changes shouldn't wait on engineering." Marketing, design and product describe the change in plain English, it runs in an isolated live sandbox on your dev server, and "ronda writes the code and opens a pull request. Engineering reviews and merges." You can use it from ChatGPT or Claude with no key to add, or in its web editor with your own Anthropic key. Good pick if you want a pull request from a plain-English request on a small budget.&lt;/p&gt;

&lt;h3&gt;
  
  
  Refinar
&lt;/h3&gt;

&lt;p&gt;"Describe a change to your product, watch it built on a copy of the live app, then publish it or send it to engineering. No terminal or GitHub account." Risky changes go to a developer first as a draft PR. The clearest difference from Butterneck: Refinar lets the person who asked publish small changes themselves. Good pick if that is what you want.&lt;/p&gt;

&lt;h3&gt;
  
  
  Fixdog
&lt;/h3&gt;

&lt;p&gt;It "lets PMs, designers, operators make changes directly on their live product and auto-generates a PR. Eng reviews and merges." We couldn't find a public price. Good pick if you want an auto-generated PR from a change made on the live product.&lt;/p&gt;

&lt;h3&gt;
  
  
  Itera
&lt;/h3&gt;

&lt;p&gt;(From its site as we read it on 28 October 2026; we couldn't reach it on 29 October.) Lets the team "propose changes to your live web product through chat" and "submit it for engineering review" as AI-generated pull requests. Builders pay per seat; "Collaborators are always free". Good pick for teams that want a PR from a chat on the live product. We compare it in more detail in our &lt;a href="https://www.butterneck.com/blog/itera-alternative" rel="noopener noreferrer"&gt;Itera alternative&lt;/a&gt; post.&lt;/p&gt;

&lt;h3&gt;
  
  
  Clogless
&lt;/h3&gt;

&lt;p&gt;"A live sandbox on your real codebase. Ship changes as pull requests that engineering reviews." It runs in its own cloud sandbox and connects to six ticketing tools, Jira included. Good pick if you want a cloud workspace that turns tickets into PRs. More in our &lt;a href="https://www.butterneck.com/blog/clogless-alternative" rel="noopener noreferrer"&gt;Clogless alternative&lt;/a&gt; post.&lt;/p&gt;

&lt;h3&gt;
  
  
  Revyse
&lt;/h3&gt;

&lt;p&gt;"Click what you want different, or describe something new. Revyse writes the code, checks it and shows it to you. Ship it when it looks right." A developer connects the app once with &lt;code&gt;npx revyse init&lt;/code&gt;; after that, anyone on the team can ask for changes on the live site, in the dev server or from the dashboard. Each change gets its own branch, a pull request and a preview, and reaches production the way the project chose: promoted from the preview, straight away once the checks pass, or after named reviewers approve ("Revyse merges; your host deploys"). It supports Next.js 14 to 16 (Vite and Create React App are "experimental"), and labels changes to authentication, payments and database schemas so a reviewer looks closely. Good pick for Next.js teams that want the person who asked to ship changes, with or without a reviewer.&lt;/p&gt;

&lt;h3&gt;
  
  
  Revise (revise.build)
&lt;/h3&gt;

&lt;p&gt;A different product from Revyse. "Edit your existing website without writing code. Connect your repository, change the real interface on phone or web, and send it to your developer for review." You select an element and adjust it, or describe the change to AI, in "a separate preview" that runs in its cloud, and "Your developers decide which parts are yours to change." Choosing Send for review "creates a pull or merge request", and Revise "does not automatically publish the change." Good pick for designers and marketers who want visual edits on an existing website repo and a pull request for the developer.&lt;/p&gt;

&lt;h3&gt;
  
  
  Plusma
&lt;/h3&gt;

&lt;p&gt;"Describe a change, preview it live, iterate until it's right, and hand your team a clean PR." It connects to your GitHub repo and "Every change spins up an instant preview environment" in its cloud. Good pick for PMs and designers who want to iterate on a cloud preview and then hand engineering a PR.&lt;/p&gt;

&lt;h3&gt;
  
  
  Productmind
&lt;/h3&gt;

&lt;p&gt;"Produtyping: production-ready prototyping." You "describe the change in plain words and watch the app update" in an isolated sandbox, either in Productmind's cloud or on your own machine with its CLI, which runs your own Claude Code or Codex. Each change is saved to the session's branch; when it looks right, "the agent opens a pull request", and "Productmind never merges a pull request on its own." It works with GitHub, GitLab and Bitbucket, and sits inside a wider suite (specs, feature requests, customer feedback). If you have no engineers, a Productmind Architect, a person from its team, can review the code, billed by the hour. Good pick if you want a product-engineering suite that ends in a pull request.&lt;/p&gt;

&lt;h3&gt;
  
  
  Vixentio
&lt;/h3&gt;

&lt;p&gt;"Many agents. One team." Vixentio is "a multiplayer coding environment where a team runs AI coding agents (Claude Code, Codex and Gemini CLI) in parallel, in cloud sandboxes or on its own Macs." Reviewers sign off as Design, Product or Technical; "Technical sign-off is required whenever an agent changed code." Approving a version does not publish it: an editor chooses Publish to GitHub, and "The Vixentio GitHub App opens the pull request. Merging stays your team's decision on GitHub." Starting a task needs a Team editor seat ($39.99 a month; viewers and commenters are free). A Jira logo appears on the home page among tools it "works with"; we didn't find a Jira integration on the pages we read. Good pick if you want named sign-offs and a pull request the team merges itself.&lt;/p&gt;

&lt;h3&gt;
  
  
  Fei Studio (AutonomyAI)
&lt;/h3&gt;

&lt;p&gt;"Describe a change and it opens a merge-ready pull request in your real codebase — your engineers approve every merge." A PM describes the change in plain language, a screenshot or a Figma file; it builds it with your own components and design tokens, renders it, and opens a pull request. Since July 2026 a PM can also start a task from Claude Code, Cursor or another MCP client and check it on a link to its live sandbox. It can pull in a Jira issue by ID or URL as the instructions, and it's priced per task rather than per seat. Good pick for product teams with a design system who want PM requests to arrive as pull requests.&lt;/p&gt;

&lt;h3&gt;
  
  
  Ovren
&lt;/h3&gt;

&lt;p&gt;"Ship Coding Tasks Without Waiting on Developers." A developer installs its GitHub App once; then anyone on the team describes a change, Ovren works on "a safe copy of your project", shows "a live preview of every frontend change", and opens a pull request "into the branch your team already merges into", with a report of what it changed. You pay per change from a balance you top up. Good pick if you want occasional changes delivered as PRs without a subscription.&lt;/p&gt;

&lt;h3&gt;
  
  
  Flex
&lt;/h3&gt;

&lt;p&gt;"Give every teammate an AI software developer." A request from Slack, Linear or Flex itself becomes an isolated branch and a live preview, and engineers "review the code, control the merge, and decide what reaches production." Previews run on a self-hosted runner in infrastructure your team controls, using your own model keys. It also builds internal tools. Good pick for a team that wants previews on its own infrastructure and a pull-request flow.&lt;/p&gt;

&lt;h3&gt;
  
  
  PinAppAI
&lt;/h3&gt;

&lt;p&gt;A "visual change-request layer for AI-built sites". Reviewers drop pins on the live site, the developer's agent applies them, and reviewers approve or reject on a generated page. It's the closest to Butterneck in spirit: reviewers are free on every plan, and the developer's own agent applies the changes. Good pick if you're a solo builder collecting client feedback on a deployed site.&lt;/p&gt;

&lt;h3&gt;
  
  
  Handle Studio
&lt;/h3&gt;

&lt;p&gt;"Design directly in production code." It's free, open source, needs no account, and works with the agents designers and developers already use. The trade-off is that the person making the change installs and runs it (Studio needs macOS 13+ on Apple Silicon). Good pick for designers who are comfortable running a local repo.&lt;/p&gt;

&lt;h3&gt;
  
  
  Hexby
&lt;/h3&gt;

&lt;p&gt;"Your codebase, turned into a design canvas — powered by your AI agents." A designer or PM opens the project in Hexby's desktop app on their own computer, with a coding agent installed and signed in there, and refines the real screens on a canvas. Teammates review the before-and-after in a browser without installing Hexby, and an approved change is handed to developers as a GitHub pull request. It's free during its beta, and it uses your own agent account, since Hexby doesn't include AI usage. Good pick for designers and PMs who can run the project locally and want a visual review before the PR.&lt;/p&gt;

&lt;h3&gt;
  
  
  Figma Make (on your codebase)
&lt;/h3&gt;

&lt;p&gt;"You can use Figma Make to ship the UI changes you want directly into your team's real codebase." In a closed beta that started on 28 May 2026, a designer or PM uses the Figma Beta desktop app for Mac to open a local repository (or clone one from GitHub) and change the running app by adjusting properties, annotating elements on screen or chatting. Each prompt is saved as a local commit, and when the work is ready they open a pull request for engineering. An engineer sets up each repository once, and for now Figma says designers who already have access to the codebase are the best fit. Good pick for design teams already working in Figma who can run the project on a Mac.&lt;/p&gt;

&lt;h3&gt;
  
  
  Layrr
&lt;/h3&gt;

&lt;p&gt;"Point, click, and edit your running web app." A free, MIT-licensed proxy in front of your local dev server that uses Claude Code, Codex CLI or Gemini and "commits successful edits with a [layrr] prefix". Whoever runs it needs the repo, and its last release was in May 2026. Good pick for developers who want a free visual overlay on their own machine.&lt;/p&gt;

&lt;h3&gt;
  
  
  PulseDev
&lt;/h3&gt;

&lt;p&gt;"Point at your site. Approve the fix." Click an element on your running site, say what's wrong, and Claude Code, Codex, Gemini or OpenCode edits the source; "nothing touches your files until you approve the diff". It uses the agent plan you already pay for and "Runs on your machine, no PulseDev cloud". Like Layrr, whoever uses it runs the project locally. Pro is regularly $12 a month or $96 a year (as of 11 November 2026, when a promo code was lowering it). Good pick for a technical founder or designer who wants a visual fix loop on their own Mac.&lt;/p&gt;

&lt;h3&gt;
  
  
  medit
&lt;/h3&gt;

&lt;p&gt;"Point at your app. Say the change. Watch it ship." An overlay inside your running app: click an element, describe the change, and your own coding agent writes the code on its own branch, with a per-branch preview; with a GitHub token it opens the pull request. Like Layrr and PulseDev, someone runs it on the machine where the app runs; the overlay also opens on other devices on the same network.&lt;/p&gt;

&lt;h3&gt;
  
  
  Modeinspect
&lt;/h3&gt;

&lt;p&gt;"A design canvas with your live product, components and tokens built in", aimed at "the last 20%" after vibe coding. It runs in the cloud, so no local dev machine is needed, and every change becomes a pull request. Good pick for design engineers polishing UI.&lt;/p&gt;

&lt;h3&gt;
  
  
  Builder.io
&lt;/h3&gt;

&lt;p&gt;"Ship the changes that can't wait." A PM points Builder at a Slack thread, Jira ticket or PRD, builds a first version from the product's own components, and stakeholders comment on the live preview; the result reaches engineering as code to review and merge. Its Jira and Slack agent is on the Team plan. Good pick for a PM who wants to build the first version themselves in a visual editor.&lt;/p&gt;

&lt;h3&gt;
  
  
  Netlify Agent Runners
&lt;/h3&gt;

&lt;p&gt;"Prototypes that become the product." A PM describes the change in a prompt; the agent writes the code in the team's repository, deploys a preview and opens a pull request that developers finish and merge. Good pick for a PM who wants a shareable preview URL and is happy for the hand-off to be a PR, especially if your site already deploys on Netlify.&lt;/p&gt;

&lt;h3&gt;
  
  
  Workshop
&lt;/h3&gt;

&lt;p&gt;"Go from idea to clickable prototype in minutes." Its Desktop app can pull in your codebase, but the output is a prototype with mocked data, which engineering "can pick up where Workshop left off". Good pick for exploring an idea before committing to a real change.&lt;/p&gt;

&lt;h3&gt;
  
  
  Else
&lt;/h3&gt;

&lt;p&gt;"Preview environments with AI editing." An engineer opens a PR, Else spins up a live environment of the full stack, and PMs, QA and designers fix things in place. It works after a PR exists, so it can sit alongside tools that work before one. Good pick for teams that want richer PR review.&lt;/p&gt;

&lt;h3&gt;
  
  
  Synlets
&lt;/h3&gt;

&lt;p&gt;"Tickets in. Pull requests out." Assign a ticket and its agent writes the change and opens a PR, then iterates on review comments. Credit-based plans with no per-seat fees. Good pick if you want tickets turned straight into PRs in the cloud.&lt;/p&gt;

&lt;h3&gt;
  
  
  Inspect (Ramp)
&lt;/h3&gt;

&lt;p&gt;a cloud coding agent you give a task "from wherever you do your work: Slack, GitHub, Linear, on the web, or on the run", which returns "a visually validated and fully reviewed pull request". Sessions are shared, so teammates can add context before review. Early access only. Good pick if your team lives in Slack and wants a cloud agent that ends in a pull request.&lt;/p&gt;

&lt;h3&gt;
  
  
  Vision (vson.ai)
&lt;/h3&gt;

&lt;p&gt;teammates "build in the same room, not in silos": one shared live session with the same chat and the same preview, live cursors, and comments pinned to the preview. Every change runs in an isolated preview and arrives as a pull request an engineer reviews, and the team can set "free zones and review zones", for example an admin area anyone can change while anything touching the database needs approval. Good pick if several non-developers want to build together on one GitHub repo, with engineers reviewing pull requests.&lt;/p&gt;

&lt;h3&gt;
  
  
  Remix
&lt;/h3&gt;

&lt;p&gt;"Your AI Product Manager": the team and an AI PM work "on a working copy of your website or product: analyze your data, propose changes, prompt new variants, test them, and ship the winner." Teammates branch variants of a live copy and comment on the canvas ("Like Figma, for your live app"). When a variant is ready it goes to GitHub as a pull request with the prompts behind it, a link to run it live, and "security checks that pass before anything merges." Good pick if a product team wants to compare several variants of a screen before engineering reviews a PR.&lt;/p&gt;

&lt;h3&gt;
  
  
  Kosuke
&lt;/h3&gt;

&lt;p&gt;"Describe the change in a chat session, check it in the Preview, and press Open PR." An engineer imports and deploys the project once; after that, people who don't write code can start sessions, and engineers "review and merge the pull request as usual". Changes come back with "a prototype, a recording, a verdict" to judge. It runs your own Claude Code or Codex subscription in its cloud sandboxes and charges for sandbox hours. Good pick if you want each PR to arrive with a recorded check of the change.&lt;/p&gt;

&lt;h3&gt;
  
  
  Specship
&lt;/h3&gt;

&lt;p&gt;Ticket-to-PR automation that starts from acceptance criteria and failing tests, with an optional auto-merge for low-risk PRs in private beta. Pricing isn't published yet. Good pick for small teams that want test-first automation.&lt;/p&gt;

&lt;h3&gt;
  
  
  CoderHelm
&lt;/h3&gt;

&lt;p&gt;"Assign a GitHub issue or Jira ticket and get a pull request", plus CI fixing, PR review and alerts-to-fixes, hosted or in your own AWS account. In closed beta. Good pick for engineering teams that want an engineering-ops agent.&lt;/p&gt;

&lt;h3&gt;
  
  
  Epicraft
&lt;/h3&gt;

&lt;p&gt;"Your AI developer lives inside Jira. Create a ticket. Assign the bot. Watch it write code, push a branch, and open a PR — all from Jira comments." It "posts an implementation plan, and waits for your 👍", and says "The PM is the user, not the developer". We couldn't find a public price. Good pick if you want PMs to turn Jira tickets into PRs.&lt;/p&gt;

&lt;h3&gt;
  
  
  CodeHerder
&lt;/h3&gt;

&lt;p&gt;An engineer connects "a device and a repository" once, then product people file tasks and its agents plan, build, review and merge them, each in its own git worktree, on a machine you already have or in your AWS account. By default, "no person approves the plan, the code or the result"; teams can add approval gates or a required human approval on the git host. Plans are priced by concurrent agents, not seats. Good pick if you want agents to take a task all the way to merge on your own hardware.&lt;/p&gt;

&lt;h3&gt;
  
  
  Butterneck
&lt;/h3&gt;

&lt;p&gt;The person who asks opens a link (or labels a Jira ticket and assigns it) and chats beside a live running copy of the app while the developer's own agent makes the edit on a computer the team connects. They check the change in the preview and keep refining. Butterneck doesn't open pull requests, merge or deploy: a developer reads the conversation and the diff and decides whether it becomes a PR through the team's usual process. The agent edits the files on the connected computer, the code context it reads goes to that agent's AI provider, and the preview and the chat reach it through Butterneck's servers, so this isn't an "everything stays local" tool. Starting from a Jira ticket isn't unique to Butterneck either: Synlets, CoderHelm, Clogless and Epicraft (which is also built for PMs) start from tickets too, and CodeHerder also runs agents on a machine the team connects; Productmind's CLI can run its sessions on your own machine. Since 28 October 2026, GitHub's own &lt;a href="https://github.blog/changelog/2026-10-28-new-tools-triggers-and-cost-controls-for-copilot-automations" rel="noopener noreferrer"&gt;Copilot Automations&lt;/a&gt; can also start when an issue is labeled or assigned. The difference is what comes back: a live preview on the developer's own running app, and no pull request until a developer decides. The person asking doesn't install anything or need the project on their own computer: the developer's connected computer runs the app and the agent, and the requester only needs the link. Not the right pick if you want a tool that creates the PR for you; several above do that well. To see the flow before connecting a computer, &lt;a href="https://app.butterneck.com/trial" rel="noopener noreferrer"&gt;create a free account and try a request on a sample shop&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to choose
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;You want a prototype to explore an idea:&lt;/strong&gt; Workshop, Modeinspect.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You want a ticket turned into a pull request automatically:&lt;/strong&gt; Synlets, Specship, CoderHelm, CodeHerder (Jira's built-in options are worth a look too).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You want a ticket in Jira turned into a PR, with the PM as the user:&lt;/strong&gt; Epicraft, Synlets, CoderHelm.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You want a cloud preview you iterate on, then a PR:&lt;/strong&gt; Plusma, Revyse (cloud), Revise, ronda, Ovren, Flex, Vision (a hosted "isolated environment" for each change), Remix (variants of "a live copy of your real app"), Lightsprint, Sparkles, Alloy, Builder.io, Netlify Agent Runners, Kosuke, Productmind, Vixentio.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You want a PR from a plain-English request:&lt;/strong&gt; ronda, Fixdog, Itera, Clogless.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You want the requester to publish small changes themselves:&lt;/strong&gt; Refinar, Revyse.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You want better review once a PR exists:&lt;/strong&gt; Else.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You're a designer or developer who'll run the tool yourself, with your own coding agent:&lt;/strong&gt; Handle Studio, Hexby, Layrr, PulseDev, Modeinspect, medit.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You're a designer already working in Figma, on a Mac, with access to the repo:&lt;/strong&gt; Figma Make (closed beta).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You want the person who asked to check the change before any PR exists, without installing anything:&lt;/strong&gt; PinAppAI, Butterneck.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Check dates: prices and quotes were re-read on each tool's own pages on 29 October 2026, except Itera (see the note under the table). Hexby, Figma Make, Inspect, Vision, Remix, Lightsprint, Sparkles, Alloy and medit were checked on 30 October 2026; Builder.io, Netlify Agent Runners, Kosuke and PulseDev on 31 October 2026, and Netlify Agent Runners' pricing and agent list again on 19 November 2026; Revise on 6 November 2026; Productmind on 7 November 2026. PulseDev and ronda were checked again on 9 November 2026, and PulseDev, ronda, Productmind, Revyse and Vixentio were re-read on 11 November 2026. Prices and features change. Tell us if something here is out of date and we'll fix it.&lt;/p&gt;

&lt;p&gt;For a product manager who wants to try Claude Code without setting up the repo, see &lt;a href="https://www.butterneck.com/blog/claude-code-for-product-managers" rel="noopener noreferrer"&gt;Claude Code for product managers&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Is there an AI coding agent for people who don't code?
&lt;/h3&gt;

&lt;p&gt;Yes, several. Most of the tools above let a PM, designer or operator describe a change in plain language and have a coding agent make it in the team's real codebase. They differ in what comes back: a prototype (Workshop), a pull request (ronda, Fixdog, Itera as of 28 Oct, Clogless, Synlets, Ovren, Flex, Productmind, Vixentio), a merged change (CodeHerder, when no approval gate is on; Revyse, when the project's release setting allows it), or a live preview the person who asked checks before a developer decides (Butterneck, PinAppAI).&lt;/p&gt;

&lt;h3&gt;
  
  
  Can a non-developer change an existing app without breaking it?
&lt;/h3&gt;

&lt;p&gt;Keep a developer in the decision. Look for three things: the change is shown on a preview before anything ships, a developer reviews it, and risky areas like login, billing and data stay with engineering. Our &lt;a href="https://www.butterneck.com/blog/ai-change-request-policy-template" rel="noopener noreferrer"&gt;AI change request policy template&lt;/a&gt; lists what to fence off. On the Git side, protect the main branch so changes only land through a reviewed pull request; &lt;a href="https://www.butterneck.com/blog/how-non-engineers-can-ship-frontend-changes-as-pull-requests" rel="noopener noreferrer"&gt;how to let non-engineers ship frontend changes as pull requests&lt;/a&gt; covers branch rules and CODEOWNERS. For the whole process, from asking on a live preview to who decides what ships, see our guide to &lt;a href="https://www.butterneck.com/blog/ai-change-requests-for-product-teams" rel="noopener noreferrer"&gt;AI change requests for product teams&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I change my existing web app with AI without a developer?
&lt;/h3&gt;

&lt;p&gt;On your own computer, yes, if you can run the project yourself: tools like Layrr and PulseDev put a point-and-edit overlay on your local dev server, and a coding agent such as Claude Code edits the source. If the app belongs to a team, someone still decides what ships. Tools like ronda and Revyse (in its cloud mode) turn your request into a pull request for the team to review. In Butterneck you don't need the project on your computer: you ask on a live copy of the app, the developer's own agent makes the change on a computer the team connects, and a developer decides what goes live. Butterneck never opens a pull request, merges or deploys.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is there a Figma Make alternative for PMs who aren't on a Mac or can't get into the beta?
&lt;/h3&gt;

&lt;p&gt;Figma Make on your codebase is a closed beta for now: access is by waitlist, it runs in the Figma Beta desktop app for Mac (Figma says Windows support is planned), and the person using it needs access to the repository (as of 30 October 2026, per &lt;a href="https://help.figma.com/hc/en-us/articles/40789739982871-Make-in-your-local-codebase-Setup-gotchas-and-troubleshooting" rel="noopener noreferrer"&gt;Figma's help article&lt;/a&gt;). ronda builds the change in an isolated live sandbox and opens a pull request; Refinar builds it on a copy of the live app, and the requester publishes it or sends it to engineering. With Butterneck, the person asking opens a link in a browser, with no repository, desktop app or Mac on their side: a developer connects a computer that already has the project, the coding assistant already signed in there makes the change, and the person asking checks it on the live preview. Butterneck does not commit, push or open a pull request; a developer decides what ships.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which of these tools let engineers review and approve a change before it merges?
&lt;/h3&gt;

&lt;p&gt;The "What you get back" column shows what each tool hands over for review: a prototype, a pull request or a live preview. Whether a merge can skip review depends on each tool's settings and your repository rules, so check its own page. Butterneck itself doesn't commit anything: the person who asked checks the change on a live preview, then a developer reviews the diff in their own tools and decides whether to commit it, open a pull request and merge.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which tools on this list are alternatives to each other?
&lt;/h3&gt;

&lt;p&gt;Tools on the same line of "How to choose" above do the same job, so they are the closest alternatives to each other. If you are looking at ronda, the other tools that turn a plain-English request into a pull request are Fixdog, Itera and Clogless. If you like that Revyse can let the person who asked publish small changes, Refinar does that too. For a prototype to explore an idea, as with Modeinspect, look at Workshop. If you'd rather the person who asked check the change before any pull request exists, PinAppAI and Butterneck work that way.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does Butterneck open a pull request?
&lt;/h3&gt;

&lt;p&gt;No. Butterneck never opens a pull request, merges or deploys. The person who asked checks the change on a live preview, and a developer reviews the diff and ships it the team's usual way.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>devtools</category>
      <category>productmanagement</category>
      <category>webdev</category>
    </item>
    <item>
      <title>AI change requests: Claude Code for product managers, no terminal</title>
      <dc:creator>Butterneck</dc:creator>
      <pubDate>Wed, 04 Nov 2026 05:45:24 +0000</pubDate>
      <link>https://dev.to/butterneck/claude-code-for-product-managers-use-your-teams-claude-code-or-cursor-without-a-terminal-3h5a</link>
      <guid>https://dev.to/butterneck/claude-code-for-product-managers-use-your-teams-claude-code-or-cursor-without-a-terminal-3h5a</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.butterneck.com/blog/claude-code-for-product-managers" rel="noopener noreferrer"&gt;butterneck.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Search for "Claude Code for product managers" or "Cursor for PMs" and most guides give similar advice: get Claude Code or Cursor (Claude Code now also runs in a desktop app and on the web at claude.ai/code, so a terminal is optional), connect the repo, learn enough git, and open pull requests yourself. For some product managers that is the right move. For many product teams it is not, and there is another way to get the same coding assistant working on a PM's request. This guide covers both: when a product manager should run Claude Code themselves, and when it is simpler to ask for the change on a live preview and let a developer's Claude Code do the edit.&lt;/p&gt;

&lt;p&gt;This post covers both. We make Butterneck, which takes the second route, so we are not neutral. We have tried to be clear about when a PM should just run Claude Code themselves.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Claude Code for product managers, in short:&lt;/strong&gt; A PM can run Claude Code or Cursor themselves, which means repo access, a paid AI seat, usually a local setup, and opening pull requests. The other way: the PM asks in plain words on a live preview, and the Claude Code, Cursor or Antigravity CLI already signed in on the developer's computer makes the change. Butterneck does not commit, push or open a pull request; a developer decides first what ships, and Butterneck never merges or deploys.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  The usual advice: give the PM their own coding assistant
&lt;/h2&gt;

&lt;p&gt;The typical guide goes like this. The PM gets access to the repository, sets up Claude Code (in a terminal, an IDE, the desktop app or the web) or Cursor, runs the project, asks the assistant for a change, and then commits it and opens a pull request for a developer to review.&lt;/p&gt;

&lt;p&gt;That works. The desktop app and the web version remove the terminal, but not the rest: the assistant still edits a copy of the code, and while the desktop app can start the dev server and show the app in its Browser pane, a local session still needs the project set up on the PM's own computer to run. With a local setup, the PM also owns the development environment: dependencies, environment variables, a dev server, branches, merge conflicts. The developer still reviews the change, but now reviews a pull request from someone who may not be able to answer questions about the diff. We looked at that trade-off in more depth in &lt;a href="https://www.butterneck.com/blog/should-product-managers-ship-code" rel="noopener noreferrer"&gt;should product managers ship code?&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Cursor's own &lt;a href="https://cursor.com/for/product-managers" rel="noopener noreferrer"&gt;page for product managers&lt;/a&gt; describes this path well: PMs prototype features and ship small changes directly, starting with Cloud Agents. It works when the PM wants to drive the agent themselves. If the PM would rather ask in plain words on the running app and leave the agent, the diff and the release to a developer, that is the other way below. With Butterneck the developer's own Cursor (or Claude Code, or Antigravity) does the edit on a developer's connected computer.&lt;/p&gt;

&lt;h2&gt;
  
  
  The other way: an AI coding agent for product managers that runs on the developer's computer
&lt;/h2&gt;

&lt;p&gt;Your team probably already has a coding assistant signed in on a developer's computer. Butterneck lets the rest of the product team use it, without a terminal and without a copy of the repo.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A developer connects a computer that already has the project and a coding CLI signed in: Claude Code (&lt;code&gt;claude&lt;/code&gt;), Cursor's CLI (&lt;code&gt;agent&lt;/code&gt;), or Antigravity (&lt;code&gt;agy&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;The app runs on that computer's dev server, and Butterneck gives it a share link. Preview traffic is relayed through Butterneck, so nobody needs a VPN, a deploy, or localhost access.&lt;/li&gt;
&lt;li&gt;The PM opens the link, sees the running app, and types the request into a chat next to the screen they mean. Or someone adds the label &lt;code&gt;butterneck&lt;/code&gt; to a Jira ticket and assigns it. See the &lt;a href="https://www.butterneck.com/integrations/jira" rel="noopener noreferrer"&gt;Jira integration&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;The CLI on the developer's computer edits the connected project. The preview updates on the same link.&lt;/li&gt;
&lt;li&gt;A developer reads the conversation, checks the change, and publishes it the way the team already does. Or throws it away.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Butterneck never opens a pull request, never merges, and never deploys. A developer decides what goes live.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;A developer installs the Butterneck connector on a computer with Node.js 22 or newer, a signed-in coding CLI, and the project folder.&lt;/li&gt;
&lt;li&gt;They point it at the project and start the app. Butterneck creates a live preview with a share link.&lt;/li&gt;
&lt;li&gt;They choose who can send requests: a list of people, or anyone with the link. People who only look need no account.&lt;/li&gt;
&lt;li&gt;The PM opens the link and asks for the change in plain words, on the page it is about.&lt;/li&gt;
&lt;li&gt;The coding CLI makes the edit in that folder, and the PM checks it on the preview. If it is wrong, the turn can be stopped and its file changes are usually rolled back (if not, the chat says so).&lt;/li&gt;
&lt;li&gt;A developer reviews the result and ships it through the normal process: commit, pull request, CI, deploy.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  PM runs Claude Code or Cursor vs PM asks on a preview
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;PM runs Claude Code or Cursor&lt;/th&gt;
&lt;th&gt;PM asks on a Butterneck preview&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;What the PM needs&lt;/td&gt;
&lt;td&gt;Repo access, a paid AI seat, and usually a local setup (the desktop app or claude.ai/code removes the terminal, not the repo)&lt;/td&gt;
&lt;td&gt;A browser and the share link&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Whose AI subscription&lt;/td&gt;
&lt;td&gt;A seat for the PM&lt;/td&gt;
&lt;td&gt;The CLI signed in on the connected computer (under its plan's terms)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Where the change is checked&lt;/td&gt;
&lt;td&gt;The PM's own local app&lt;/td&gt;
&lt;td&gt;A live preview of the developer's running dev server&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;What comes out&lt;/td&gt;
&lt;td&gt;A pull request from the PM&lt;/td&gt;
&lt;td&gt;Edited files on the developer's computer; the developer opens the PR&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who decides what ships&lt;/td&gt;
&lt;td&gt;A developer reviewing the PR&lt;/td&gt;
&lt;td&gt;A developer reviewing the change and the conversation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Good for&lt;/td&gt;
&lt;td&gt;PMs who want to build and own changes&lt;/td&gt;
&lt;td&gt;Small changes on a product that already runs&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  When PMs should just use Claude Code themselves
&lt;/h2&gt;

&lt;p&gt;Be honest about your team. Giving the PM their own coding assistant is often the better call when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The PM is comfortable with git and a coding assistant (terminal, desktop app or web), and wants to learn the codebase.&lt;/li&gt;
&lt;li&gt;They are prototyping something new, not changing a live product.&lt;/li&gt;
&lt;li&gt;The work is in a separate repo, a script, or an internal tool that no developer needs to approve.&lt;/li&gt;
&lt;li&gt;Your team already has a review process for PM-authored pull requests, and it works.&lt;/li&gt;
&lt;li&gt;No developer computer can stay on to run the project and the preview.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In those cases, a PM with their own Claude Code or Cursor seat is simpler than routing requests through someone else's setup.&lt;/p&gt;

&lt;p&gt;It works best when engineering treats the PM's setup as a product of its own. Needl.ai, for example, describes PMs working in its production codebase with Claude Code, using reusable skills its engineers built to enforce authentication, the design system and deployment (&lt;a href="https://vikramsrinivasan.substack.com/p/the-repo-is-the-new-prd" rel="noopener noreferrer"&gt;The Repo Is the New PRD&lt;/a&gt;, April 2026).&lt;/p&gt;

&lt;h2&gt;
  
  
  What to know before you try this
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Your AI provider's terms apply.&lt;/strong&gt; The coding CLI sends code context to its own provider, under that provider's terms. Butterneck does not run its own model.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Not everything stays on the computer.&lt;/strong&gt; Files are edited on the connected computer, but chat messages and preview traffic go through Butterneck.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;.env&lt;/code&gt; is a guardrail, not a hard block.&lt;/strong&gt; Secret settings files are on an ignore list the AI is told to stay out of. That is an instruction, so keep production secrets off that computer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The AI stays in the folder you connected,&lt;/strong&gt; and you can add ignore rules for paths it should not touch.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The computer has to be on&lt;/strong&gt; for the preview to load and for work to start.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If your team needs written rules for who can ask the AI for what, start from our &lt;a href="https://www.butterneck.com/blog/ai-change-request-policy-template" rel="noopener noreferrer"&gt;AI change request policy template&lt;/a&gt;. For why we keep a developer at the last step, read &lt;a href="https://www.butterneck.com/blog/human-in-the-loop-ai-coding" rel="noopener noreferrer"&gt;human-in-the-loop AI coding&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it costs
&lt;/h2&gt;

&lt;p&gt;Starter is free for one developer and one person who asks for changes. Pro is USD 19 per person per month, billed monthly, with 20% off annual billing. Developers and people who request changes both count as seats; people who only open a share link to look do not. You keep paying for your own coding assistant subscription, on a plan that allows use on your team's behalf (see the note on plans and terms below). A workspace owner on Starter can also start a one-month Pro trial from the Billing page, once per workspace. Details on &lt;a href="https://www.butterneck.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Can product managers use Claude Code without a terminal?
&lt;/h3&gt;

&lt;p&gt;Yes. Claude Code also runs in Anthropic's desktop app and in the browser at claude.ai/code, so a PM doesn't strictly need a terminal. They still need a paid Claude plan, access to the repository, and usually a way to run the app to check the change. With Butterneck the PM needs none of those: they type the request in a chat on a live preview, and Claude Code runs on a developer's computer where it is already signed in.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does a product manager need repository access to use Claude Code or Cursor?
&lt;/h3&gt;

&lt;p&gt;To run it themselves, yes. Claude Code and Cursor work on code the PM can reach: a local clone, or, for Cursor's Cloud Agents, only repositories the PM's own Git account can already reach (&lt;a href="https://cursor.com/docs/cloud-agent/security" rel="noopener noreferrer"&gt;Cursor's security docs&lt;/a&gt;). With Butterneck the PM doesn't need repository access. They open a share link to the app running on a developer's computer and type the request, and the Claude Code, Cursor or Antigravity CLI signed in there edits the project. The developer chooses who can send requests, and a developer decides what ships.&lt;/p&gt;

&lt;h3&gt;
  
  
  What does "Cursor for product managers" mean if the PM has no repo access?
&lt;/h3&gt;

&lt;p&gt;Cursor's own &lt;a href="https://cursor.com/for-product-managers" rel="noopener noreferrer"&gt;page for product managers&lt;/a&gt; describes PMs prototyping and shipping small changes themselves, starting with Cloud Agents. Those agents connect to the PM's repositories, and you can ask questions and kick off tasks from Slack. If the PM has no repository access or Cursor seat, the other path is to ask on a Butterneck live preview: Cursor's CLI (&lt;code&gt;agent&lt;/code&gt;), signed in on the developer's connected computer, makes the edit, the PM checks the preview, and a developer decides what ships.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can't a developer just share their Claude Code session with the PM instead?
&lt;/h3&gt;

&lt;p&gt;They can, and for pairing with another developer that often works well. A shared session shows the other person the agent's chat, commands and diffs, and the host usually approves what runs. Butterneck is built for the person who doesn't read those: the PM opens a share link to the running app, types the change in a chat next to the screen they mean, and checks the result on that same preview. They never see a terminal or the code. The developer chooses who can send requests on each copy, either chosen people or anyone with the link. Requests don't stop for a prompt on every tool call: the coding CLI runs with its interactive permission prompts skipped, and the workspace is snapshotted before each turn so a stopped turn can usually be rolled back. Butterneck does not commit, push, open a pull request, merge or deploy, so a developer still reviews and publishes the change the usual way.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does each PM need their own Claude Code or Cursor subscription?
&lt;/h3&gt;

&lt;p&gt;They don't run or sign in to a coding tool themselves. Requests from the live preview run on the coding CLI already signed in on the developer's connected computer (Claude Code, Cursor's agent CLI, or Antigravity), so check that its plan allows use on your team's behalf; whether that means extra seats with your AI vendor depends on its terms (see the note below). On Pro, each person who sends requests counts as a seat; Starter includes one developer and one requester for free.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A note on plans and terms.&lt;/strong&gt; Butterneck runs requests through the AI coding tool your developer is already signed into, so that tool's terms apply. The signed-in plan must allow use on your team's behalf. Personal and consumer plans (Claude Pro or Max, Cursor's individual plans, personal Google AI plans) may not. Anthropic's consumer terms, for example, say you "may not make your Account available to anyone else," and Claude Code's docs say Pro and Max limits "assume ordinary, individual usage." Team, Business or Enterprise plans, where each person has a seat, or an organization API key (Anthropic Console, Gemini API / Vertex AI) are the safer fit. Check your plan's terms or ask your vendor. This is not legal advice.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does Butterneck open pull requests for the PM's change?
&lt;/h3&gt;

&lt;p&gt;No. It edits files in the connected project and stops. A developer decides whether to commit it, open a pull request, or discard it. Butterneck never merges and never deploys.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can product managers use Google Antigravity this way?
&lt;/h3&gt;

&lt;p&gt;Yes. Google's &lt;a href="https://antigravity.google/use-cases/product-management/" rel="noopener noreferrer"&gt;Antigravity for product management&lt;/a&gt; page covers a PM running Antigravity themselves, for example to draft PRDs grounded in the codebase or put together prototypes. With Butterneck the PM doesn't open Antigravity at all: a developer connects a computer that has the project and the Antigravity CLI (&lt;code&gt;agy&lt;/code&gt;) signed in, the PM types the change in a chat on a live preview of the existing app, and Antigravity makes the edit on that computer. The plan note above applies to Antigravity too. Butterneck does not commit, push or open a pull request, and a developer decides what ships.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is there an AI coding agent for product managers that works on our existing codebase?
&lt;/h3&gt;

&lt;p&gt;Yes. Butterneck is one option for a team that already has a web app. A developer connects a computer that already runs the product and has Claude Code, Cursor or Antigravity signed in. The product manager opens a live preview of the existing app, types the change in a chat, and checks the result on that preview. The agent edits the real project on the developer's computer. Butterneck does not commit, push or open a pull request: a developer decides first what ships, and Butterneck never merges or deploys. Tools such as Alloy, Clogless and Plusma instead connect your GitHub repository, run the change in a hosted preview and open a pull request. A third kind is a desktop app the PM installs, which runs the product and a coding agent on the PM's own laptop and usually needs tools such as git, Docker or Claude Code set up there first. With Butterneck the PM installs nothing; the app and the agent run on the developer's connected computer.&lt;/p&gt;

&lt;h3&gt;
  
  
  Where are files edited, and what leaves the computer?
&lt;/h3&gt;

&lt;p&gt;The files are edited on the connected computer. But the coding CLI sends code context to its AI provider under that provider's terms, and chat and preview traffic are relayed through Butterneck.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is there a free plan?
&lt;/h3&gt;

&lt;p&gt;Yes. Starter is free for one developer and one person who asks for changes.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can designers use Claude Code this way too?
&lt;/h3&gt;

&lt;p&gt;Yes. A designer can type a copy, spacing, color or layout change in the chat on the live preview and check it on the screen they mean, without setting up Claude Code or the repository. Claude Code still runs on the developer's connected computer, and the developer still decides what ships. Anyone who sends requests counts as a seat on Pro; people who only open the share link to look don't. More in &lt;a href="https://www.butterneck.com/blog/how-non-engineers-can-ship-frontend-changes-as-pull-requests" rel="noopener noreferrer"&gt;how designers and PMs can ship frontend changes&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does this work with OpenAI Codex?
&lt;/h3&gt;

&lt;p&gt;Not today. The connector runs Claude Code (&lt;code&gt;claude&lt;/code&gt;), Cursor's CLI (&lt;code&gt;agent&lt;/code&gt;) or Antigravity (&lt;code&gt;agy&lt;/code&gt;), signed in on the developer's connected computer. If your team only uses Codex, Butterneck isn't a fit for now.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;If your PMs keep asking for small changes that sit in the backlog, &lt;a href="https://calendar.app.google/p2McAaz4ZwXBiG5m9" rel="noopener noreferrer"&gt;book a 30-minute demo&lt;/a&gt; and we will run a real request on a live copy. Or see &lt;a href="https://www.butterneck.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt; and start on the free plan.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productmanagement</category>
      <category>productivity</category>
      <category>webdev</category>
    </item>
    <item>
      <title>AI change requests: share local app without deploying</title>
      <dc:creator>Butterneck</dc:creator>
      <pubDate>Wed, 04 Nov 2026 05:44:50 +0000</pubDate>
      <link>https://dev.to/butterneck/share-your-local-app-with-stakeholders-without-deploying-it-5ec8</link>
      <guid>https://dev.to/butterneck/share-your-local-app-with-stakeholders-without-deploying-it-5ec8</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.butterneck.com/blog/share-local-app-without-deploying" rel="noopener noreferrer"&gt;butterneck.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;You changed the pricing page. It runs on your computer at &lt;code&gt;localhost:3000&lt;/code&gt;. The product manager wants to see it before it goes anywhere. What happens next usually takes longer than the change did.&lt;/p&gt;

&lt;p&gt;This post is about that gap: getting a running local app in front of the people who asked for it, and getting their feedback back to the project, without deploying first.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Sharing a local app without deploying, in short:&lt;/strong&gt; With Butterneck, a bridge on the developer's computer starts the app and gives it a public share link, so a PM or stakeholder opens the real running app with no staging deploy, VPN or screen share, and no account just to look. They ask for changes in a chat on that preview, the coding assistant already signed in on the developer's computer edits the project, and hot reload shows the result. Chat messages and preview traffic go through Butterneck's server, and the coding CLI sends code context to its AI provider. Butterneck does not commit, push or open a pull request; a developer decides first what ships.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Why "just deploy it to staging" is slow
&lt;/h2&gt;

&lt;p&gt;Staging works. It is also a lot of steps for "can you look at this button".&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You commit work that is not finished, or you make a branch only so it can be deployed.&lt;/li&gt;
&lt;li&gt;You wait for a build and a deploy.&lt;/li&gt;
&lt;li&gt;Staging often has different data, different settings, or someone else's half-done change on it.&lt;/li&gt;
&lt;li&gt;The reviewer finds one more thing. You change it locally and deploy again.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each round is minutes at best. Often it is hours, because the reviewer is in a meeting when the deploy finishes. The change is small. The waiting is not.&lt;/p&gt;

&lt;h2&gt;
  
  
  The usual workarounds, and where they fall short
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Screenshots and screen recordings
&lt;/h3&gt;

&lt;p&gt;Fast to send. But a screenshot can't be clicked. The reviewer can't try the form, resize the window, or check the page next to it. Questions come back as more screenshots with red circles.&lt;/p&gt;

&lt;h3&gt;
  
  
  Screen sharing on a call
&lt;/h3&gt;

&lt;p&gt;Good for a walkthrough. Bad for "I'll look later". Everyone has to be free at the same time, and the reviewer is watching, not using.&lt;/p&gt;

&lt;h3&gt;
  
  
  Tunnels
&lt;/h3&gt;

&lt;p&gt;A tunnel gives your local port a public address. That solves the "can they open it" part. It does not solve who is allowed to open it, where the feedback goes, or what happens after someone says "make the heading shorter". You still collect the request in Slack, find the right file, and change it yourself.&lt;/p&gt;

&lt;p&gt;Some newer share-localhost tools add a feedback layer on top: pinned comments on the page, or a voice note turned into a transcript you can hand to your coding agent. That gets the request to you faster. Someone still has to read it, find the file and make the change.&lt;/p&gt;

&lt;h3&gt;
  
  
  Preview deploys per branch
&lt;/h3&gt;

&lt;p&gt;Very good when you already have them. They still need a push and a build, and they still split the conversation: the preview is in one place, the comments are in another. We compare the two orders in &lt;a href="https://www.butterneck.com/blog/live-preview-before-pull-request" rel="noopener noreferrer"&gt;live preview before the PR&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a stakeholder actually needs
&lt;/h2&gt;

&lt;p&gt;When a product manager or a support lead reviews a change, they need four things:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;A link that opens the real app.&lt;/strong&gt; Not a picture. The app, running, with its pages and forms.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No setup.&lt;/strong&gt; No VPN, no account just to look, no "install this first".&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A place to say what they want next to the thing they mean.&lt;/strong&gt; Not a separate thread.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A clear answer on what happens to their request.&lt;/strong&gt; Who makes the change, and who decides it goes live.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The fourth one is the part most tools skip.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Butterneck shares a local app
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://dev.to/"&gt;Butterneck&lt;/a&gt; is built around one idea: people on the product team ask for changes on a live copy of the product, and a developer decides what goes live. Sharing the running app is the first half of that.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fiivgift77a5chi6zqx1c.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fiivgift77a5chi6zqx1c.png" title="1280x720" alt="The Butterneck workspace, where a developer sees each copy of the project and its share link" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Connect the computer that already has the project
&lt;/h3&gt;

&lt;p&gt;A developer creates a workspace and installs a small connector, called the bridge, on a computer that already has the project. That computer needs Node.js 22 or newer and a coding assistant that is already signed in: Cursor, Claude Code, or Antigravity (team, enterprise or API plans recommended). The bridge is paired to the workspace with a code from the admin screen.&lt;/p&gt;

&lt;p&gt;You point it at the project folder. It can start the app for you and find the port it runs on.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Every running app gets a share link
&lt;/h3&gt;

&lt;p&gt;Once the app is running, it gets a public link. Anyone you send it to opens the real app, served from your computer. No deploy, no VPN, and nobody has to know what &lt;code&gt;localhost&lt;/code&gt; means.&lt;/p&gt;

&lt;p&gt;Some details matter more than they sound:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Hot reload keeps working.&lt;/strong&gt; The preview passes through the dev server's live-reload connection, so when a file changes, the person looking sees it update.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Streaming responses and file downloads work.&lt;/strong&gt; Event streams pass through, and so do binary files such as office documents.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Looking does not need an account.&lt;/strong&gt; Someone can open the preview without signing up.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  3. You choose who can ask
&lt;/h3&gt;

&lt;p&gt;Opening the preview and asking for a change are two different things. You decide whose messages start the AI: a list of people, or anyone with the link. If the link is closed, a visitor can ask for access, and you allow it or decline it.&lt;/p&gt;

&lt;p&gt;A reply from a developer in the same chat does not trigger the AI. So you can answer a question without changing any files.&lt;/p&gt;

&lt;h2&gt;
  
  
  The feedback stays on the app
&lt;/h2&gt;

&lt;p&gt;This is where sharing a local app becomes more than a tunnel. The Butterneck preview has a chat built in. The product manager types the change on the page they are looking at:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Make the button say "Book a call".&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The coding assistant on the developer's computer reads the request and edits the project. Because hot reload is on, the change shows up in the same preview. The request, any screenshots, and the replies stay together on that live copy.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Feh10nopyv289kzt99n4z.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Feh10nopyv289kzt99n4z.gif" title="1280x720" alt="A request typed in the chat, and the app in the preview updating after the AI edits the project" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If your requests start in Jira instead, add the label &lt;code&gt;butterneck&lt;/code&gt; to a ticket and assign it to a teammate whose Jira account is mapped to a computer that has the project. Butterneck opens its own copy named after the ticket, and the title, description, latest comments, and attached files become the request. When the AI is done, a short note and a link to the preview go back on the ticket. Setup, including how each developer's Jira account is mapped to their computer, is on the &lt;a href="https://www.butterneck.com/integrations/jira" rel="noopener noreferrer"&gt;Jira integration page&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is edited on a developer's connected computer, and what leaves it
&lt;/h2&gt;

&lt;p&gt;Sharing a local app is only comfortable if you know what the outside world can touch. With Butterneck:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The AI edits only the folder you connected. You can block other paths with ignore rules.&lt;/li&gt;
&lt;li&gt;Secret settings files (&lt;code&gt;.env&lt;/code&gt;) are on the agent's ignore list (an instruction, not a hard block).&lt;/li&gt;
&lt;li&gt;If a turn goes wrong, you can stop it, and that turn's file changes are usually rolled back; if the rollback can't be completed, the chat says so.&lt;/li&gt;
&lt;li&gt;Chat messages and preview traffic go through Butterneck's server, and the coding CLI sends code context to its AI provider, as it does in normal use.&lt;/li&gt;
&lt;li&gt;Butterneck does not commit, push, open a pull request, merge or deploy. The change is not published until someone on your team publishes it the way you already do.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last point is the whole design. We wrote more about it in &lt;a href="https://www.butterneck.com/blog/human-in-the-loop-ai-coding" rel="noopener noreferrer"&gt;Human-in-the-loop AI coding: why Butterneck never merges&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;For how the whole flow fits together, layer by layer, read &lt;a href="https://www.butterneck.com/blog/human-in-the-loop-architecture-for-ai-product-changes" rel="noopener noreferrer"&gt;Ask freely, ship deliberately: an architecture for human-in-the-loop AI product changes&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  When sharing a local app is the right call
&lt;/h2&gt;

&lt;p&gt;It fits well when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The change is small and visual: copy, layout, a form field, a colour.&lt;/li&gt;
&lt;li&gt;The reviewer is not a developer and will not clone the project.&lt;/li&gt;
&lt;li&gt;You want feedback on the real thing, with real behaviour, before anything ships.&lt;/li&gt;
&lt;li&gt;Requests arrive as Jira tickets full of comments and files, and someone has to carry them to the project.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It is not the right tool when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You need a long-lived environment for load tests or QA sign-off. Use staging for that.&lt;/li&gt;
&lt;li&gt;Your team wants the AI to open pull requests or merge on its own. Butterneck does not do that.&lt;/li&gt;
&lt;li&gt;There is no local project folder at all, for example a team that works only in a cloud IDE.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A short checklist before you send the link
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Start the app through the bridge and open the share link yourself first.&lt;/li&gt;
&lt;li&gt;Decide who can ask: a named list, or anyone with the link.&lt;/li&gt;
&lt;li&gt;Check that the pages you want reviewed use test data, not real customer data.&lt;/li&gt;
&lt;li&gt;Send the link with one sentence on what to look at.&lt;/li&gt;
&lt;li&gt;When the change looks right, publish it the way you always do.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Can I share a local app with stakeholders without deploying it?
&lt;/h3&gt;

&lt;p&gt;Yes. With Butterneck, the bridge on your computer starts the app and it gets a public share link. Requests to that link are relayed to the app on your computer, so there is no staging deploy, VPN or screen share, and hot reload keeps working.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do stakeholders need an account to view the preview?
&lt;/h3&gt;

&lt;p&gt;No. Looking does not need an account. You decide separately who can ask for changes: a list of people, or anyone with the link. If the link is closed, a visitor can ask for access.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does preview traffic go through Butterneck?
&lt;/h3&gt;

&lt;p&gt;Yes. Chat messages and preview traffic go through Butterneck's server, and the coding CLI sends code context to its AI provider, as it does in normal use. Butterneck does not commit, push, open a pull request, merge or deploy; nothing ships until someone on your team publishes the change the way you already do.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do we need a staging environment for every change so a PM can review it?
&lt;/h3&gt;

&lt;p&gt;Not for small changes. With Butterneck, the person who asked reviews the change on a share link to the app already running on a developer's connected computer, where the coding agent signed in there (Cursor, Claude Code or Antigravity) made the edit. Nothing has to be pushed first, and no CI pipeline, build or deploy runs before they can look; hot reload shows each edit on the same link. The trade-off is that the connected computer has to be on for the preview to load. For QA sign-off, load tests or anything that needs a production-like build, keep using your branch preview or staging environment. Butterneck does not commit, push, open a pull request, merge or deploy; a developer decides what ships.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I share a native mobile app this way?
&lt;/h3&gt;

&lt;p&gt;Not a native iOS or Android build. Butterneck shares web apps: the bridge starts the project's app on the connected computer, finds the port it runs on, and the share link opens it in a browser. A native app doesn't run behind a web link, so there is nothing for a stakeholder to open. If your product is a web app, the person who asked can still check the phone layout by narrowing the browser window to phone width. Butterneck does not commit, push, open a pull request, merge or deploy.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does it work with our stack, for example Rails, Django or Laravel?
&lt;/h3&gt;

&lt;p&gt;Butterneck doesn't depend on a particular framework or language. It works with a web app that the connected computer can start with a command and that serves pages on a local port. Each app in the project has its own start command and port, which the developer sets up once (detection can fill them in from the project's files), and the share link opens that app in a browser. If your dev server reloads the page when a file changes, that keeps working on the share link. The bridge itself needs Node.js 22 or newer on that computer, whatever your app is written in. Butterneck does not commit, push, open a pull request, merge or deploy.&lt;/p&gt;

&lt;h3&gt;
  
  
  What if our app needs Docker Compose or a local database?
&lt;/h3&gt;

&lt;p&gt;That works, as long as the app runs on the connected computer. When the developer sets up the project, Butterneck reads its files, including a Docker Compose file, and lists what the computer needs, such as Docker Compose services running or a database to create. The developer confirms that list once. Each copy then follows its setup steps, which can include starting the database services from the compose file, for example &lt;code&gt;docker compose up db -d&lt;/code&gt;, before the app starts. The app itself still needs a start command and a local port, which is what the share link opens. Use local or test data for previews, not production data. Butterneck does not commit, push, open a pull request, merge or deploy.&lt;/p&gt;

&lt;h3&gt;
  
  
  How is this different from a localhost tunnel like ngrok?
&lt;/h3&gt;

&lt;p&gt;A tunnel gives your local port a public address, and some add a login or comments on top. Butterneck also starts the app through the bridge, puts a chat on the preview, and lets you choose who can ask for changes. The coding assistant already signed in on a developer's connected computer makes the change, and hot reload shows it on the same link. Butterneck does not commit, push, open a pull request, merge or deploy.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can a product manager comment on my local dev server and have the AI make the change?
&lt;/h3&gt;

&lt;p&gt;Yes. Some open-source review tools proxy your dev server and add a comment layer that your coding agent reads; most are designed mainly for a developer reviewing their own agent's work. With Butterneck, the product manager opens the share link from wherever they are, with no account needed to look, and types the change in the chat on the page they mean. You choose who can ask. The coding assistant already signed in on a developer's connected computer edits the project, and hot reload shows the result on the same link, so they can keep asking until it is right. Butterneck does not commit, push, open a pull request, merge or deploy; nothing ships until a developer publishes the change.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;Starter is free for one developer and one person who asks for changes, with one private copy and 1 GB of preview traffic a month. Pro is USD 19 per person per month and adds more copies and more traffic, and a workspace owner on Starter can try Pro for one month from the Billing page. See &lt;a href="https://www.butterneck.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt; for the details, or read &lt;a href="https://www.butterneck.com/#how-it-works" rel="noopener noreferrer"&gt;how it works&lt;/a&gt; on the home page.&lt;/p&gt;

&lt;p&gt;The change is usually small. Getting the request to the project is what takes the week. A link to the app that's already running on your computer removes most of that.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>devtools</category>
      <category>productivity</category>
      <category>productmanagement</category>
    </item>
    <item>
      <title>Itera alternative: an honest comparison with Butterneck</title>
      <dc:creator>Butterneck</dc:creator>
      <pubDate>Wed, 04 Nov 2026 05:44:20 +0000</pubDate>
      <link>https://dev.to/butterneck/itera-alternative-an-honest-comparison-with-butterneck-f98</link>
      <guid>https://dev.to/butterneck/itera-alternative-an-honest-comparison-with-butterneck-f98</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.butterneck.com/blog/itera-alternative" rel="noopener noreferrer"&gt;butterneck.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;If you are looking at Itera and wondering whether there is an alternative that fits your team better, this post compares Itera and Butterneck side by side. We make Butterneck, so we are not neutral. We have tried to stick to what each product says publicly, and to be clear about where Itera may be the better pick.&lt;/p&gt;

&lt;p&gt;Everything about Itera below comes from its public website, &lt;a href="https://iteradev.ai" rel="noopener noreferrer"&gt;iteradev.ai&lt;/a&gt;, and the customer docs it published, as read on October 27–29, 2026. Products change. Check their site for the current details.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Itera vs Butterneck, in short:&lt;/strong&gt; Itera takes a change from idea through design and engineering scoping to a written brief, and a coding agent turns it into an AI-generated pull request. Butterneck handles small changes on a live copy of the app: it runs on the developer's computer with the coding agent they already use, Butterneck does not commit, push or open a pull request, and a developer decides first what ships.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  What Itera says it does
&lt;/h2&gt;

&lt;p&gt;Itera describes itself as "the shared context layer where PMs, designers, and engineers iterate on the live product together, then hand coding agents the complete brief they need to ship."&lt;/p&gt;

&lt;p&gt;Its site lists this flow:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A PM describes a change in plain language, grounded in the live codebase.&lt;/li&gt;
&lt;li&gt;A designer refines the UX on a live prototype built from the team's real components and design system.&lt;/li&gt;
&lt;li&gt;An engineer answers high-level questions such as API contracts, service boundaries, and dependencies.&lt;/li&gt;
&lt;li&gt;Itera turns the conversation, prototype, and decisions into an execution-ready brief. A coding agent (Claude Code, Codex, Cursor, or Copilot) claims the planned PR and implements it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Features listed on the site include GitHub, GitLab, and Bitbucket integration, design-system-aware output, branch-based frontend previews, ephemeral environments with mock data for backend-touching changes, test suite integration, a Point &amp;amp; Edit visual mode, AI-generated pull requests, and a view of every change in flight across teams.&lt;/p&gt;

&lt;p&gt;Its public pricing says "One seat per builder. Collaborators are always free." and "Currently free for early partners". Two paid plans are listed: Builder at €30 per seat per month, which includes 5 iterations per month, and Unlimited at €100 per seat per month, which adds unlimited iterations, priority support, multi-repo workspaces, and advanced review workflows.&lt;/p&gt;

&lt;p&gt;That is a full product-development workflow: discovery, design, architecture scoping, and a planned PR at the end.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Butterneck does
&lt;/h2&gt;

&lt;p&gt;Butterneck is narrower. It handles the small change on a product that already runs.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A PM or stakeholder opens a share link to a live copy of the app and types the change into a chat next to the screen they mean. Or they label a Jira ticket &lt;code&gt;butterneck&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;A coding agent CLI the developer already uses (Cursor &lt;code&gt;agent&lt;/code&gt;, Claude Code &lt;code&gt;claude&lt;/code&gt;, or Antigravity &lt;code&gt;agy&lt;/code&gt;) runs on the developer's own computer and edits the connected project folder.&lt;/li&gt;
&lt;li&gt;The preview updates on the same link. The developer reads the conversation, checks the change, and publishes it the way the team already does.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Butterneck never merges, never opens a pull request, and never deploys. You decide what goes live.&lt;/p&gt;

&lt;p&gt;If you want the mechanics, we wrote up &lt;a href="https://www.butterneck.com/blog/run-ai-coding-agent-sandbox-on-your-machine" rel="noopener noreferrer"&gt;how the agent runs in a sandbox on your machine&lt;/a&gt; and &lt;a href="https://www.butterneck.com/blog/human-in-the-loop-ai-coding" rel="noopener noreferrer"&gt;why we keep a human in the loop&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  The main differences
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Scope of the workflow
&lt;/h3&gt;

&lt;p&gt;Itera covers the path from idea through design and architecture to a planned PR. It is built for changes that need a designer, an engineer's scoping, and a written brief.&lt;/p&gt;

&lt;p&gt;Butterneck covers the last step for small changes: copy, layout, a missing field, a wrong color, a broken link. The kind of request where the change takes minutes and the back-and-forth takes a week.&lt;/p&gt;

&lt;h3&gt;
  
  
  Where the agent runs
&lt;/h3&gt;

&lt;p&gt;Itera says it connects to your Git host and hands the brief to a coding agent through an installed skill.&lt;/p&gt;

&lt;p&gt;In Butterneck, the agent runs on a developer's computer, in a folder the developer picks, using the CLI they are already signed in to (team, enterprise or API plans recommended). To be exact about data: the coding CLI sends prompts and code context to its own AI provider, as it does when you use it directly. Chat messages and preview traffic go through the Butterneck server so the share link works. See &lt;a href="https://www.butterneck.com/blog/run-ai-coding-agent-sandbox-on-your-machine" rel="noopener noreferrer"&gt;what leaves your machine&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  What you get at the end
&lt;/h3&gt;

&lt;p&gt;Itera's output is an AI-generated pull request.&lt;/p&gt;

&lt;p&gt;Butterneck's output is edited files in a folder and a running preview. Butterneck does not open a PR. The developer reviews the diff, then commits, opens a PR, or throws it away. Some teams want the PR made for them. Others want the AI kept out of the release pipeline entirely. That is the clearest fork between the two tools.&lt;/p&gt;

&lt;h3&gt;
  
  
  Previews
&lt;/h3&gt;

&lt;p&gt;Itera lists branch-based frontend previews and ephemeral environments with mock data.&lt;/p&gt;

&lt;p&gt;Butterneck's preview is the app running on the developer's machine, with real local data, shared through a public link. No VPN, staging deploy, or localhost link. More on that in &lt;a href="https://www.butterneck.com/blog/share-local-app-without-deploying" rel="noopener noreferrer"&gt;how to share a local app without deploying&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Jira
&lt;/h3&gt;

&lt;p&gt;Butterneck has a Jira Cloud integration. Add the label &lt;code&gt;butterneck&lt;/code&gt; to a ticket and assign it to a teammate whose Jira account is mapped to a computer that has the project. Its own copy opens, named after the ticket. The title, description, latest comments, and attachments become the request. When the AI is done, a short note and a preview link are posted back to the ticket. Itera's MCP documentation lets a new Itera task be linked to a Jira ticket (&lt;code&gt;ticketProvider: JIRA&lt;/code&gt;). We didn't find a Jira trigger like a label or assignee, or a preview link posted back to the ticket, in its public docs. Check with them if that matters to you.&lt;/p&gt;

&lt;h3&gt;
  
  
  Pricing
&lt;/h3&gt;

&lt;p&gt;Itera lists two plans: Builder at €30 per seat per month with 5 iterations per month, and Unlimited at €100 per seat per month with unlimited iterations. Its site says "One seat per builder. Collaborators are always free." and that it is "Currently free for early partners".&lt;/p&gt;

&lt;p&gt;Butterneck has a free Starter plan for one developer and one requester with one private copy. Pro is USD 19 per person per month (also priced in INR, EUR, GBP, AUD, CAD, SGD, and AED), with 20% off annual billing, 50 private copies, and 50 GB of preview traffic per month. You also pay for your own coding agent subscription. Details on &lt;a href="https://www.butterneck.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;. A workspace owner on Starter can also start a one-month Pro trial from the Billing page, once per workspace.&lt;/p&gt;

&lt;h2&gt;
  
  
  When Itera is likely the better fit
&lt;/h2&gt;

&lt;p&gt;Be honest with yourself about the kind of change you are shipping.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You want a designer and engineer involved in shaping each change, with a written brief.&lt;/li&gt;
&lt;li&gt;You want AI-generated pull requests, with your test suite run against them.&lt;/li&gt;
&lt;li&gt;Your changes often touch the backend and benefit from ephemeral environments.&lt;/li&gt;
&lt;li&gt;You want one place to see every change in flight across several teams.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  When Butterneck is likely the better fit
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Most requests are small, and the slow part is explaining which page and which button.&lt;/li&gt;
&lt;li&gt;You want the person asking to see the change on the live app, not a ticket status.&lt;/li&gt;
&lt;li&gt;You want the AI to edit files and stop there. No PRs, no merges, no deploys.&lt;/li&gt;
&lt;li&gt;You already pay for Cursor, Claude Code, or Antigravity on a team or API plan and want the product team to use it through a connected developer computer.&lt;/li&gt;
&lt;li&gt;Your requests already live in Jira and you want a label and an assignee to start the work, with the preview link posted back on the ticket.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  When neither is a fit
&lt;/h2&gt;

&lt;p&gt;Butterneck needs a local project folder on a developer's computer, and it does not replace a cloud IDE or a staff augmentation contract. If you want changes to merge themselves, it is not for you.&lt;/p&gt;

&lt;h2&gt;
  
  
  Other Itera alternatives
&lt;/h2&gt;

&lt;p&gt;If what you like about Itera is the whole team shaping a change on the real product and ending in a pull request, these tools work that way too (quotes from each tool's own site, checked 31 October 2026):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Alloy&lt;/strong&gt;: "Product managers and designers use cloud agents to propose real changes as pull requests…" "Prompt your idea, share a link for feedback, and push to GitHub." (&lt;a href="https://alloy.app/cloud-agents" rel="noopener noreferrer"&gt;alloy.app&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Plusma&lt;/strong&gt;: "Describe a change, preview it live, iterate until it's right, and hand your team a clean PR." (&lt;a href="https://plusma.ai/" rel="noopener noreferrer"&gt;plusma.ai&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Refinar&lt;/strong&gt;: describe a change, watch it in a live preview, "then publish it or send it to engineering as a pull request." (&lt;a href="https://refinar.ai/en/for/product-managers" rel="noopener noreferrer"&gt;refinar.ai&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Builder.io&lt;/strong&gt;: "Point Builder at the Slack thread, Jira ticket, or PRD, and the context comes with it." (&lt;a href="https://www.builder.io/for/product-managers" rel="noopener noreferrer"&gt;builder.io&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For prices, where each one runs and who it's for, see &lt;a href="https://www.butterneck.com/blog/tools-for-non-developers-to-change-an-existing-app" rel="noopener noreferrer"&gt;AI tools that let non-developers change an existing web app&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Is Butterneck a direct Itera alternative?
&lt;/h3&gt;

&lt;p&gt;Partly. Both let non-engineers drive changes on a real product with AI. Itera covers more of the product-development process and ends in a PR. Butterneck focuses on small changes on a live copy and ends in a preview a developer reviews.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does Butterneck open pull requests like Itera?
&lt;/h3&gt;

&lt;p&gt;No. Butterneck edits files in the connected folder. The developer decides whether to commit, open a PR, or discard the change.&lt;/p&gt;

&lt;h3&gt;
  
  
  Where are files edited with Butterneck, and what leaves the computer?
&lt;/h3&gt;

&lt;p&gt;The files are edited on a developer's connected computer and Butterneck does not run its own model. But the coding CLI sends code context to its AI provider, and chat and preview traffic pass through Butterneck's server.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which coding agents does each support?
&lt;/h3&gt;

&lt;p&gt;Itera's site lists Claude Code, Codex, Cursor, and Copilot. Butterneck supports the Cursor, Claude Code, and Antigravity CLIs.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I try Butterneck for free?
&lt;/h3&gt;

&lt;p&gt;Yes. Starter is free for one developer and one person asking for changes, and a workspace owner can start a one-month Pro trial from the Billing page.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;If your team's small changes stall in handoffs, &lt;a href="https://calendar.app.google/p2McAaz4ZwXBiG5m9" rel="noopener noreferrer"&gt;book a 30-minute demo&lt;/a&gt; and we will run a real request on a live copy. Or see &lt;a href="https://www.butterneck.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt; and start on the free plan. More on the product at &lt;a href="https://dev.to/"&gt;butterneck.com&lt;/a&gt;. Comparing a cloud-sandbox tool too? Read our &lt;a href="https://www.butterneck.com/blog/clogless-alternative" rel="noopener noreferrer"&gt;Clogless alternative&lt;/a&gt; comparison. For a wider comparison, see &lt;a href="https://www.butterneck.com/blog/tools-for-non-developers-to-change-an-existing-app" rel="noopener noreferrer"&gt;AI tools that let non-developers change an existing web app&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>devtools</category>
      <category>productmanagement</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Clogless alternative: an honest comparison with Butterneck</title>
      <dc:creator>Butterneck</dc:creator>
      <pubDate>Wed, 04 Nov 2026 05:44:12 +0000</pubDate>
      <link>https://dev.to/butterneck/clogless-alternative-an-honest-comparison-with-butterneck-4hlh</link>
      <guid>https://dev.to/butterneck/clogless-alternative-an-honest-comparison-with-butterneck-4hlh</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.butterneck.com/blog/clogless-alternative" rel="noopener noreferrer"&gt;butterneck.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;If you are weighing Clogless and wondering whether an alternative fits your team better, this post compares Clogless and Butterneck side by side. We make Butterneck, so we are not neutral. The two products go after the same problem: small product changes that sit in the engineering backlog. They solve it in different ways. We have tried to stick to what each product says publicly, and to be clear about where Clogless is likely the better pick.&lt;/p&gt;

&lt;p&gt;Everything about Clogless below comes from its public website, &lt;a href="https://clogless.ai" rel="noopener noreferrer"&gt;clogless.ai&lt;/a&gt;, as read on 28 October 2026, mainly its home, how it works, ticket to pull request, security, and pricing pages. Clogless is a new product, and new products change fast. Check their site for the current details.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Clogless vs Butterneck, in short:&lt;/strong&gt; Clogless works an idea or ticket in a disposable cloud sandbox, shows a live preview on your codebase, and then opens a pull request with your Git provider for engineering to review and merge. Butterneck handles small changes on a live copy of the app: it runs on the developer's computer with the coding agent they already use, Butterneck does not commit, push or open a pull request, and a developer decides first what ships.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  What Clogless says it does
&lt;/h2&gt;

&lt;p&gt;Clogless calls itself an "AI workspace that turns tickets into pull requests". Its home page says its agents "take any idea from plan to live preview on your codebase in a secure cloud environment, then hand engineering a pull request instead of a request."&lt;/p&gt;

&lt;p&gt;Its site describes three ways to start work:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Explore&lt;/strong&gt;, from an idea: draft a PRD with its agents and see the change on your real product, ending with a ticket and an open PR.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Solve&lt;/strong&gt;, from an existing ticket: agents work the ticket in an isolated environment while you watch and steer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ship&lt;/strong&gt;, from an existing PR: comment on the PR and Clogless deploys a live environment for reviewers to click through.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each unit of work gets "a disposable, isolated cloud sandbox". You configure its shape once (base image, services, secrets, integrations), and each environment cleans itself up when the work merges or goes idle.&lt;/p&gt;

&lt;p&gt;For tickets, Clogless says: "Connect your ticketing system once, then open the ticket you want to work on in Clogless." When the change is ready, "Clogless opens a pull request with your Git provider", and engineering reviews and merges it.&lt;/p&gt;

&lt;p&gt;Its ticket-to-PR page lists Jira, Linear, Trello, monday.com, Notion, and Asana for tickets; GitHub and Bitbucket for Git; and React, Next.js, Angular, and Vite as frameworks. Figma and Slack integrations are included on every plan. Admin roles ship on every plan, and Team and Enterprise add role-based permissions.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Butterneck does
&lt;/h2&gt;

&lt;p&gt;Butterneck handles the small change on a product that already runs, and stops before anything goes live.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A developer installs a small connector on a computer that already has the project and a coding assistant already signed in: Cursor, Claude Code, or Antigravity (team, enterprise or API plans recommended).&lt;/li&gt;
&lt;li&gt;A PM or stakeholder opens a share link to a live copy of the app and types the change into a chat next to the screen they mean. Or someone adds the label &lt;code&gt;butterneck&lt;/code&gt; to a Jira ticket and assigns it.&lt;/li&gt;
&lt;li&gt;The coding assistant on that computer edits the connected project, and the preview updates on the same link.&lt;/li&gt;
&lt;li&gt;The developer reads the conversation, checks the change, and publishes it the way the team already does.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Butterneck never opens pull requests, never merges, and never deploys. You decide what goes live.&lt;/p&gt;

&lt;h2&gt;
  
  
  The main differences
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Where the work runs
&lt;/h3&gt;

&lt;p&gt;Clogless runs each idea, ticket, or PR in its own cloud sandbox, set up once from a base image, services, and secrets you configure.&lt;/p&gt;

&lt;p&gt;Butterneck runs on a computer your team connects, in a project that already runs there, with the coding assistant that is already signed in (team, enterprise or API plans recommended). There is no per-ticket environment to configure. The trade-offs are real: that computer has to be on for the preview to load and for work to start, and &lt;code&gt;.env&lt;/code&gt; handling is a guardrail, not a hard block. Secret settings files are on an ignore list the AI is told to stay out of, so keep production secrets off that computer. More on data flow in &lt;a href="https://www.butterneck.com/blog/run-ai-coding-agent-sandbox-on-your-machine" rel="noopener noreferrer"&gt;how the agent runs on your machine&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  What you get at the end
&lt;/h3&gt;

&lt;p&gt;Clogless ends in a pull request that it opens with your Git provider.&lt;/p&gt;

&lt;p&gt;Butterneck ends in edited files in the connected project and a running preview. There is no bot PR. The developer who checked the preview commits the change, opens a PR, or throws it away, so the change has a human owner from the start. We wrote about why that matters in &lt;a href="https://www.butterneck.com/blog/ai-prs-need-an-owner" rel="noopener noreferrer"&gt;AI pull requests need an owner&lt;/a&gt;. Some teams want the PR made for them; others want the AI kept out of the release pipeline. That is the clearest fork between the two tools.&lt;/p&gt;

&lt;h3&gt;
  
  
  How a Jira ticket starts the work
&lt;/h3&gt;

&lt;p&gt;In Clogless, you connect your ticketing system and open the ticket in Clogless.&lt;/p&gt;

&lt;p&gt;In Butterneck, the work starts inside Jira. Add the label &lt;code&gt;butterneck&lt;/code&gt; to a ticket and assign it to a teammate whose Jira account is mapped to a computer that has the project. Its own copy opens, named after the ticket, and the title, description, latest comments, and attachments become the request. When the AI is done, a short note and a preview link are posted back to the ticket. We did not find a description of posting results back to the ticket on Clogless's public pages. Ask them if that matters to you. Details on the &lt;a href="https://www.butterneck.com/integrations/jira" rel="noopener noreferrer"&gt;Jira integration page&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Breadth
&lt;/h3&gt;

&lt;p&gt;Clogless covers more ground: six ticketing tools (Butterneck supports only Jira Cloud), PRD drafting with agents, preview environments from a PR comment, and, on its Team plan, real-time collaboration and a context lake (its QA agents are not included on Team). Butterneck does none of those. It is built for one loop: someone asks for a small change, sees it on a live copy, and a developer decides.&lt;/p&gt;

&lt;h3&gt;
  
  
  Pricing
&lt;/h3&gt;

&lt;p&gt;Clogless lists Starter at $99 per month and Team at $489 per month, billed monthly on an annual commitment (as of Oct 30, 2026, per &lt;a href="https://clogless.ai/pricing" rel="noopener noreferrer"&gt;Clogless's pricing page&lt;/a&gt;), plus Enterprise through sales. Starter includes 1 project or repo and 2 environments; Team includes 4 and 8. AI usage is listed as "Credit / BYOK". We did not see a per-seat price on the page.&lt;/p&gt;

&lt;p&gt;Butterneck has a free Starter plan for one developer and one person who asks for changes. Pro is USD 19 per person per month, billed monthly, with 20% off annual billing. You also pay for your own coding assistant subscription. Details on &lt;a href="https://www.butterneck.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;. A workspace owner on Starter can also start a one-month Pro trial from the Billing page, once per workspace.&lt;/p&gt;

&lt;h2&gt;
  
  
  Side by side
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Clogless&lt;/th&gt;
&lt;th&gt;Butterneck&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Where the AI works&lt;/td&gt;
&lt;td&gt;A cloud sandbox per idea, ticket, or PR&lt;/td&gt;
&lt;td&gt;A connected computer that already runs the project&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;AI engine&lt;/td&gt;
&lt;td&gt;Clogless agents; usage by credit or your own key&lt;/td&gt;
&lt;td&gt;Your signed-in Cursor, Claude Code, or Antigravity&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;End result&lt;/td&gt;
&lt;td&gt;A pull request with GitHub or Bitbucket&lt;/td&gt;
&lt;td&gt;Edited files and a live preview; the developer opens the PR&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who publishes&lt;/td&gt;
&lt;td&gt;Engineering reviews and merges the PR&lt;/td&gt;
&lt;td&gt;The developer publishes the usual way&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Ticketing&lt;/td&gt;
&lt;td&gt;Jira, Linear, Trello, monday.com, Notion, Asana&lt;/td&gt;
&lt;td&gt;Jira Cloud only&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;How a ticket starts&lt;/td&gt;
&lt;td&gt;Open the ticket in Clogless&lt;/td&gt;
&lt;td&gt;Label &lt;code&gt;butterneck&lt;/code&gt; and assign it in Jira&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Back on the ticket&lt;/td&gt;
&lt;td&gt;Not found on their public pages&lt;/td&gt;
&lt;td&gt;A note and a preview link&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pricing&lt;/td&gt;
&lt;td&gt;$99/mo Starter, $489/mo Team, billed monthly on an annual commitment&lt;/td&gt;
&lt;td&gt;Free Starter; Pro $19 per person per month; one-month Pro trial&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Clogless prices: $99/mo Starter and $489/mo Team, billed monthly on an annual commitment (as of Oct 30, 2026, per &lt;a href="https://clogless.ai/pricing" rel="noopener noreferrer"&gt;Clogless's pricing page&lt;/a&gt;).&lt;/p&gt;

&lt;h2&gt;
  
  
  When Clogless fits better
&lt;/h2&gt;

&lt;p&gt;Be honest about how your team ships.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You want a pull request opened for you at the end of every change.&lt;/li&gt;
&lt;li&gt;Your tickets live in Linear, Trello, monday.com, Notion, or Asana rather than Jira.&lt;/li&gt;
&lt;li&gt;You want a fresh cloud environment for each change, with no team computer that has to stay on.&lt;/li&gt;
&lt;li&gt;You want agents to help draft the PRD before any code is written.&lt;/li&gt;
&lt;li&gt;You want live preview environments from a comment on an existing PR.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  When Butterneck fits better
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Your requests already live in Jira and you want a label and an assignee to start the work, with the preview link landing back on the ticket.&lt;/li&gt;
&lt;li&gt;You want the AI to edit files and stop there. No PRs, no merges, no deploys.&lt;/li&gt;
&lt;li&gt;You would rather not configure a cloud environment, and the project already runs on a developer's computer.&lt;/li&gt;
&lt;li&gt;You already pay for Cursor, Claude Code, or Antigravity on a team or API plan and want the product team to use it through a connected developer computer.&lt;/li&gt;
&lt;li&gt;You want to start free and pay per person, month to month.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  When neither is a fit
&lt;/h2&gt;

&lt;p&gt;If you want changes to merge themselves, neither tool is built for that. Both keep engineering in charge of what ships. And if your request is a new feature that needs design and architecture work, start with your team, not a chat box.&lt;/p&gt;

&lt;h2&gt;
  
  
  Other Clogless alternatives
&lt;/h2&gt;

&lt;p&gt;If the pull request at the end is what you like about Clogless, these tools also end in a PR for engineering to review (quotes from each tool's own site, checked 30 October 2026):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;ronda&lt;/strong&gt;: "ronda writes the code and opens a pull request. Engineering reviews and merges." (&lt;a href="https://useronda.com/" rel="noopener noreferrer"&gt;useronda.com&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Plusma&lt;/strong&gt;: "Describe a change, preview it live, iterate until it's right, and hand your team a clean PR." (&lt;a href="https://plusma.ai/" rel="noopener noreferrer"&gt;plusma.ai&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Refinar&lt;/strong&gt;: describe a change, watch it in a live preview, "then publish it or send it to engineering as a pull request." (&lt;a href="https://refinar.ai/en/for/product-managers" rel="noopener noreferrer"&gt;refinar.ai&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Synlets&lt;/strong&gt;: "Tickets in. Pull requests out." You assign a ticket to its agent. (&lt;a href="https://synlets.com/" rel="noopener noreferrer"&gt;synlets.com&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For prices, where each one runs and who it's for, see &lt;a href="https://www.butterneck.com/blog/tools-for-non-developers-to-change-an-existing-app" rel="noopener noreferrer"&gt;AI tools that let non-developers change an existing web app&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Is Butterneck a direct Clogless alternative?
&lt;/h3&gt;

&lt;p&gt;For small changes on a live product, yes. Both let product managers and designers ask for a change and see it running before engineering accepts it. Clogless runs in cloud sandboxes and ends in a pull request. Butterneck runs on a computer your team connects and ends in a preview that a developer publishes.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does Butterneck open pull requests like Clogless?
&lt;/h3&gt;

&lt;p&gt;No. Butterneck edits files in the connected project. The developer decides whether to commit, open a PR, or discard the change.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does Butterneck work with Linear, Trello, or Asana?
&lt;/h3&gt;

&lt;p&gt;No. Butterneck's ticket integration is Jira Cloud only. Without Jira, people ask for changes in the chat on the live copy.&lt;/p&gt;

&lt;h3&gt;
  
  
  Where are files edited with Butterneck, and what leaves the computer?
&lt;/h3&gt;

&lt;p&gt;The files are edited on the connected computer, and Butterneck does not run its own model. But the coding assistant sends code context to its AI provider, and chat and preview traffic pass through Butterneck's server.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I try Butterneck for free?
&lt;/h3&gt;

&lt;p&gt;Yes. Starter is free for one developer and one person asking for changes, and a workspace owner can start a one-month Pro trial from the Billing page.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;If your team's small changes stall in the backlog, &lt;a href="https://calendar.app.google/p2McAaz4ZwXBiG5m9" rel="noopener noreferrer"&gt;book a 30-minute demo&lt;/a&gt; and we will run a real request on a live copy. Or see &lt;a href="https://www.butterneck.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt; and start on the free plan. If you are comparing other tools too, we also wrote an &lt;a href="https://www.butterneck.com/blog/itera-alternative" rel="noopener noreferrer"&gt;Itera alternative&lt;/a&gt; comparison. For a wider comparison, see &lt;a href="https://www.butterneck.com/blog/tools-for-non-developers-to-change-an-existing-app" rel="noopener noreferrer"&gt;AI tools that let non-developers change an existing web app&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>devtools</category>
      <category>productmanagement</category>
      <category>webdev</category>
    </item>
    <item>
      <title>AI change requests: Jira ticket to pull request with AI</title>
      <dc:creator>Butterneck</dc:creator>
      <pubDate>Wed, 04 Nov 2026 05:43:49 +0000</pubDate>
      <link>https://dev.to/butterneck/jira-ticket-to-pull-request-with-ai-check-a-live-preview-before-anyone-opens-the-pr-5701</link>
      <guid>https://dev.to/butterneck/jira-ticket-to-pull-request-with-ai-check-a-live-preview-before-anyone-opens-the-pr-5701</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.butterneck.com/blog/jira-ticket-to-pr-with-ai" rel="noopener noreferrer"&gt;butterneck.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Butterneck lets a product person turn a Jira ticket into a change to a live web app and check it on a live preview. Butterneck does not commit, push or open a pull request; a developer decides first. For "Jira ticket to pull request", that means a label starts the work, an AI coding agent makes the change on its own copy of your app on the developer's computer, the person who asked checks the preview, and then a developer decides whether to open a pull request. Butterneck never opens the PR itself.&lt;/p&gt;

&lt;p&gt;Plenty of tools now promise to turn a Jira ticket into a pull request with AI. The idea is good. Most tickets for small changes are clear enough that a coding agent can do the edit. The hard questions are about what happens around it: who sees the result, who checks it, and what reaches your main branch.&lt;/p&gt;

&lt;p&gt;This post walks through a ticket-to-change workflow for product teams, and how Butterneck handles it. One honest note up front: Butterneck does not open the PR itself. It turns the ticket into a reviewable change on a live preview. Your developer opens the PR. We explain why below.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Jira ticket to pull request, in short:&lt;/strong&gt; Add the &lt;code&gt;butterneck&lt;/code&gt; label to a Jira ticket assigned to a mapped teammate, and an AI coding agent makes the change on its own copy of your app on that developer's computer, with the coding agent they already use (Cursor, Claude Code or Antigravity). A preview link goes back on the ticket and the person who asked checks it. Butterneck does not commit, push or open a pull request; a developer decides first whether to open one, and Butterneck never merges or deploys.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Jira ticket to pull request: where Butterneck fits
&lt;/h2&gt;

&lt;p&gt;The path from a ticket to a PR has three steps, and Butterneck covers the first two:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The ticket starts the work.&lt;/strong&gt; Adding the &lt;code&gt;butterneck&lt;/code&gt; label to a ticket assigned to a mapped teammate opens its own copy named after the ticket, and the agent works from the ticket's text and attachments.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The requester checks a live preview.&lt;/strong&gt; A link to the running app with the change goes back on the ticket. The requester looks at it and keeps refining in chat until it is right.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A developer decides about the PR.&lt;/strong&gt; The developer reads the conversation and the diff. If the change is worth keeping, they commit on a branch and open the PR with your usual process. If not, the change is thrown away and no PR ever exists.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;So if you want a tool that creates the pull request for you, Butterneck is not it. If you want the person who wrote the ticket to see the change before anyone spends review time on a PR, that is the gap it fills.&lt;/p&gt;

&lt;h2&gt;
  
  
  What "Jira to PR with AI" usually means
&lt;/h2&gt;

&lt;p&gt;The common pattern:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A ticket is assigned to an AI agent.&lt;/li&gt;
&lt;li&gt;The agent reads the ticket, checks out the repo, and makes changes.&lt;/li&gt;
&lt;li&gt;The agent opens a pull request.&lt;/li&gt;
&lt;li&gt;An engineer reviews the diff.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;That moves the code part faster. But for the person who wrote the ticket, often a PM, nothing changes. They still cannot see the result until someone deploys a preview. And the engineer reviewing the diff still has to guess whether it matches what the PM meant.&lt;/p&gt;

&lt;h2&gt;
  
  
  The missing step: seeing the change
&lt;/h2&gt;

&lt;p&gt;For product changes, the reviewer that matters first is the person who asked. A diff does not tell a PM whether the empty state reads well. A running app does.&lt;/p&gt;

&lt;p&gt;So a useful ticket-to-change flow should give the ticket author a live preview, let them refine it, and only then put it in front of an engineer. (More on what to check in &lt;a href="https://www.butterneck.com/blog/live-preview-before-pull-request" rel="noopener noreferrer"&gt;a live preview before the PR&lt;/a&gt;.)&lt;/p&gt;

&lt;h2&gt;
  
  
  How the Jira flow works in Butterneck
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Connect Jira once
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Sign in with Jira Cloud and choose your site.&lt;/li&gt;
&lt;li&gt;Link a Jira project to your app in Butterneck.&lt;/li&gt;
&lt;li&gt;Paste Butterneck's address into Jira, so Jira can tell Butterneck when a ticket is created or updated.&lt;/li&gt;
&lt;li&gt;Map each developer's Jira account to their computer.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Label a ticket to start
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Add the label &lt;code&gt;butterneck&lt;/code&gt; to a ticket.&lt;/li&gt;
&lt;li&gt;Assign it to a teammate whose Jira account is mapped to a computer that has the project. If the assignee isn't mapped, nothing starts; the Jira page in Butterneck shows why.&lt;/li&gt;
&lt;li&gt;Butterneck opens its own copy of the project named after the ticket.&lt;/li&gt;
&lt;li&gt;The ticket's title, description, latest comments, and attached files become the request.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The agent makes the change
&lt;/h3&gt;

&lt;p&gt;The coding agent runs on the assignee's computer, in that copy's folder, using the CLI they are already signed in to: Cursor, Claude Code, or Antigravity (team, enterprise or API plans recommended). The app runs there too, and Butterneck gives it a share link.&lt;/p&gt;

&lt;h3&gt;
  
  
  The preview goes back on the ticket
&lt;/h3&gt;

&lt;p&gt;When the AI is done, a short note and a link to the preview are posted back to the Jira ticket. The full conversation stays on the live copy, where anyone allowed can keep refining in chat. Updating the same ticket later does not open a second copy.&lt;/p&gt;

&lt;p&gt;You can also paste a ticket number into an existing chat to load that ticket.&lt;/p&gt;

&lt;h2&gt;
  
  
  From preview to PR
&lt;/h2&gt;

&lt;p&gt;Once the change looks right, the developer:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Reads the conversation on the live copy.&lt;/li&gt;
&lt;li&gt;Checks the diff in their own editor or git client.&lt;/li&gt;
&lt;li&gt;Commits on a branch and opens a PR the way the team already does, with the Jira key in the branch name or title if that is your convention.&lt;/li&gt;
&lt;li&gt;Your normal review, CI, and deploy take over.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If the copy is a git worktree, the change is already on its own branch and checkout, separate from the main working copy.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to link a Jira ticket to a PR
&lt;/h2&gt;

&lt;p&gt;Once a developer opens the pull request, you will want it to show up on the Jira ticket. Butterneck doesn't do this step, because it doesn't open the PR. Jira's own development integrations do. With Jira Cloud connected to GitHub (through the GitHub for Jira app), Bitbucket or GitLab, Jira links development work to an issue when the issue key appears in it (&lt;a href="https://support.atlassian.com/jira-software-cloud/docs/reference-issues-in-your-development-work/" rel="noopener noreferrer"&gt;Atlassian: reference issues in your development work&lt;/a&gt;):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Branch name:&lt;/strong&gt; for example &lt;code&gt;PROJ-123-update-pricing-copy&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Commit message:&lt;/strong&gt; for example &lt;code&gt;PROJ-123 Update pricing copy&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pull request title:&lt;/strong&gt; for example &lt;code&gt;PROJ-123: Update pricing copy&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Use the key in capitals, exactly as Jira shows it. Once linked, the PR appears in the ticket's Development panel. So the full path for a labelled ticket is: the AI coding agent makes the change on a live copy, the requester checks the preview, and the developer commits on a branch named with the ticket key and opens the PR. The ticket then shows the preview link Butterneck posted and the PR your Git provider linked.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Butterneck stops before the PR
&lt;/h2&gt;

&lt;p&gt;We get asked this a lot. Short version, from &lt;a href="https://www.butterneck.com/blog/human-in-the-loop-ai-coding" rel="noopener noreferrer"&gt;human-in-the-loop AI coding&lt;/a&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The person asking is often not a developer.&lt;/strong&gt; They should approve what they see, not a diff.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Your release process already exists.&lt;/strong&gt; Branch names, PR templates, reviewers, CI. A tool that creates PRs has to fit all of it. A developer opening the PR fits by default.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mistakes stay cheap.&lt;/strong&gt; A bad turn can be stopped and, in most cases, rolled back. A wrong change can be thrown away. Nothing has touched your remote.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;There is no code path in Butterneck that pushes, opens a PR, merges, or deploys. If you want PRs created automatically, a PR-generating tool is a better fit. See our &lt;a href="https://www.butterneck.com/blog/clogless-alternative" rel="noopener noreferrer"&gt;Clogless comparison&lt;/a&gt; or &lt;a href="https://www.butterneck.com/blog/itera-alternative" rel="noopener noreferrer"&gt;Itera comparison&lt;/a&gt; for examples.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to put in a ticket so the AI does well
&lt;/h2&gt;

&lt;p&gt;The agent reads the title, description, latest comments, and attachments. Tickets that work well:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Name the page or screen: "Checkout, step 2".&lt;/li&gt;
&lt;li&gt;Say what is there now and what it should be: "Button says Continue. Should say Review order."&lt;/li&gt;
&lt;li&gt;Attach a screenshot when the location is not obvious.&lt;/li&gt;
&lt;li&gt;Keep one change per ticket. Small tickets give small, reviewable diffs.&lt;/li&gt;
&lt;li&gt;Leave out anything that needs secrets or production data.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For a copy-ready version, put the five-line template from &lt;a href="https://www.butterneck.com/blog/how-to-write-a-change-request-for-ai" rel="noopener noreferrer"&gt;how to write a change request for an AI coding agent&lt;/a&gt; in the ticket description.&lt;/p&gt;

&lt;h2&gt;
  
  
  Security notes for CTOs
&lt;/h2&gt;

&lt;p&gt;For the full picture of folders, the ignore list and what leaves the machine, read &lt;a href="https://www.butterneck.com/blog/run-ai-coding-agent-sandbox-on-your-machine" rel="noopener noreferrer"&gt;how Butterneck runs the coding agent in a sandbox on your machine&lt;/a&gt;.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The agent works only in the folder tied to the copy.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;.env&lt;/code&gt; files and team-defined globs are on an ignore list given to the agent as an instruction. It is not a hard sandbox, so keep production secrets off the bridge machine.&lt;/li&gt;
&lt;li&gt;The coding CLI sends prompts and code context to its own AI provider, under your agreement with that provider.&lt;/li&gt;
&lt;li&gt;Chat messages and preview traffic pass through Butterneck's server.&lt;/li&gt;
&lt;li&gt;Every turn takes a baseline first, so a stopped turn usually rolls its file changes back. If the rollback can't be completed, for example because a changed file was too large to snapshot, the chat says so.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;More in &lt;a href="https://www.butterneck.com/blog/run-ai-coding-agent-sandbox-on-your-machine" rel="noopener noreferrer"&gt;how Butterneck runs an AI coding agent in a sandbox on your machine&lt;/a&gt; and &lt;a href="https://www.butterneck.com/blog/human-in-the-loop-architecture-for-ai-product-changes" rel="noopener noreferrer"&gt;human-in-the-loop architecture for AI product changes&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;See it before you set anything up:&lt;/strong&gt; &lt;a href="https://app.butterneck.com/trial" rel="noopener noreferrer"&gt;create a free account and try a request on a sample shop&lt;/a&gt; before connecting a computer. On your own project, the edit runs on a developer's connected computer. Your team still decides what goes live.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Can Butterneck turn a Jira ticket into a pull request?
&lt;/h3&gt;

&lt;p&gt;It turns a labeled ticket into a working change on a live preview, and posts the preview link back to the ticket. A developer then opens the PR. Butterneck does not open PRs itself.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I link a Jira ticket to a pull request in GitHub?
&lt;/h3&gt;

&lt;p&gt;Connect Jira Cloud to GitHub with the GitHub for Jira app, then put the issue key (for example PROJ-123) in the branch name, a commit message or the PR title. Jira then shows the PR in the ticket's Development panel. With Butterneck, a developer opens that PR after the requester has checked the change on a live preview; Butterneck doesn't open it.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which AI tools turn a Jira ticket into a pull request?
&lt;/h3&gt;

&lt;p&gt;Several do. Atlassian's own Jira Coding Agent can generate code from a work item and open a draft pull request for your team to review and merge. In Jira you can also assign a work item to Cursor, which starts a Cursor Cloud Agent and, if it opens a pull request, links it on the ticket, or to Atlassian's Claude Agent for Jira (Beta), which typically opens a draft GitHub pull request. Clogless opens a pull request with your Git provider when the change is ready. Butterneck stops one step earlier: a labeled ticket opens its own copy of the app, the developer's own coding agent makes the change, and a preview link goes back on the ticket. A developer then decides whether to commit it and open a PR. Butterneck never opens a pull request, merges or deploys. Our &lt;a href="https://www.butterneck.com/integrations/jira" rel="noopener noreferrer"&gt;Jira integration page&lt;/a&gt; explains how this differs from assigning the ticket to Cursor or Claude.&lt;/p&gt;

&lt;h3&gt;
  
  
  Should approving the preview also merge the pull request?
&lt;/h3&gt;

&lt;p&gt;Approving a preview and merging code are two different decisions: does the change look right, and is the code fit to merge? In Butterneck they stay separate. The person who asked approves what they see on the live preview. A developer then reads the diff and decides whether to commit it and open a pull request, and your usual review and branch rules take it from there. Butterneck never opens a pull request, merges or deploys.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I trigger it from Jira?
&lt;/h3&gt;

&lt;p&gt;Add the label &lt;code&gt;butterneck&lt;/code&gt; and assign the ticket to a teammate whose Jira account is mapped to a computer that has the project. Mapping each developer's Jira account to their computer is part of connecting Jira.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does the AI read the ticket's comments and attachments?
&lt;/h3&gt;

&lt;p&gt;Yes. The ticket's title, description, latest comments and attached files become the request, so a screenshot on the ticket reaches the coding agent. Leave secrets and production data out of the ticket.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which Jira tickets should you give an AI coding agent?
&lt;/h3&gt;

&lt;p&gt;Small, visible changes that the person who asked can check on screen: copy and labels, spacing and layout, an empty state, a new column or filter. Write the ticket as where it is, what it says now, what it should say and what must stay the same. Keep login and permissions, billing, database changes and secrets with a developer. More in &lt;a href="https://www.butterneck.com/blog/how-to-write-a-change-request-for-ai" rel="noopener noreferrer"&gt;how to write a change request for AI&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which Jira versions are supported?
&lt;/h3&gt;

&lt;p&gt;Jira Cloud only. Jira Data Center and Jira Server aren't supported.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can requests start from Linear, GitHub Issues or another tracker?
&lt;/h3&gt;

&lt;p&gt;Not automatically. Jira Cloud is the only issue tracker Butterneck connects to today; there is no Linear or GitHub Issues integration. Teams on another tracker paste the live preview's share link into the issue instead. The person who asked opens the running app in a browser, without an account, and, if the developer has allowed them to send requests, types the change in the chat next to the screen they mean. Nothing is posted back to that issue automatically, so the developer links the change when they commit or open the pull request. Butterneck doesn't commit, push, open a pull request, merge or deploy.&lt;/p&gt;

&lt;h3&gt;
  
  
  What happens if the ticket is edited later?
&lt;/h3&gt;

&lt;p&gt;Updating the same ticket does not open a second copy.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which AI coding agents does it use?
&lt;/h3&gt;

&lt;p&gt;The Cursor, Claude Code, or Antigravity CLI already installed and signed in on the developer's computer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://calendar.app.google/p2McAaz4ZwXBiG5m9" rel="noopener noreferrer"&gt;Book a 30-minute demo&lt;/a&gt; and we will label a real ticket together. Or see &lt;a href="https://www.butterneck.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;: the Starter plan is free and allows one private copy at a time (so one ticket or one chat copy). Each labeled ticket opens its own copy, so regular Jira use needs Pro. Pro is USD 19 per person per month, and a workspace owner on Starter can try Pro free for one month. More at &lt;a href="https://dev.to/"&gt;butterneck.com&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>jira</category>
      <category>ai</category>
      <category>productmanagement</category>
      <category>productivity</category>
    </item>
    <item>
      <title>AI change requests for product teams: a practical guide</title>
      <dc:creator>Butterneck</dc:creator>
      <pubDate>Tue, 03 Nov 2026 07:46:08 +0000</pubDate>
      <link>https://dev.to/butterneck/ai-change-requests-for-product-teams-a-practical-guide-1938</link>
      <guid>https://dev.to/butterneck/ai-change-requests-for-product-teams-a-practical-guide-1938</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.butterneck.com/blog/ai-change-requests-for-product-teams" rel="noopener noreferrer"&gt;butterneck.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;In short:&lt;/strong&gt; AI change requests let product managers and designers ask for a change to an existing app in plain words. An AI coding agent edits the real code, the requester checks the result on a live preview, and a developer decides what ships. In Butterneck, the agent is the Claude Code, Cursor or Antigravity CLI a developer already uses, running on the developer's computer. Butterneck does not commit, push or open a pull request; a developer decides first, and Butterneck never merges or deploys.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Every product team has a queue of small change requests. Fix this label. Move that field. Update the copy on the pricing card. Each one is minor. Together they eat a surprising amount of a team's week, mostly in handoffs.&lt;/p&gt;

&lt;p&gt;AI change requests are a way to shorten that queue: the person asking describes the change, an AI coding agent makes it on a live copy, and a developer approves it. This post covers what that looks like in practice for product teams, what to watch out for, and how Butterneck does it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is an AI change request?
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;AI change requests&lt;/strong&gt; let non-developers, like product managers and designers, ask for a change to an existing app in plain words. An AI coding agent edits the real code, the requester checks the result on a live preview, and a developer decides what ships.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;A change request is any "can we change X to Y" on a product that already exists. An AI change request is one where an AI coding agent does the edit, not a person reading a ticket.&lt;/p&gt;

&lt;p&gt;The useful version has four parts:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Ask in context.&lt;/strong&gt; The requester points at the real screen, not a description of it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AI edits real code.&lt;/strong&gt; Not a mockup. The agent changes the project's own files.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Requester sees the result.&lt;/strong&gt; On a running copy, right away.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Developer decides.&lt;/strong&gt; A developer reviews and publishes, or discards.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Leave out step 3 and the requester is back to waiting. Leave out step 4 and engineering will not let it near the product. For the PM side of this, and the other ways teams handle it, see &lt;a href="https://www.butterneck.com/blog/how-pms-can-change-a-live-app-without-waiting-on-engineering" rel="noopener noreferrer"&gt;how PMs can change a live app without waiting on engineering&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the requester checks, and what the developer checks
&lt;/h2&gt;

&lt;p&gt;Both people review the change. They check different things. It is the same plan, execute, verify loop a developer runs with an AI agent: the requester plans (describes the change), the agent executes (edits the code), and the verify step is split between two people.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The requester checks the result:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It is the change they asked for, seen on a live preview of the existing app, on the screen they asked from.&lt;/li&gt;
&lt;li&gt;The wording, layout and spacing look right.&lt;/li&gt;
&lt;li&gt;The states that matter still work: empty, error, loading, mobile width.&lt;/li&gt;
&lt;li&gt;Nothing else on the page moved or broke.&lt;/li&gt;
&lt;li&gt;If something is off, they keep asking on the same request until it is right.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;The developer checks the code:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The diff touches only what the request needed.&lt;/li&gt;
&lt;li&gt;The change is right beyond that one screen: shared components, translations, tests, emails that reuse the same text.&lt;/li&gt;
&lt;li&gt;Tests, lint and the build still pass.&lt;/li&gt;
&lt;li&gt;Nothing touched secrets, sign-in, billing or data.&lt;/li&gt;
&lt;li&gt;Whether it ships: commit and release it the usual way, or discard it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This split isn't only ours. VirtusLab's Visdom guide on &lt;a href="https://visdom-maturity-matrix.virtuslab.com/guides/organization/non-coder-contributors-via-agent-interfaces" rel="noopener noreferrer"&gt;non-coder contributors via agent interfaces&lt;/a&gt; describes the non-coder's job as "PEV: plan, execute, verify" and says their "verification method cannot be 'read the code.' It must be: see the change in a staging environment, run the specified acceptance test, or review the change description generated by the agent in non-technical terms." It also suggests that, at first, an engineer review "every agent output before it's merged, even though the non-coder has already verified it."&lt;/p&gt;

&lt;p&gt;For a fuller checklist, and why this check should happen before a pull request exists, see &lt;a href="https://www.butterneck.com/blog/live-preview-before-pull-request" rel="noopener noreferrer"&gt;live preview before the PR&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The requester's check matters more as AI writes more code than people can review. We collected the data on the &lt;a href="https://www.butterneck.com/blog/ai-prs-need-an-owner" rel="noopener noreferrer"&gt;AI PR review bottleneck&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why product teams need a process for this (and what AI automation should cover)
&lt;/h2&gt;

&lt;p&gt;Without a process, AI change requests happen anyway, just badly. A PM pastes a screenshot into a chat tool and asks a developer to "just run it through Claude." The developer copies the request, runs the agent, deploys a preview, and sends a link. The AI saved five minutes of coding. The relay still took two days.&lt;/p&gt;

&lt;p&gt;A process puts the request, the agent, and the preview in the same place.&lt;/p&gt;

&lt;p&gt;Most AI automation for product teams moves information: routing feedback, writing release notes, syncing Jira and Slack. Change requests are the same problem with code at the end. The part worth automating is the handoff: the request, the screen it's about, and the files, delivered to a coding agent that already knows the project. The part to keep human is the decision about what ships.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Butterneck handles AI change requests
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Feh10nopyv289kzt99n4z.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Feh10nopyv289kzt99n4z.gif" title="1280x720" alt="The chat updating the live app" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Requests come from chat or Jira
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Chat on a live copy.&lt;/strong&gt; A developer shares a link to the running app. The requester opens it, sees the app with a chat beside it, and types the change.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Jira.&lt;/strong&gt; Label a ticket &lt;code&gt;butterneck&lt;/code&gt; and assign it to a teammate whose Jira account is mapped to a computer that has the project. The ticket becomes the request, and a note with a preview link is posted back when the AI is done. Details in &lt;a href="https://www.butterneck.com/blog/jira-ticket-to-pr-with-ai" rel="noopener noreferrer"&gt;Jira ticket to pull request with AI&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The agent runs on a developer's machine
&lt;/h3&gt;

&lt;p&gt;The coding agent is the CLI the developer already uses: Cursor, Claude Code, or Antigravity. It runs on a developer's connected computer, in a folder they choose for that copy. Butterneck does not run its own model.&lt;/p&gt;

&lt;h3&gt;
  
  
  The preview is the app itself
&lt;/h3&gt;

&lt;p&gt;The app runs on the developer's machine and Butterneck gives it a public share link. Hot reload works through the link, so the requester sees the change on the screen they asked from. No staging deploy. See &lt;a href="https://www.butterneck.com/blog/share-local-app-without-deploying" rel="noopener noreferrer"&gt;how to share a local app without deploying&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  A developer decides what goes live
&lt;/h3&gt;

&lt;p&gt;Butterneck never merges, opens a PR, or deploys. The developer reads the conversation, checks the diff in their own tools, and publishes the usual way.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who can ask, and how much
&lt;/h2&gt;

&lt;p&gt;Access control matters once more than one person can send requests.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The developer chooses who can send: a named list, or anyone with the link.&lt;/li&gt;
&lt;li&gt;If the link is closed, a visitor can ask for access. The developer allows or declines.&lt;/li&gt;
&lt;li&gt;Viewers do not need an account.&lt;/li&gt;
&lt;li&gt;A reply from a developer in the chat does not change any files, so developers can answer questions without triggering the AI.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Guardrails to check before you roll this out
&lt;/h2&gt;

&lt;p&gt;These are the questions a CTO should ask any AI change request tool. Here are Butterneck's answers, stated plainly.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Where does the agent write?&lt;/strong&gt; Only in the folder tied to the copy. Make that folder a git worktree or a fresh clone, and in-flight requests stay off the main checkout.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Can it read secrets?&lt;/strong&gt; &lt;code&gt;.env&lt;/code&gt; files and team-added globs are listed as off-limits in the agent's instructions. That is a guardrail, not an enforced block. Keep production secrets off the bridge machine.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What leaves the machine?&lt;/strong&gt; The coding CLI sends code context to its own AI provider. Chat messages and preview traffic go through Butterneck's server.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Can a bad change be undone?&lt;/strong&gt; Each turn records a baseline. Stopping a turn usually rolls its file changes back; if it can't, the chat says so.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Can it ship by itself?&lt;/strong&gt; No. There is no code path that pushes, merges, or deploys.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Who can send a request, and what the share link exposes, are on the &lt;a href="https://www.butterneck.com/security" rel="noopener noreferrer"&gt;Security&lt;/a&gt; page.&lt;/p&gt;

&lt;p&gt;The longer version is in &lt;a href="https://www.butterneck.com/blog/run-ai-coding-agent-sandbox-on-your-machine" rel="noopener noreferrer"&gt;how Butterneck runs an AI coding agent in a sandbox on your machine&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What kinds of requests fit
&lt;/h2&gt;

&lt;p&gt;Good fits:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Copy and label changes.&lt;/li&gt;
&lt;li&gt;Layout and spacing tweaks.&lt;/li&gt;
&lt;li&gt;Small UI fixes: a missing state, a wrong color, a broken link.&lt;/li&gt;
&lt;li&gt;Adding or removing a form field when the backend already supports it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Poor fits:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;New features that need design and scoping.&lt;/li&gt;
&lt;li&gt;Changes to billing, permissions, or data models without close engineering review.&lt;/li&gt;
&lt;li&gt;Anything that needs production data or secrets.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Dalia Abuadas draws the same line on GitHub's engineering blog: "A change is not cheap just because the code was cheap to generate. It's cheap only if a human can confidently review and own the result." Adding a display field that already exists in the backend "is usually cheap"; changing authorization behavior "is not cheap, no matter how clean the diff" (&lt;a href="https://github.blog/engineering/the-cost-of-saying-yes-has-changed/" rel="noopener noreferrer"&gt;The cost of saying yes has changed&lt;/a&gt;, GitHub Blog, 17 July 2026).&lt;/p&gt;

&lt;p&gt;For how to word a single request so the agent gets it right, see &lt;a href="https://www.butterneck.com/blog/how-to-write-a-change-request-for-ai" rel="noopener noreferrer"&gt;how to write a change request for an AI coding agent&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  A rollout plan for product teams
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Week 1:&lt;/strong&gt; One app, one developer, one PM. Requests limited to copy and UI.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Week 2:&lt;/strong&gt; Add Jira. Agree on a "small change" definition for the &lt;code&gt;butterneck&lt;/code&gt; label.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Week 3:&lt;/strong&gt; Add more requesters through the named list. Keep one developer reviewing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;After that:&lt;/strong&gt; Decide which apps and request types are in scope, and write it down.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Track one number: time from request to reviewed change. Compare it with your normal ticket flow. If you need your engineering lead's agreement first, send them the &lt;a href="https://www.butterneck.com/blog/pm-change-request-pilot-proposal" rel="noopener noreferrer"&gt;4-week pilot proposal&lt;/a&gt;: a one-page plan with the scope, guardrails, what to measure and when to stop.&lt;/p&gt;

&lt;p&gt;For a product manager who wants to try Claude Code without setting up the repo, see &lt;a href="https://www.butterneck.com/blog/claude-code-for-product-managers" rel="noopener noreferrer"&gt;Claude Code for product managers&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Is there an AI coding agent for product teams?
&lt;/h3&gt;

&lt;p&gt;Yes. With Butterneck, a PM, designer or support lead asks for a change in a chat beside a live preview of the app, and the developer's own coding agent (Cursor, Claude Code or Antigravity) makes it on a computer that has the project. The person who asked checks the preview. A developer decides whether it ships, and Butterneck never opens a pull request, merges or deploys. For how agentic coding works when the person asking isn't a developer, see &lt;a href="https://www.butterneck.com/blog/agentic-coding-for-product-teams" rel="noopener noreferrer"&gt;agentic coding for product teams&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  What should a product manager look for in an AI change request tool?
&lt;/h3&gt;

&lt;p&gt;Four things. You ask on the real screen, not from memory. The AI edits the project's own code, not a mockup. You see the result on a running copy right away. And a developer decides what ships. Then ask the questions in the guardrails list above: where the agent writes, what it can read, what leaves the machine, and whether it can ship by itself. In Butterneck, the developer's own Cursor, Claude Code or Antigravity CLI makes the change on a computer that has the project, and Butterneck never opens a pull request, merges or deploys. For a side-by-side of tools that change an existing app, see &lt;a href="https://www.butterneck.com/blog/tools-for-non-developers-to-change-an-existing-app" rel="noopener noreferrer"&gt;AI tools that let non-developers change an existing app&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  What are AI change requests?
&lt;/h3&gt;

&lt;p&gt;They let non-developers, like product managers and designers, ask for a change to an existing app in plain words. An AI coding agent edits the real code, the requester checks the result on a live preview, and a developer decides what ships.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do requesters need technical skills?
&lt;/h3&gt;

&lt;p&gt;No. They use a share link in a browser, or a Jira label.&lt;/p&gt;

&lt;h3&gt;
  
  
  How should a non-technical stakeholder review an AI-generated UI change?
&lt;/h3&gt;

&lt;p&gt;On the running app, not in the code. Open the changed screen on the live preview and check it against what you asked for: the exact wording, the spacing next to the elements around it, the empty, loading and error states, and a phone-sized width. Make sure nothing else on the page moved. If something is off, ask again on the same request instead of starting a new one, and when it is right, say so in writing where you asked. With Butterneck the preview is the app running on a developer's connected computer, so this happens before any pull request exists. A developer then reads the diff and decides what ships; Butterneck doesn't commit, push, open a pull request, merge or deploy. The full checklist is in &lt;a href="https://www.butterneck.com/blog/live-preview-before-pull-request" rel="noopener noreferrer"&gt;what to check on a live preview before the PR&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can support teams use AI change requests to fix confusing labels and error messages?
&lt;/h3&gt;

&lt;p&gt;Yes, for the small fixes behind repeat tickets: a confusing label, a missing hint on a form, an unclear error message. The support lead opens the share link, types the change in the chat beside the live preview (a customer's screenshot can be attached), and checks the result on screen. A developer still reviews it and decides whether it ships. Keep anything that touches billing, refunds, permissions or customer data with a developer. When the ticket is a bug report, let the person who reported it check the fix on the preview before a developer ships it; see &lt;a href="https://www.butterneck.com/blog/reporter-checks-the-fix" rel="noopener noreferrer"&gt;let the reporter check the fix before it ships&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is the AI allowed to deploy?
&lt;/h3&gt;

&lt;p&gt;Not in Butterneck. It edits files in a folder. A developer publishes.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which AI models are used?
&lt;/h3&gt;

&lt;p&gt;Whichever model the developer's Cursor, Claude Code, or Antigravity CLI is set to use, under your team's plan for that tool (team or API plans recommended).&lt;/p&gt;

&lt;h3&gt;
  
  
  How much does it cost?
&lt;/h3&gt;

&lt;p&gt;Starter is free for one developer and one requester. Pro is USD 19 per person per month, with 20% off annual billing and local-currency pricing, and a workspace owner on Starter can try Pro for one month. See &lt;a href="https://www.butterneck.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can AI automate small change requests from the product backlog?
&lt;/h3&gt;

&lt;p&gt;Yes, for small, clearly described changes: copy and labels, layout and spacing, and small UI fixes. Keep sign-in, billing, data and permissions with an engineer. Some tools turn a ticket straight into a draft pull request. In Butterneck, a chat message on the live preview, or a Jira ticket labelled &lt;code&gt;butterneck&lt;/code&gt; and assigned to a teammate whose Jira account is mapped to a computer that has the project, starts the coding agent on a developer's connected computer. The person who asked checks the change on the preview, and a developer decides what ships. Butterneck does not open the pull request.&lt;/p&gt;

&lt;h3&gt;
  
  
  How is this different from tools that open pull requests?
&lt;/h3&gt;

&lt;p&gt;Butterneck stops at a reviewable change on a live preview. For a comparison with a PR-generating tool, read our &lt;a href="https://www.butterneck.com/blog/itera-alternative" rel="noopener noreferrer"&gt;Itera alternative&lt;/a&gt; or &lt;a href="https://www.butterneck.com/blog/clogless-alternative" rel="noopener noreferrer"&gt;Clogless alternative&lt;/a&gt; post, and for the reasoning, &lt;a href="https://www.butterneck.com/blog/human-in-the-loop-ai-coding" rel="noopener noreferrer"&gt;human-in-the-loop AI coding&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://calendar.app.google/p2McAaz4ZwXBiG5m9" rel="noopener noreferrer"&gt;Book a 30-minute demo&lt;/a&gt; and bring a change request from your backlog. Or start on the free plan from &lt;a href="https://www.butterneck.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;. Learn more at &lt;a href="https://www.butterneck.com/" rel="noopener noreferrer"&gt;butterneck.com&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productmanagement</category>
      <category>productivity</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
