What the agent does
Ember apps carry deprecations in a file, and the agent starts by reading what that file hides. In an app laid out like ember-learn/super-rentals, app/deprecation-workflow.js calls setupDeprecationWorkflow with throwOnUnhandled: false and a workflow list of two entries, both handler: 'silence': ember-data:deprecate-legacy-imports and warp-drive.deprecate-tracking-package. The comment above them reads "TODO: actually fix these deprecations". app/app.js loads that file through importSync only inside macroCondition(isDevelopingApp()), so it is active in the development-mode build that pnpm test makes with vite build --mode development. Separately, config/environment.js sets RAISE_ON_DEPRECATION: true, and ember-cli-build.mjs passes WarpDrive a compatWith of '5.8' with an empty deprecations object, under a comment saying that value should name the newest version whose deprecations are all resolved.
It does not guess what triggers an id from its name. The app's own files already import from the new packages: app/models/rental.js from @warp-drive/legacy/model, app/services/store.js from @warp-drive/legacy and @warp-drive/json-api, the routes from @warp-drive/utilities/json-api, and a search of app/ and tests/ finds the string ember-data only inside the workflow file itself. So the agent removes one silence entry, runs pnpm test with Chrome under Testem, and reads the message that now appears. A deprecation message names its id, the version it was introduced in, the version that removes the old behaviour and a guide URL, and the stack shows whether the call came from app/ or from a package under node_modules. The agent records both for each id before changing any code.
The fix depends on where the trigger lives. When it is in the app, the agent changes the import or the call to the form the guide names and reruns the suite: 24 tests across the acceptance file, seven component files and the model test, which exercise the store through store.request(query('rental')), findRecord and createRecord. When it is in a dependency, the fix is a version of that dependency that no longer makes the call. The agent checks the registry for one, bumps only that package, and keeps the five @warp-drive/* packages on a single version, since package.json pins them all to ~5.8.2. When no fixed release exists yet, the entry stays silenced, and the pull request says which package is waiting and on what.
Last, it makes the result stick. For each WarpDrive deprecation it has resolved, the agent records it in the deprecations object of the setConfig call in ember-cli-build.mjs, which is the place that file's own comment reserves for resolved ones, and raises compatWith only when every deprecation up to that version is cleared. It deletes the emptied entries and the TODO from app/deprecation-workflow.js and sets throwOnUnhandled: true, so a deprecation nobody has triaged fails the test run and cannot scroll past in a console. Then it runs pnpm lint, whose ESLint config already loads eslint-plugin-warp-drive, and pnpm test one more time on the final tree.
Start it with one API call
POST https://api.phoenix.so/o/{org}/sessions with this body:
{
"agent": "claude",
"input": "Fix the deprecations this Ember app is silencing. Read app/deprecation-workflow.js, app/app.js, config/environment.js, ember-cli-build.mjs, package.json, eslint.config.mjs, testem.cjs, app/services/store.js, app/models/rental.js, app/utils/handlers.js, the routes and tests/test-helper.js first. Install with pnpm, export CI=true, install Chrome if it is missing, and run pnpm test once unchanged to record the baseline. Then, for each silenced id in the workflow list, one at a time: remove the entry, run pnpm test, and capture the full deprecation message with its id, since and until versions, guide URL and stack. Say whether the trigger is in this repository or in a dependency. If it is in the app, change the code to the replacement the guide names. If it is in a dependency, look for a released version that fixes it and bump only that package, keeping all @warp-drive packages on one version; if none exists, restore the silence entry with a comment naming the package. Do not silence anything new and do not edit files under node_modules. For each WarpDrive deprecation resolved, record it in the deprecations object of setConfig in ember-cli-build.mjs, and raise compatWith only if every deprecation up to that version is resolved. Finally set throwOnUnhandled to true, remove the TODO, and run pnpm lint and pnpm test. Open a pull request with a table of each id, where it was triggered, the fix or the reason it remains, and the baseline and final test output.",
"resources": [
{
"url": "https://github.com/your-org/your-app"
}
]
}- Get an API key. In the console, open Settings, then API keys, and create a key for your org. Send it in the Authorization header as a Bearer token.
- Send the request. POST the body in request.json to https://api.phoenix.so/o/{org}/sessions, with your repository as the resources URL. The run starts in its own cloud sandbox.
- Read what came back. Follow the run on its live stream or wait for the run.completed webhook, then read the result and its trajectory.
What comes back
The pull request has one commit per deprecation id, each small enough to read in one sitting: the removed silence entry, the changed import or the single dependency bump, and the matching line in ember-cli-build.mjs. A final commit turns on throwOnUnhandled. The description carries a table with a row per id giving the message as printed, the file or package that triggered it, the versions it was introduced and removed in, and what was done. Below the table are two test outputs, the baseline from the untouched tree and the last run.
A reviewer checks that the workflow list shrank and did not merely change, that no handler was switched from silence to log to keep a count down, and that any entry still present has a comment naming the dependency it waits on. They look at each deprecations entry in setConfig against the table, because telling the build a deprecation is resolved removes the old code path for it, and a wrong entry there breaks at runtime and not at build time. If compatWith moved, they confirm that the table has no remaining row at or below the new version.
They also decide whether to keep throwOnUnhandled: true. It is the stricter setting: the next dependency update that introduces a deprecation turns the Test job red until someone fixes or triages it. A team that prefers a warning can revert that one line and keep everything else.
Run it on every CI failure from a new deprecation
Once unhandled deprecations fail the suite, the event to react to is a red Test job. Create an automation on the Project with a github trigger on workflow_run.failure and a prompt that says: read the failed run named in the event; if the failure is an unhandled deprecation, trace it and fix it the way this page describes and open a pull request; if it is anything else, stop and say so. The trigger adds the event after the prompt as data and fills in no placeholder.
CI runs from forks never fire the trigger, and the automation's max_runs_per_hour bounds how many runs a streak of red builds can start. A team that upgrades on a calendar can pair this with a monthly schedule trigger that runs the same pass before the upgrade does.
The use case this job follows, with its automation and trigger: Hand off a long task.
Why run it on Rush?
A deprecation is only understood once it has been made to fire, and that takes a build and a browser. The agent's Rush sandbox has both to itself, so it can remove one entry, run the whole suite, read the stack, restore, and repeat for the next id without anyone's dev server being interrupted. Each run of pnpm test and the message it printed is kept in the transcript, so the table in the pull request can be checked against what the tools said.
The work also tends to stall on a question only the team can answer, such as whether to take a dependency bump now. When a turn ends the sandbox parks with its disk and memory, and a follow-up message wakes it where it left off, so the answer goes to the same run and it carries on from the commit it had reached.
Frequently asked questions
Why not just add the new deprecations to the workflow file?
That is what the file is for in the short term, and it is how the two entries got there. But a silenced deprecation is still a scheduled breakage: each one names the version that removes the old behaviour. The agent's job is to shrink the list before an upgrade reaches one of those versions, and to leave a comment on anything it could not remove.
What if the deprecation comes from an addon I cannot change?
Then the fix is a newer release of that addon, and the agent looks for one that no longer triggers the message. If none exists, the entry stays with a comment naming the addon, and the pull request lists it as waiting. The agent does not patch files under node_modules or fork the addon unless the request asks for that.
Will the app behave differently after the pull request merges?
It should not, and the test output is the evidence offered for that. Replacing a deprecated import with its successor keeps behaviour by design. The one deliberate change is in development and test builds, where an untriaged deprecation now throws; production builds do not load the workflow file at all.
More Ember.js jobs
The same job on other stacks
More jobs like this: Hand off a long task
- Fix "AttributeError: 'EntryPoints' object has no attribute 'get'" on Python 3.12 (importlib.metadata)