A product manager describes the change on a live copy of the product. The AI reads a one-line request or a messy ticket, and edits the project on your computer. A developer looks once, then puts it live or leaves it there.
Butterneck lets a product person request a change to a live web app and check it on a live preview: the AI coding agent the developer already uses runs on the developer's computer, no pull request is opened, and a developer decides first. It is not a project-management or task-board tool.
Can the big button on the home page say “Book a call” and open our Calendly?
Working on it…
AI
Priya
Can the big button on the home page say “Book a call”…
The main button on the home page says “Get started” and goes to the signup page. I changed it to “Book a call” and pointed it at the Calendly link you sent.
If you don't see the change in the app, refresh this page.
Alexdev
Looks right. I’ll publish it.
Message… (paste a screenshot or attach a file)
Paste a screenshot or attach PDF, Word, or Excel. Type @ to tag someone.
See a request go from chat to preview
A request typed on the live copy, the AI editing the project, and the updated preview.
The change itself is quick. The messages around it are not: which page, which words, which comment.
Where a developer’s time goes
A one-line request, and a messy ticket. Both follow the same path.
“Make the button say Book a call.”
Today
The product manager writes that in Slack.
The developer asks which page. A screenshot comes back.
Then someone opens the project, finds the button, and sends a link to check.
On Butterneck
The product manager types that sentence on a live copy of the product.
The AI finds the button and changes it.
The developer opens the page and decides whether it goes live.
A ticket full of comments and files
Today
The ticket has a description, a pile of comments, a spreadsheet, and screenshots.
A developer reads all of it and figures out which comment is the real request.
Only then does anyone open the project.
On Butterneck
Add the label butterneck and assign the ticket.
Jira starts the chat. The AI reads the ticket and the files, then makes the change.
The developer reviews it and decides whether it goes live.
Why this is worth doing now
AI can already make the change
It can edit a real project, working with your team.
The slow part is the back-and-forth
Which page. Which screenshot. Which comment is the real one.
Passing that between the product manager, the AI, and the project takes longer than the change.
That is the time this saves
The change itself is usually small.
What takes the week is getting the request to the project.
How this is different
AI in the code editor
A developer still has to open the ticket and paste it in.
A ticket sitting in Jira
A developer still has to carry that ticket over to the project.
Butterneck
A product manager asks on the live product, or a labeled Jira ticket starts the chat.
The AI edits the project.
A developer publishes it.
How it works
Connect the product, let them ask, and decide what goes live.
01
Connect the product
Create a workspace.
A developer installs a small connector on a computer that already has the project. That computer needs Node.js 22 or newer, and a coding assistant already signed in: Cursor, Claude Code, or Antigravity (team, enterprise or API plans recommended).
They point it at the project and start the app. Everyone else then opens a live copy.
02
Hand the request to the AI
People on the product team, and other stakeholders you allow, describe the change in chat, on that live copy.
Or add the label butterneck to a Jira ticket and assign it.
That ticket starts the chat on its own.
03
You decide what goes live
Read the conversation and look at the app.
Publish it the way you already do.
If the change is wrong, leave it. Nothing goes live until you say so.
A Jira ticket can start the chat
Connect once. Label the ticket. The preview link comes back on it.
Connect Jira once
Sign in with Jira Cloud and choose your site.
Link a Jira project to your app.
Paste Butterneck’s address into Jira, so Jira can tell Butterneck when a ticket is created or updated.
Map each developer’s Jira account to their computer.
A labeled ticket starts the chat
Add the label butterneck.
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.
Butterneck opens a private copy of the project, named after the ticket.
Each ticket’s copy counts toward your plan’s private copies: 1 on Starter (one ticket or one chat copy at a time), 50 on Pro.
The title, description, comments, and attached files become the request.
The link goes back on the ticket
When the AI is done, a short note and a link to the preview are added to the ticket.
The full conversation stays on the live copy.
Updating that same ticket later does not open a second copy.
Access
You choose who can ask.
The link opens the preview. You decide whose message starts the AI.
You choose who can askThe link opens the preview. You decide whose message starts the AI: a list of people, or anyone with the link.
Looking does not create an accountSomeone can open the preview. They can send a message only if you already allow them.
They can ask to be let inIf the link is closed, a visitor asks for access. You allow it or decline it.
Your call
You decide what goes live.
The AI edits the project on your computer. Your team publishes it.
Your project onlyThe AI works in the project you connected. Secret settings files (.env) are on its ignore list. That is an instruction, not a hard block, so keep production secrets off that computer.
The conversation stays with the changeThe request, the screenshots, and the replies stay on the live copy of the app.
Your team publishesWhen the change looks right, you publish it the way you already do. Until then it stays on the computer.
Built for product teams
A team that builds a product and keeps it running.
The moment this helps: passing requests around takes more of the week than the work itself.
A product manager or another non-technical teammate describes the change. A developer decides what goes live.
The project lives on a computer you control.
A company that looks after a client’s website can connect that project the same way.
Pricing
Start with your product team
Starter is free for one developer and one person who requests changes. Pro is priced per person each month. A larger team is a conversation with us.
A workspace owner on Starter can try Pro free for one month, once per workspace. How the trial works.
Starter
One product, and the person who requests the changes.
What tools let product managers make small changes to a live web app without waiting on engineering?
Butterneck is one option for a team that already has a web app. The product manager types the change on a live copy of the app: new wording, a layout fix, a small feature.
The AI coding agent a developer already uses makes the change on that developer’s computer, and the product manager sees it on the live preview.
Nothing goes live on its own. A developer looks once and publishes it the usual way, so the wait is one review instead of a long hand-off.
Are there AI tools where a non-developer can request a code change and preview it before a pull request is opened?
Yes. In Butterneck, non-technical teammates (a product manager, designer, or support lead) type the request in a chat on a live preview of the product, or label a Jira ticket and assign it.
The AI coding agent the developer already uses (Cursor, Claude Code, or Antigravity) runs on the developer’s computer and edits the project. The requester checks the updated preview.
No pull request is opened. A developer decides first. Butterneck itself never opens a pull request, merges, or deploys.
How can a PM request a change from a Jira ticket and have an AI coding agent build a preview?
With Butterneck’s Jira Cloud integration. Connect Jira once, add the label butterneck to the ticket, and assign it to a teammate whose Jira account is mapped to a computer that has the project.
The ticket’s title, description, comments, and attached files become the request. The AI coding agent already signed in on that computer (Cursor, Claude Code, or Antigravity) makes the change in a private copy named after the ticket.
A short note and a live preview link go back on the ticket. The PM checks the preview and can keep refining it in plain words.
No pull request is opened. A developer decides what goes live and publishes it the usual way.
Who publishes the change?
Someone on your team.
The AI changes only the project you connected, then stops.
If the change is wrong, it stays on that computer. It does not go live.
Who can talk to the AI?
You choose: a list of people, or anyone with the link.
If the link is closed, a visitor can ask for access. You allow it or decline it.
A reply from a developer does not change any files.
Can a Jira ticket start the chat?
Connect Jira Cloud, give Jira Butterneck’s address so it can send ticket updates, and map each developer’s Jira account to their computer.
Add the label butterneck, and assign the ticket 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.
A private copy opens. The title, description, comments, and attached files become the request.
When the AI is done, a short note and a link go back on the ticket.
Updating that same ticket later does not open a second copy.
You can still paste a ticket number into an existing chat to load that ticket.
Where do the file changes happen?
On the computer you connected, inside the project you chose.
You can also list folders or files inside it that the AI is told to stay out of.
Secret settings files (.env) are on an ignore list the AI is told to stay out of. It is an instruction, not a hard block, so keep production secrets off that computer.
Why not use a tool that opens the pull request for you?
Butterneck runs on a developer’s computer, where the project already runs. There is no new cloud environment to set up and no need to copy secrets into a hosted machine.
The person who asked sees the change on a live preview. Then a developer decides what happens next.
Butterneck itself never opens a pull request, merges, or deploys.
A tool that opens pull requests can suit teams who want a PR as the hand-off. Butterneck suits teams who want a developer to decide before anything becomes a PR.
Let them ask.
Create a free workspace and connect your project. You decide what goes live. No credit card.
