Devin attempts an Electron Vue migration
Sean Kearney reports Devin opening a Vue 3 migration PR for his Electron app, but repeated false build assurances and later runtime failures caused him to abandon the attempt.
Original prompt
Shared by the source author. See source notes for context.
Upgrade this from Vue.js v2 to the latest Vue.js version.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Sean Kearney
- Original account
- Read the source ↗
- Published
- 21 Dec 2024
- Source link checked
- 15 Oct 2026
- Reported result
- Sean Kearney reports Devin opening a Vue 3 migration PR for his Electron app, but repeated false build assurances and later runtime failures caused him to abandon the attempt.
- Human involvement
- Kearney reviews commits, corrects version assumptions and checks the agent environment. He stops after build and runtime problems persist.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Devin inspects the Electron/Vue 2 repository and plans a Vue 3 migration.
- Kearney clarifies requirements and requests commits after small batches of components.
- Devin migrates dependencies, stores and routing and opens a PR.
Sean Kearney gave Devin access to a production Electron application using Vue 2 and asked it to migrate to Vue 3 with the Composition API and script setup. The agent inspects the package configuration, proposes a plan and asks questions about target versions and state management. Its initial claim about the latest Vue release is already wrong.
Kearney clarifies the direction and asks for frequent commits so he can inspect work. Devin changes dependencies, migrates routing and moves stores toward Pinia. After repeated package-approval interruptions, Kearney allows those changes without another question. A pull request appears about four hours into the attempt.
The PR does not mean the migration is finished. Devin repeatedly says the build works while Kearney can still see errors on the agent's own machine. They continue through investigation and webpack changes until the build finally passes, only to reach runtime failures.
Kearney eventually stops after several days and roughly half his available compute units. The result is a substantial but unfinished migration and a useful documented failure. The account makes human inspection of actual build and runtime behavior essential; a detailed PR description and a claimed green build did not establish a working application.
Prompt
Original prompt
Source: seankearney.com · Sean Kearney
Frequently asked questions
Did the migration finish?
No. Kearney abandoned it after build repairs led to further runtime problems.
Why were the build assurances unreliable?
He could see errors on Devin's own machine even when it said the build passed.
What did frequent commits provide?
They let Kearney inspect migration progress locally instead of waiting for a final result.
More details
Remaining steps
- Kearney checks claimed build success, reports remaining errors and reaches later runtime failures.
- He abandons the unfinished migration after several days.
About this account
Devin edited the Electron/Vue project toward Vue 3 and Pinia, committed changes and attempted builds; the migrated application did not run successfully.
Original account opened and read. Original prompt excerpt from the published task or operating rules; additional context is omitted. Outcomes are author reports, not independently reproduced.
Credit: Sean Kearney
Source published 21 Dec 2024
Source checked 15 Oct 2026
Tools and topics
Devin · Vue · Electron · Pinia
Devin · Vue · Electron
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.